Difference between revisions of "Maximum retries exceeded on transmission"

From Kolmisoft Wiki
Jump to navigationJump to search
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 18: Line 20:
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 ==


It is possible that Asterisk is under NAT and not properly configured.
It is possible that Asterisk is under NAT and not properly configured.


Solution: [[Asterisk under NAT]]
Solution: [[Asterisk under NAT]]

Revision as of 17:47, 25 November 2008

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

It is possible that Asterisk is under NAT and not properly configured.

Solution: Asterisk under NAT