sudden call disconnected

kingston · Brekeke Member Joined: 16 Oct 2006 Posts: 13

1. Brekeke Product Name and version:

Brekeke SIP Server v2.0.7.2/217

2. Java version:

1.5.0_11

3. OS type and the version:

Linux 2.6.9-42.ELsmp

4. UA (phone), gateway or other hardware/software involved:

UA: eyeBeam v1.5.5.1 build 30037
Gateway:
- Radvision N30 SIP Gateway
- Radvision P25M 3G Gateway

5. Select your network pattern from http://www.brekeke-sip.com/bbs/network/networkpatterns.html :

Similar to pattern 3 with the following additional network components:

1. Public IP is assigned to eyeBeam. All SIP Requests from UA will be submitted to NAT router first, and then forward it to OSS. NAT router port forwarding information as follow:

- Router's global IP address: 202.xxx.xxx.xxx
- SIP exchanger: UDP 5060
- RTP exchanger: 16384 - 65535

SIP server Interface Addresses:
- Interface address 1: 192.168.99.122
- Interface address 2: 192.168.96.7

2. When the request reached NAT Router, they will be forwarded to SIP Server. Routing path as follow:

voipwell.com · Posted: Fri Mar 30, 2007 8:46 am Post subject:

Hi,

I'm sorry but I'm not clear what the N30 and P25 are and what they are doing in between the internet and your phone. I would put the RTP port range in sip server back to 10000-10999. Make sure your force rtp relay to on in the sip server config. Make sure the router is forwarding ports 5060 and the above port range to sip server. You interface entries in the sip server should be 1) internal lan address, 2) external wan address only. Nat traversal should be ON in the sip server. The Disconnected by the system message sounds like an RTP Session Timeout. Brekeke is trying to send the bye message but it can't get thru because some path is not open. After a while it times out and writes the "disconnected by system".

A word of advice to solve your problem is to isolate it. Try removing devices from the path until your call works properly. You have a Ua with public address going to to a router then to Brekeke. Register a device on the brekeke sip server to complete the call. Then add devices one at a time between brekeke and your phone until it fails to see where the problem is.

Brkeke works very well with nat traversal. The only time it doesn't is when you lan address is numbered with wan ip addresses. That will confuse Brekeke. Although, they have a new configuration string that will now force nat traversal even if you are using wan addresses in your lan. I believe this is available in Version 2.

You could also download wireshark/ethereal to put on the brekeke server to see where the sip messages are having trouble getting thru.

Nick

kingston · Brekeke Member Joined: 16 Oct 2006 Posts: 13

Dear Nick,

Thank you for your prompt reply. I am so glad you gave me so many suggestions. It does help me a lot to figure out the root caused of the issue.

Please see my comment below:

voipwell.com · Posted: Sat Mar 31, 2007 5:24 pm Post subject:

Kingston,

I can not visualize your setup but I am concerned about the two lans you have connected to your brekeke server. Let's eliminate that as a problem by binding Brekeke to the lan you want to use for this problem call and restricting Brekeke from using the other lan address. In your sv.properties file in Program Files\Brekeke\pbx\webapps\proxy\WEB-INF\work\sv directory put the following lines in then reboot the server to make sure they get picked up.

net.net1.interface-restrict=xx.xx.xx.xx (where xx.xx.xx.xx) is the lan address that is not part of the call. This is a starting point since I can't see what is going on. If you would like to help me visualize it then put the situation in the following format for me.

This is what it should do.

eybeam(299.998.000.22) to ondo router (22.22.22.22) to ondo(192.168.1.22).

This is what it is doing.

eybeam to ondo router back to eyebeam.

thanks!

kingston · Brekeke Member Joined: 16 Oct 2006 Posts: 13

voipwell.com · Posted: Sun Apr 01, 2007 5:27 pm Post subject:

Kingston,

So the problem appears to be that the N30 sends an OK to Brekeke and Brekeke sends the Ack to the router instead of back to the N30 right?

It might be possible that the nat traversal is confused by the dual lan's. If that is the case then turn off rtp relay and nat traversal in the dial plan for the invites to N30. That may help.

In the deploy pattern for dial plan that invites N30 put
$nat = false
&net.rtp.follow.remoteaddr = false

If that doesn't work , then turn off nat traversal and rtp relay in the sip config. (reboot) then use the above two lines for the from and to pbx dial plans with true on both variables and in both dial plans. This will force rtp and nat traversal off on everthing except the to and from pbx which the eyebeam will use. You shouldn't have to do this though and it is not advisable to leave it this way since it does not accomdate all scenarios.

Nick

kingston · Brekeke Member Joined: 16 Oct 2006 Posts: 13

Dear Nick,

kingston · Brekeke Member Joined: 16 Oct 2006 Posts: 13

Dear Nike,

The issue is fixed. What I do is defined the dial plan and explicitly defined the destination ip as 192.168.96.4 as follow:

Matching Patterns

 
	  Code:
	
$request=^INVITE

To=sip:(.+)@

Deploy patterns:

$auth=false

$target=192.168.96.4

[color=red]To=sip:%1@192.168.96.4[/color]

All requests including ACK & BYE from eyebeam can now forwarded to N30 (192.168.96.4) and vise versa.

You do help me a lot in solving the problem. Thanks a lot.

voipwell.com · Posted: Mon Apr 02, 2007 5:13 am Post subject:

Kingston,

Your welcome. Helping you exposes me to more ways that people use Brekeke. Being able to modify the sip headers which is what you did to solve your problem, is one of the most powerful features that seperate Brekeke from the rest of the market. You have obtained enough knowledge to see you thru most problems you will encounter. I look forward to seeing you back here helping others when you have time.

Thanks for using Brekeke!

Nick