Hi Andrey On SIP AS side sip stack is running on port 5060, then this packet send to Application running over on top of it. Is their any issue with this scenario? In SIP packet its 5060 only. Port is changed only in UDP/TCP packets. But I think their shouldn't be anything wrong with this cause SIP Stack utilizes only sip packets (inside of UDP). And SER is replying to it.
Regards Kamal Mann
-----Original Message----- From: Andrey Kuprianov [mailto:andrey.kouprianov@gmail.com] Sent: Monday, November 06, 2006 11:52 AM To: serusers@iptel.org Subject: Re: [serusers]: trusted table(permissions module)
Hi Kamal,
I noticed one strange thing in your traces. INVITE from SIP-AS is sent from port 4141 (!) to port 5060, but 100 and 407 response from SER is sent back to port 5060 (not port 4141)! Can you, please, explain why?
Andrey.
On 11/6/06, Kamal.Mann@t-systems.com Kamal.Mann@t-systems.com wrote:
Hi Andrey Please find ethereal packet capture enclosed. SER n/w dump is
'SER_SERVER' and SIP_AS n/w dump is 'SAS_SERVER'.
SER IP = 10.25.119.155 SIP AS IP = 10.25.119.156 To URI is registered at SER end (dilip) From URI is Application Name (example) and neither created nor
registered (WakeUpService) with SER.
Thanks in anticipation Kamal Mann
_______________________________________________ Serusers mailing list Serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers