Hello Kamailio Team,
We have been using kamailio successfully for some time now to test the functionality of our S/W. Recently we started facing an issue with kamailio (I don't know whether it's a known issue or not). So thought to drop an email with the details to see whether we can get a fix for that. The scenario for the problem set is as follows.
We are running the latest KAMAILIO release 3.3.1 (02nd Aug 2012) release. When we send out the REGISTER request from the client, the server it turn returns 200 OK messages to us then we start the call i.e. INVITE with SDP to other client which is also sends REGISTER request to the same SIP Server. The call gets CONNECTED and the RTP flow starts both ways peer - to - peer from one side to another. Now if we move from one subnet of the same network to another subnet of the same network so the last field of the private IP address changes from say 192.168.1.XXX to 192.168.1.YYY then at this time kamailio crashes and this we can see happening all the time with this scenario. Can you please help us fix this problem. If logs are required then please tell us how can we generate those and then we can send out these to you (if required).
Thanks & Best Regards Saurabh Srivastava
On 15.10.2012 12:41, Saurabh Srivastava wrote:
We are running the latest KAMAILIO release 3.3.1 (02nd Aug 2012) release. When we send out the REGISTER request from the client, the server it turn returns 200 OK messages to us then we start the call i.e. INVITE with SDP to other client which is also sends REGISTER request to the same SIP Server. The call gets CONNECTED and the RTP flow starts both ways peer - to - peer from one side to another. Now if we move from one subnet of the same network to another subnet of the same network so the last field of the private IP address changes from say 192.168.1.XXX to 192.168.1.YYY then at this time kamailio crashes and this we can see happening all the time with this scenario. Can you please help us fix this problem. If logs are required then please tell us how can we generate those and then we can send out these to you (if required).
Whose IP address is changed? The IP address of the Kamailio server?
How do you change it? When Kamailio is running?
When is Kamailio crashing? During IP address change or during startup? Or during message processing?
regards Klaus
The IP address of the clients are changing not for KAMAILIO. KAMAILIO is ruuning on static IP that does not change ever. The problem occurs when the two clients whose address change as they move to different subnet on the same network (say from X subnet to Y, but in same network i.e. LAN).
On Mon, Oct 15, 2012 at 4:28 PM, Klaus Darilion < klaus.mailinglists@pernau.at> wrote:
On 15.10.2012 12:41, Saurabh Srivastava wrote:
We are running the latest KAMAILIO release 3.3.1 (02nd Aug 2012) release. When we send out the REGISTER request from the client, the server it turn returns 200 OK messages to us then we start the call i.e. INVITE with SDP to other client which is also sends REGISTER request to the same SIP Server. The call gets CONNECTED and the RTP flow starts both ways peer - to - peer from one side to another. Now if we move from one subnet of the same network to another subnet of the same network so the last field of the private IP address changes from say 192.168.1.XXX to 192.168.1.YYY then at this time kamailio crashes and this we can see happening all the time with this scenario. Can you please help us fix this problem. If logs are required then please tell us how can we generate those and then we can send out these to you (if required).
Whose IP address is changed? The IP address of the Kamailio server?
How do you change it? When Kamailio is running?
When is Kamailio crashing? During IP address change or during startup? Or during message processing?
regards Klaus
Hi Saurabh!
Your problem description is not detailed enough. If a client changes IP addresses, at first Kamailio can not even notice (as RTP sind peer-to-peer). Only if one of the clients sends requests, Kamailio may notice the IP address change. Thus:
- what activity is performed by the clients on IP address change? (reINVITE, REGISTER, BYE ....)
- If Kamailio crashes, it will usually report why/where it crashes. Configure your system to write core dumps as described here: http://www.kamailio.org/dokuwiki/doku.php/troubleshooting:corefiles
Then send the backtrace of the coredump to the mailing list.
- Most times crashes are triggered by processing an incoming message. Please post the message which caused the crash (if so).
regards Klaus
On 15.10.2012 13:23, Saurabh Srivastava wrote:
The IP address of the clients are changing not for KAMAILIO. KAMAILIO is ruuning on static IP that does not change ever. The problem occurs when the two clients whose address change as they move to different subnet on the same network (say from X subnet to Y, but in same network i.e. LAN).
On Mon, Oct 15, 2012 at 4:28 PM, Klaus Darilion <klaus.mailinglists@pernau.at mailto:klaus.mailinglists@pernau.at> wrote:
On 15.10.2012 12:41, Saurabh Srivastava wrote: We are running the latest KAMAILIO release 3.3.1 (02nd Aug 2012) release. When we send out the REGISTER request from the client, the server it turn returns 200 OK messages to us then we start the call i.e. INVITE with SDP to other client which is also sends REGISTER request to the same SIP Server. The call gets CONNECTED and the RTP flow starts both ways peer - to - peer from one side to another. Now if we move from one subnet of the same network to another subnet of the same network so the last field of the private IP address changes from say 192.168.1.XXX to 192.168.1.YYY then at this time kamailio crashes and this we can see happening all the time with this scenario. Can you please help us fix this problem. If logs are required then please tell us how can we generate those and then we can send out these to you (if required). Whose IP address is changed? The IP address of the Kamailio server? How do you change it? When Kamailio is running? When is Kamailio crashing? During IP address change or during startup? Or during message processing? regards Klaus