Difference between revisions of "Maximum retries exceeded on transmission"
(New page: http://bugs.digium.com/view.php?id=5336 This is not a problem with Asterisk - essentially what happens when you cancel a call is this: 1. Phone sends CANCEL 2. Asterisk sends 487 Reque...) |
|||
| (6 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
= SIP implementation bug on device = | |||
http://bugs.digium.com/view.php?id=5336 | http://bugs.digium.com/view.php?id=5336 | ||
| Line 10: | Line 12: | ||
Your phone/device is not sending an ACK back, so Asterisk continues to send the 487 Request Terminated because it knows no better. | Your phone/device is not sending an ACK back, so Asterisk continues to send the 487 Request Terminated because it knows no better. | ||
This is a problem with SIP non-compliance by the phone/device, specifically, rfc3261, section 17.1.1 requries an ACK to the 487. If Asterisk do not get ACK'd, it should resend. | '''This is a problem with SIP non-compliance by the phone/device, specifically, rfc3261, section 17.1.1 requries an ACK to the 487.''' If Asterisk do not get ACK'd, it should resend. | ||
Solution: | |||
If you are using some softphone - try to change it. | If you are using some softphone - try to change it. | ||
If you are using some hard-phone - try to upgrade/downgrade firmware. | If you are using some hard-phone - try to upgrade/downgrade firmware. | ||
<br><br> | |||
---------------- | |||
<br><br> | |||
= Asterisk under NAT = | |||
In CLI also visible: '''No reply to our critical packet''' | |||
WARNING[25126]: chan_sip.c:2057 retrans_pkt: Maximum retries exceeded on transmission 2c051da44ee93e675cbef8932367e41a@209.216.2.xxx for seqno 102 (Critical Response) -- See doc/sip-retransmit.txt. | |||
[2011-08-10 09:45:16] WARNING[25126]: chan_sip.c:2079 retrans_pkt: Hanging up call 2c051da44ee93e675cbef8932367e41a@209.216.2.xxx - no reply to our critical packet (see doc/sip-retransmit.txt). | |||
It is possible that Asterisk is under NAT and not properly configured. | |||
Solution: [[Asterisk under NAT]] | |||
If it does not help - change your router. | |||
<br><br> | |||
= Other network problems = | |||
Proceed with: [[sip-retransmit.txt]] | |||
Latest revision as of 15:05, 10 August 2011
SIP implementation bug on device
http://bugs.digium.com/view.php?id=5336
This is not a problem with Asterisk - essentially what happens when you cancel a call is this:
1. Phone sends CANCEL 2. Asterisk sends 487 Request Terminated 3. Asterisk sends 200 OK 4. Phone sends ACK to acknowledge the above messages.
Your phone/device is not sending an ACK back, so Asterisk continues to send the 487 Request Terminated because it knows no better.
This is a problem with SIP non-compliance by the phone/device, specifically, rfc3261, section 17.1.1 requries an ACK to the 487. If Asterisk do not get ACK'd, it should resend.
Solution:
If you are using some softphone - try to change it.
If you are using some hard-phone - try to upgrade/downgrade firmware.
Asterisk under NAT
In CLI also visible: No reply to our critical packet
WARNING[25126]: chan_sip.c:2057 retrans_pkt: Maximum retries exceeded on transmission 2c051da44ee93e675cbef8932367e41a@209.216.2.xxx for seqno 102 (Critical Response) -- See doc/sip-retransmit.txt. [2011-08-10 09:45:16] WARNING[25126]: chan_sip.c:2079 retrans_pkt: Hanging up call 2c051da44ee93e675cbef8932367e41a@209.216.2.xxx - no reply to our critical packet (see doc/sip-retransmit.txt).
It is possible that Asterisk is under NAT and not properly configured.
Solution: Asterisk under NAT
If it does not help - change your router.
Other network problems
Proceed with: sip-retransmit.txt
