Summary:ASTERISK-05325: Ringing multiple sip phones gives warning
Reporter:John Hill (bennoach)Labels:
Date Opened:2005-10-19 12:18:24Date Closed:2011-06-07 14:10:08
Versions:Frequency of
Description:Oct 19 12:12:38 WARNING[3514]: chan_sip.c:1184 retrans_pkt: Maximum retries exceeded on transmission 56103c340b93448b1e282bb93a019b69@ for seqno 102 (Critical Request)
Oct 19 12:12:38 WARNING[3514]: chan_sip.c:1201 retrans_pkt: Hanging up call 56103c340b93448b1e282bb93a019b69@ - no reply to our critical packet.
Oct 19 12:12:39 NOTICE[3514]: sched.c:296 ast_sched_del: Attempted to delete nonexistent schedule entry 644!

I get the above message if I try:
exten => s,4,Dial(SIP/2238&SIP/2239|20|tpnNA(beep))

Phones will ring but all you get is dial tone when you pick them up.

IF I use:
exten => s,4,Dial(SIP/2238|20|tpnNA(beep))
No problem.

SMP no Hyperthread.

Comments:By: Olle Johansson (oej) 2005-10-19 12:30:46

Why is this report categorized as "Zaptel"? Also, for all SIP reports you have to provide a SIP debug log according to the bug tracker instructions (make sure you read them!)

Seems like one of the phones does not answer our call to them from the short excerpt.

By: Olle Johansson (oej) 2005-10-19 13:45:22

Please *never* add that long debug in the note, add all debug files as external attachments to the issue report. It makes it much easier reading the e-mails from the bug tracker and managing the issue.

By: Olle Johansson (oej) 2005-10-19 13:50:40

Seems like we time out before we get any response from 2238. It's a perfectly logical timeout...

You might want to test with or without qualify=yes in the sip.conf peer entry for 2238. Also set debug to 4 and verbose to 4 when capturing a SIP debug.

By: John Hill (bennoach) 2005-10-19 14:12:15

Sorry for the long debug. First time!

Turning off qualify as you suggested fixed the warning problem.

I did notice that the log will say calling and list each phone then it will give a list of ringing the phones with duplicate entries:

   -- Called 2238
   -- Called 2239
   -- Called 2240
   -- Called 2241
   -- Called 2242
   -- Called 2243
   -- SIP/2238-c0bb is ringing
   -- SIP/2240-1ac0 is ringing
   -- SIP/2242-d7cc is ringing
   -- SIP/2239-446e is ringing
   -- SIP/2241-42f0 is ringing
   -- SIP/2243-ad8d is ringing
   -- SIP/2239-446e is ringing
   -- SIP/2241-42f0 is ringing
   -- SIP/2239-446e is ringing
   -- SIP/2243-ad8d is ringing
   -- SIP/2241-42f0 is ringing
   -- SIP/2243-ad8d is ringing

The warning is gone. I can't test the answer pickup till this evening, this test box is at my home.


By: Olle Johansson (oej) 2005-10-19 14:29:23

Seems like we can write this off as a timing problem in your network.

By: John Hill (bennoach) 2005-10-19 14:43:05

Yes or could it be a slow smp system. I rebuilt this on an old 300MHZ Dual PII from an older 400MHZ single PII. It is in a vlan but perhaps the cpu speed is dragging it down. I did notice it spawns 12 child processess. This seems a bit over the top? Memory usage is good, io seems ok. No irq problems.
Go ahead and close this.
Thanks again.

By: Olle Johansson (oej) 2005-10-19 14:45:31

Removing the "major" status...