rssLink RSS for all categories
 
icon_red
icon_green
icon_red
icon_red
icon_blue
icon_green
icon_green
icon_red
icon_red
icon_red
icon_orange
icon_green
icon_green
icon_green
icon_green
icon_blue
icon_green
icon_orange
icon_red
icon_green
icon_red
icon_red
icon_green
icon_red
icon_red
icon_red
icon_red
icon_orange
icon_green
 

FS#11683 — FS#15877 — SIP Call Recording

Attached to Project— VoIP
Incident
Backend / Core
CLOSED
100%
We had a disruption in the treatment of certain SIP call recordings between 9:35 and 9:38 this morning.

We are investigating.
Date:  Wednesday, 23 December 2015, 17:25PM
Reason for closing:  Done
Comment by OVH - Wednesday, 23 December 2015, 17:25PM

The problem was detected on the SIP1 Proxy.

This proxy rejected the new recordings for 3 minutes from 9:35 to 9:38 following a localized overload of such requests.
This should specifically block packs and not most requests, we adjust the configuration in these terms.

This had no impact on the current calls but on the positions being recorded at this time.

Most of SIP extensions automatically try again to be recorded, but it seems that some modems took longer,
a simple reboot could force this recording.