Thru Registration not working

Discuss any topic about Brekeke SIP Server.

Moderator: Brekeke Support Team

Post Reply
jdavis017
Posts: 7
Joined: Thu Sep 03, 2020 9:55 am
Location: Dallas, Texas

Thru Registration not working

Post by jdavis017 »

1. Brekeke Product Name and Version:
Brekeke Sip Server 3.10.6.5
2. Java version:
Redhat OpenJDK 11.0.11-1
3. OS type and the version:
Windows Server 2019 Standard
4. UA (phone), gateway or other hardware/software involved:
FusionPBX 4.2.2
5. Your problem:

I am attempting to use BSS as an SBC front-ending FusionPBX with multiple domains. Thru Registration is giving me the fits and I can find no examples whatsoever. I am first wanting extensions to work and I can get phones registered but when I dial the extension, the pbx says the person at extension 1234 is not available. I am able to record a message and retrieve it from the other extension.

Here is the dialplan example:

-------------
matching Pattern Init_Register:

$request = ^REGISTER
To = (.+)@publicdomain.com

Deploy:

&net.registrar.thru.allow = true
$continue = true

--------------
matching Pattern Register_Thru:

$request = ^REGISTER
To = (.+)@publicdomain.com

Deploy:

$b2bua = true
$auth = false
To = sip:%1@privatedomain.com

--------------
matching Pattern Call_Invite: (just using extensions right now)

$request = ^INVITE
To = sip:(.+)@publicdomain.com
From = sip:(.+)@publicdomain.com

Deploy:

$b2bua = true
$auth = false
From = sip:%2@publicdomain.com
To = sip:%1@privatedomain.com

--------------
The Init_Register does nothing. I can Disable it with the same results.
Fratto
Posts: 4
Joined: Mon Nov 24, 2008 5:57 pm

Post by Fratto »

Are these domains, publicdomain.com and privatedomain.com, different PBX servers?

It seems both "Init_Register" and "Register_Thru" rules have the same Matching Pattern line. So rule "Register_Thru" will not be executed.

To = (.+)@publicdomain.com


If you want to forward SIP-REGISTER to privatedomain.com, use the DialPlan rule like the following.

Rule: Register_Thru
[Matching Pattern]
$request = ^REGISTER
To = @privatedomain.com

[Deploy Pattern]
$auth = false
&net.registrar.thru.allow = true
$continue = true
jdavis017
Posts: 7
Joined: Thu Sep 03, 2020 9:55 am
Location: Dallas, Texas

Post by jdavis017 »

The public domain, from the internet, as an example is publicdomain.com. This is where stations are located and outside the local network where the BSS is.

The firewall will port forward by hostname to the BSS.

The privatedomain.com is internal and on the same network as the BSS, not external. It actually has a domain assigned by an internal DNS server using A records like. mypbx.internal.local or whatever is assigned.

The servers see each other, but I am assuming the thru registration does not work because the To = domain is not the same as the targeted server.
Fratto
Posts: 4
Joined: Mon Nov 24, 2008 5:57 pm

Post by Fratto »

Does the SIP client use Brekeke SIP Server as an outbound proxy?
There are several ways to meet the requirement.

Following rules are based on your original DialPlan rules.

Rule: REG privatedomain
[Matching Patterns]
$request = ^REGISTER
To = @privatedomain.com

[Deploy Patterns]
$auth = false
&net.registrar.thru.allow = true
$continue = true

Rule: REG publicdomain
[Matching Patterns]
$request = ^REGISTER
To = @publicdomain.com

[Deploy Patterns]
$auth = false
&net.registrar.thru.allow = true
$continue = true

Rule: INVITE privatedomain
[Matching Patterns]
$request = ^INVITE
To = sip:(.+)@privatedomain.com

[Deploy Patterns]
$auth = false
$b2bua = true
To = sip:%1@privatedomain.com

Rule: INVITE publicdomain
[Matching Patterns]
$request = ^INVITE
To = sip:(.+)@publicdomain.com

[Deploy Patterns]
$auth = false
$b2bua = true
To = sip:%1@publicdomain.com
Post Reply