<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 sip:8009499014@X.YYY.32.3:5060;transport=udp SIP/2.0</div><div>Record-Route: <sip:X.YYY.32.10;lr=on;ftag=247898></div>
<div>To: <sip:8009499014@X.YYY.32.10:5060>;tag=ac86f72d2bfe10395b2e62e01c70bf66.0f65</div><div>From: "Scott Thompson" <sip:7166359474@X.YYY.32.10>;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 href="mailto:94f80f866e877490729548a079abe371@192.168.101.5">94f80f866e877490729548a079abe371@192.168.101.5</a></div>
<div>CSeq: 2 INVITE</div><div>Contact: <sip:7166359474@X.YYY.33.178:5060></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="sip:8009499014@X.YYY.32.10:5060",response="cb6306569b3047ac35064dcb5aee6db4"</div>
<div>X-Enswitch-RURI: sip:8009499014@X.YYY.32.10:5060</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 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>