Hi Forums,
I’ve got someone else’s box doing strange lockups. It always seems to occur in the logs around a bunch of DTMF transfers.
It is a busy box with a 100+ extensions, so there’s quite a bunch of people getting pissed off when it happens
Jul 16 14:00:43 DEBUG[22758] chan_sip.c: Stopping retransmission on '3c2f8970493e-zq15ezybd5dn@snom320-00041327C661' of Response 2: Match Found
Jul 16 14:00:43 DEBUG[23424] channel.c: Got DTMF on channel (SIP/2580-b5e9eb38)
Jul 16 14:00:43 DEBUG[23424] channel.c: Bridge stops bridging channels SIP/5060-b6cc6ab8 and SIP/2580-b5e9eb38
Jul 16 14:00:43 DEBUG[23424] res_features.c: Feature interpret: chan=SIP/5060-b6cc6ab8, peer=SIP/2580-b5e9eb38, sense=2, features=2
Jul 16 14:00:43 DEBUG[23424] res_features.c: Set time limit to 500
Jul 16 14:00:43 DEBUG[23424] channel.c: Got DTMF on channel (SIP/2580-b5e9eb38)
Jul 16 14:00:43 DEBUG[23424] channel.c: Bridge stops bridging channels SIP/5060-b6cc6ab8 and SIP/2580-b5e9eb38
Jul 16 14:00:43 DEBUG[23424] res_features.c: Feature interpret: chan=SIP/5060-b6cc6ab8, peer=SIP/2580-b5e9eb38, sense=2, features=2
Jul 16 14:00:43 DEBUG[23424] res_features.c: Executing Attended Transfer SIP/5060-b6cc6ab8, SIP/2580-b5e9eb38 (sense=2) XXX
Jul 16 14:00:43 DEBUG[23424] channel.c: Scheduling timer at 160 sample intervals
Jul 16 14:00:43 DEBUG[23424] channel.c: Scheduling timer at 160 sample intervals
Is it a known problem?