[Serdev] TCP Blocking Connect issue

[Andrew Mee]

However SER is not sending a packet to 

<sip:support at 192.168.2.253:16501;maddr=192.168.2.11;transport=tcp>

When viewing on NGREP there is no packet that comes from 192.168.2.253 to 192.168.2.11:16501 as you would expect...
port 16501 is available and listening on the UA

Perhaps what I am seeing goes back to my original comment then that this is a TCP issue...
perhaps the TCP connection is not looking for an existing connection to send the packet to and is trying to create another connection hence a blocking error? I am guessing here btw.

Andrew


Juha Heinanen wrote:

>Andrew Mee writes:
>
> > T 192.168.2.28:1148 -> 192.168.2.253:5060 [AP]
> >   ACK 
> > sip:support at 192.168.2.253;transport=tcp;ftag=ac5d7c39647143ed8365ef1c5f
> >   aaaf16;lr=on SIP/2.0..Via: SIP/2.0/TCP 
> > 192.168.2.28:16532..Max-Forwards: 70
> >   ..From: "HS User" 
> > <sip:test2 at 192.168.2.253>;tag=ac5d7c39647143ed8365ef1c5fa
> >   aaf16;epid=a98f8fc72f..To: 
> > <sip:support at 192.168.2.253>;tag=04445215ea6d4c70
> >   b7c5bdadd5db0598..Call-ID: 
> > 793c8868bce64e82b7e097dd204d57f6 at 192.168.2.28..C
> >   Seq: 1 ACK..Route: 
> > <sip:support at 192.168.2.253:16501;maddr=192.168.2.11;tran
> >   sport=tcp>..User-Agent: RTC/1.2..Content-Length: 0....
> > 
> >  From here it tries to (as assumed) ACK to 192.168.2.11:10227 and then 
> > falls down... instead of SER realising that 192.168.2.11:10227 doesn't 
> > exist and then trying 192.168.2.11:16501, it just fails.
>
>as jiri said, when ser routes ack, it doesn't do any location lookup.
>it just forwards the ack according to route header which specifies:
>
><sip:support at 192.168.2.253:16501;maddr=192.168.2.11;transport=tcp>
>
>this is in conformance with rfc3261.
>
>-- juha
>  
>


-- 
Andrew Mee