Re: [reSIProcate-users] Using sendTo to force destination of an ACK
You should use Wireshark: www.wireshark.org to trace the actual SIP
packets that are sent out on the network interface to confirm if the
ACK is actually being sent or not. Otherwise there should be some
information in the stack level trace of resip that would help track
this down.
Scott
On Tue, Feb 3, 2009 at 2:44 PM, Andrew Wood <ajwood@xxxxxxx> wrote:
> Is there a reason why the stack would silently drop the following ACK which
> has been recieved and then forwarded to 192.168.254.1:5060 using UDP because
> it appears its never getting sent but theres no message on the console:
>
> The phone which has generated the ACK is on 192.168.254.2, it needs to get
> to 192.168.254.1 with resiprocate in the middle forwarding it
>
> ACK sip:200@xxxxxxxxxxxxx:5060;user=phone;transport=UDP SIP/2.0
> Via: SIP/2.0/UDP 192.168.254.2:5060;branch=z9hG4bK1a48c8a0e4d384fc
> To: <sip:200@xxxxxxxxxxxxxxx;user=phone>;tag=1467854400
> From: <sip:201@xxxxxxxxxxxxxxx;user=phone>;tag=3440312132
> Call-ID: 2973441516@xxxxxxxxxxxxx
> CSeq: 2 ACK
> Proxy-Authorization: Digest
> username="userB",realm="",nonce="1233689561:2c84eb790393f4d6ff51e9f5c7327e02",uri="sip:200@xxxxxxxxxxxxxxx",response="8a448d6f7131a5ed56968c497f817418",qop=auth-int,nc=00000001,cnonce="3aa1d532"
> User-Agent: Cisco-CP7912/8.0.0-060111A
> Content-Length: 0
>
> Ive been struggling for days to work out why the client was ignoring it, but
> now I dont think its actually being forwarded.
>
> Regards
> Andrew
>
>
> _______________________________________________
> resiprocate-users mailing list
> resiprocate-users@xxxxxxxxxxxxxxx
> List Archive: http://list.resiprocate.org/archive/resiprocate-users/
>