Re: [Sip-implementors] Distinguishing Forked and Looped scenarios atSIP proxy

2009-04-19 Thread Shanbhag, Somesh (NSN - IN/Bangalore)
At the very first, the transaction for 1st INVITE would have been created. And when second INVITE comes, since the branch_id is different definitely it will be a different transaction. But it would eventually map to dialog created by first INVITE. But if the SIPProxy supports spiral call flows,

Re: [Sip-implementors] Distinguishing Forked and Looped scenarios at SIP proxy

2009-04-19 Thread Iñaki Baz Castillo
El Domingo, 19 de Abril de 2009, Ashwath Kumar escribió: > These two are distinguised by only one parameter that is > branch=z9hG4bK-22034-1-1 > in via header. > > Now how the proxy will consider this ? > Will Proxy treat it as loop ? Why a loop? A loop occurs when a proxy routes a request to hi

Re: [Sip-implementors] Major issues with TLS port-numbers

2009-04-19 Thread Iñaki Baz Castillo
El Domingo, 19 de Abril de 2009, Franz Edler escribió: > Thank's Iñaki, > > > Hope it's useful for you. > > Yes. Thanks for the detailed elaboration. It is clear now and I remember on > the mechanism responsible for that. > > In my case I do not have a NAT environment, but I found that the SIP serv

[Sip-implementors] Distinguishing Forked and Looped scenarios at SIP proxy

2009-04-19 Thread Ashwath Kumar
Hi All, I am sending TWO INVITE messages to a proxy . = 1st INVITE == INVITE sip:2...@1.20.20.33:5060 SIP/2.0 Via: SIP/2.0/UDP 1.1.1.25:7766;branch=z9hG4bK-22034-1-0 From: sipp ;tag=22034SIPpTag001 To: sut Call-ID: 1-22...@1.1.1.25 CSeq: 1 INVITE Conta