Can't Call registered Users on a Local Network.

Discuss any topic about Brekeke SIP Server.

Moderator: Brekeke Support Team

Post Reply
Vincent
Posts: 25
Joined: Thu Aug 27, 2009 9:53 am

Can't Call registered Users on a Local Network.

Post by Vincent »

1. Brekeke Product Name and version: BPBX 2.4.9.0

2. Java version:1.6

3. OS type and the version:Win 2008 Server.

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

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

6. Your problem:Can't call users that are registered with a local ip (192.168.0.xx).

With any of the below dial plans I can call registered users on a global ip:

[Matching Pattern]
$request = ^INVITE
To = sip:0(.+)@

[Deploy pattern]
$auth = false
To = sip:%1@
$register.contact.remote=true
$continue=false

This other dial plan also works but not for users that are registered with a local ip:

[Matching Pattern]
$request = ^INVITE
To = sip:0(.+)@

[Deploy pattern]
$auth = false
To = sip:%1@
$net.rtp.follow.remoteaddr=true
$continue=false

I've tried the suggested solution on Brekeke wiki but it didn't help.Here's the suggested solution:

When UA2 is on a local network, [NAT traversal] > [Keep address/port mapping] should be set to ON in the [Configuration] menu to resolve NAT traversal on UA2 side. The setting doesn't matter if UA2 can use STUN, and STUN supports the router(NAT)'s type on UA2's side.

I'd appreciate any tips or clues that could help me resolve this issue.

Thanks,
Vincent.
ambrosio
Posts: 215
Joined: Thu Mar 27, 2008 12:20 pm

Post by ambrosio »

$register.contact.remote=true
must be
&register.contact.remote=true

$net.rtp.follow.remoteaddr=true
must be
&net.rtp.follow.remoteaddr=true

use '&' instead of '$' because they are environment variables.
Vincent
Posts: 25
Joined: Thu Aug 27, 2009 9:53 am

Post by Vincent »

Hello Ambrosio,

Sorry for the typo,I actually did use the environment variable character "&" in this line of statement :
[&net.rtp.follow.remoteaddr=true] but did otherwise in

"$register.contact.remote=true ". I'll try it and see if it works.

Thanks.
Vincent
Posts: 25
Joined: Thu Aug 27, 2009 9:53 am

Post by Vincent »

I've tried the environment variable prefix but it didn't help.Could this be a policy issue?
ambrosio
Posts: 215
Joined: Thu Mar 27, 2008 12:20 pm

Post by ambrosio »

You need to have "&register.contact.remote=true" in both rules.
Post Reply