Hi, There is no connectivity issue between the server and the IPv6 client. The client can register properly and now I can even make a call to the IPv4 client but the IPv6 client does not recieve any RTP packets from the router once session is established. So I have come half way to solve my problem.
________________________________ From: Sammy Govind govoiper@gmail.com To: nunu abe nunu_abe@yahoo.com Cc: SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - Users Mailing List sr-users@lists.sip-router.org Sent: Tuesday, January 10, 2012 2:09 PM Subject: Re: [SR-Users] RTPproxy on Kamailio 3.2.1 difficulty.
yes sure it is, verify that your Kamailio/RTpproxy server can properly ping IPv6 destination and has a default route set for those.
On Tue, Jan 10, 2012 at 5:37 PM, nunu abe nunu_abe@yahoo.com wrote:
Hi,
Thank you for pointing this out. I looked into it and I found out that the packets were larger than 1500 bytes, so I set the max MTU size to be 1650 on the kamailio-rtpproxy server, and there is no more complainig about the packet size. However, I can not see the packets being modified by the rtpproxy server pass my router.The router I am using is juniper srx-240, I tried to allow all packets going in/out of these interfaces but no luck. It seems its routing problem.
From: Sammy Govind govoiper@gmail.com To: nunu abe nunu_abe@yahoo.com Cc: SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - Users Mailing List sr-users@lists.sip-router.org Sent: Tuesday, January 10, 2012 7:04 AM
Subject: Re: [SR-Users] RTPproxy on Kamailio 3.2.1 difficulty.
I'm not better at IPv6, not yet atleast but if the caller is getting a timeout response and you see repeated SIP traces for IPv6 Client then the obvious is that your server is trying to route the call to IPv6 client and there is not route to destination. Thats why packets are timed out.