Displaying 2 results from an estimated 2 matches for "1778xxxxxxx".
2011 Jan 27
1
chan_sip bug? (Asterisk 1.4)
Today I upgraded my Asterisk to the new 1.4.39.1. One of sip trunk stop
working after the upgrade. Here is the sip debug:
---------------------------------------------------------------------------
<--- SIP read from 208.65.xxx.xxx:5060 --->
INVITE sip:1778xxxxxxx at 10.11.22.77:5060 SIP/2.0
Via: SIP/2.0/UDP
208.65.xxx.xxx:5060;branch=z9hG4bK-d8754z-d9175178645e9146-1---d8754z-;rport
Via: SIP/2.0/UDP
208.65.xxx.xxx:5061;branch=z9hG4bK-uhhmj2ir4ew6cn4p;rport=5061
Max-Forwards: 69
Record-Route: <sip:208.65.xxx.xxx;lr>
Contact: "Anonymous"<...
2011 Jan 28
0
asterisk-users Digest, Vol 78, Issue 66
...it could be that the networking routines in
> Asterisk have added a 7 at the end. You could compare a tcpdump of
> that packet to what Asterisk sees. If the tcpdump shows .777 then the
> problem is in Sippy. If it shows .77 then the problem is in Asterisk.
>
>
>> INVITE sip:1778xxxxxxx at 10.11.22.77:5060 SIP/2.0
>> Via: SIP/2.0/UDP
>> 208.65.xxx.xxx:5060;branch=z9hG4bK-d8754z-d9175178645e9146-1---d8754z-;rport
>> Via: SIP/2.0/UDP
>> 208.65.xxx.xxx:5061;branch=z9hG4bK-uhhmj2ir4ew6cn4p;rport=5061
>> Max-Forwards: 69
>> Record-Route:<sip:208.6...