<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<br>
To:
<a class="moz-txt-link-rfc2396E" href="sip:8009499014@X.YYY.32.10:5060"><sip:8009499014@X.YYY.32.10:5060></a>;tag=ac86f72d2bfe10395b2e62e01c70bf66.0f65<br>
<br>
In your call sample To has a tag. <br>
if this is the first Invite it can't have a tag at the end,
otherwise Asterisk will look for an existing dialog in its database
and will show an error, if can't find any.<br>
<br>
It looks like the other end is never closing the previous dialog?..
is Asterisk sending a proper 200 OK after receiving a BYE?<br>
NAT problem?<br>
<br>
regards,<br>
<pre class="moz-signature" cols="72">--
==================================
Miguel Oyarzo
DevOps Engineer
<a class="moz-txt-link-freetext" href="http://www.linkedin.com/in/mikeaustralia">http://www.linkedin.com/in/mikeaustralia</a>
Linux User: # 483188 - counter.li.org
Melbourne, Australia
</pre>
<br>
<br>
<br>
<div class="moz-cite-prefix">On 9/17/2013 6:18 AM, Vik Killa wrote:<br>
</div>
<blockquote
cite="mid:CAC-LwPNRCHrbtef4cDkxmRWdyf_HFWuXY5smVritnAsj0ar3WQ@mail.gmail.com"
type="cite">
<meta http-equiv="Context-Type" content="text/html;
charset=ISO-8859-1">
<div dir="ltr">Asterisk is sending a 481 in response to an INVITE
for reasons I do not understand. Here is the INVITE:<br>
<br>
<br>
<div>
<div>INVITE <a class="moz-txt-link-freetext" href="sip:8009499014@X.YYY.32.3:5060;transport=udp">sip:8009499014@X.YYY.32.3:5060;transport=udp</a>
SIP/2.0</div>
<div>Record-Route: <a class="moz-txt-link-rfc2396E" href="sip:X.YYY.32.10;lr=on;ftag=247898"><sip:X.YYY.32.10;lr=on;ftag=247898></a></div>
<div>To:
<a class="moz-txt-link-rfc2396E" href="sip:8009499014@X.YYY.32.10:5060"><sip:8009499014@X.YYY.32.10:5060></a>;tag=ac86f72d2bfe10395b2e62e01c70bf66.0f65</div>
<div>From: "Scott Thompson"
<a class="moz-txt-link-rfc2396E" href="sip:7166359474@X.YYY.32.10"><sip:7166359474@X.YYY.32.10></a>;tag=247898</div>
<div>Via: SIP/2.0/UDP
X.YYY.32.10;branch=z9hG4bK542e.5042d534.0</div>
<div>Via: SIP/2.0/UDP
X.YYY.33.178:5060;rport=5060;received=X.YYY.33.178;branch=z9hG4bK57b720cccb00f8498662f48e8</div>
<div>Call-ID: <a moz-do-not-send="true"
href="mailto:94f80f866e877490729548a079abe371@192.168.101.5">94f80f866e877490729548a079abe371@192.168.101.5</a></div>
<div>CSeq: 2 INVITE</div>
<div>Contact: <a class="moz-txt-link-rfc2396E" href="sip:7166359474@X.YYY.33.178:5060"><sip:7166359474@X.YYY.33.178:5060></a></div>
<div>Max-Forwards: 69</div>
<div>x-inin-crn: 2001471530;loc=Amherst;ms=STAMPEDE-MS</div>
<div>Supported: join, replaces</div>
<div>User-Agent: ININ-TsServer/3.13.11.12748</div>
<div>Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS,
PRACK, REFER, SUBSCRIBE</div>
<div>Accept: application/sdp</div>
<div>Accept-Encoding: identity</div>
<div>Content-Type: application/sdp</div>
<div>Content-Length: 252</div>
<div>Proxy-Authorization: Digest
username="909003660716",realm="X.YYY.32.10",nonce="5237559000011a22ed0fae66765d46ef9131e311fbb9d2fb",uri=<a class="moz-txt-link-rfc2396E" href="sip:8009499014@X.YYY.32.10:5060">"sip:8009499014@X.YYY.32.10:5060"</a>,response="cb6306569b3047ac35064dcb5aee6db4"</div>
<div>X-Enswitch-RURI: <a class="moz-txt-link-freetext" href="sip:8009499014@X.YYY.32.10:5060">sip:8009499014@X.YYY.32.10:5060</a></div>
<div>X-Enswitch-Source: X.YYY.33.178:5060</div>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div>The only problem I see with this INVITE is the VIAs are not
right after the INVITE line... although in <a
moz-do-not-send="true"
href="https://www.ietf.org/rfc/rfc3261.txt">https://www.ietf.org/rfc/rfc3261.txt</a>,
it explicitly states the the order of the headers is not a
requirement, it seems Asterisk does make it one... </div>
<div><br>
</div>
<div>"The relative order of header fields with different field
names is not</div>
<div> significant. However, it is RECOMMENDED that header
fields which are</div>
<div> needed for proxy processing (Via, Route, Record-Route,
Proxy-Require,</div>
<div> Max-Forwards, and Proxy-Authorization, for example)
appear towards</div>
<div> the top of the message to facilitate rapid parsing. The
relative</div>
<div> order of header field rows with the same field name is
important."</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by <a class="moz-txt-link-freetext" href="http://www.api-digital.com">http://www.api-digital.com</a> --
New to Asterisk? Join us for a live introductory webinar every Thurs:
<a class="moz-txt-link-freetext" href="http://www.asterisk.org/hello">http://www.asterisk.org/hello</a>
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
<a class="moz-txt-link-freetext" href="http://lists.digium.com/mailman/listinfo/asterisk-users">http://lists.digium.com/mailman/listinfo/asterisk-users</a></pre>
</blockquote>
<br>
</body>
</html>