Plase do capture on the SER server on linux cooked interface called "any", I suspect that your ser is forwarding the request to itself and at the moment it won't catch using the trusted table.
More comments inline.
On Mon, 2006-11-06 at 14:47 +0700, Andrey Kuprianov wrote:
Hi,
See inline
On 11/6/06, Kamal.Mann@t-systems.com Kamal.Mann@t-systems.com wrote:
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?
I think there might be... I just think there should be some consistency between your SIP and UDP/TCP packets. If UDP source port is 4141, for example, then your Contact header (and From header too), should have this port. If someone else has some good ideas, plz, comment.
What Andrey describes is symetric signalling, what we see in the capture is asymetric signalling.... it is not the problem. It is possible (not when you are behind NAT) to use 5060 for receiving incoming requests and responses and use other ports to send requests.
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.
Your ethereal traces on SER side show 100 and 407 responses are marked as black and red color (i use ethereal 0.99.x). That means something is wrong.
Due to UDP checksum not beeing correct.
Michal
Regards Kamal Mann
Regards,
Andrey.-----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
Serusers mailing list Serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers