1. Brekeke Product Name and version: latest
2. Java version: latest
3. OS type and the version:
4. UA (phone), gateway or other hardware/software involved:
5. Select your network pattern from http://www.brekeke-sip.com/bbs/network/ ... terns.html : 9
6. Your problem:
I want to register a softphone extension from outside through BSS on our trixbox.
Current dialplan:
Matching pattern:
$request=^REGISTER
Deploy pattern:
To=sip:trixbox@
$auth=false
$action=register
&net.registrar.thru.allow=true
---------------------
to=sip@trixbox@ is a registered connection from the trixbox (this works, because I use the same setup to do outbound dialing from trixbox to BSS)
Every time I get a 403 not authorized. I don't know what to change on the dialplan the registration to be passe on to the trixbox machine.
To test I've made captures on the BSS and the trixbox machine. The trixbox machine does not even get the registration request from it has to do with the dialplan currently in BSS.
any tips?
Through Registration
Moderator: Brekeke Support Team
I just read my post again, and I realise I was very unclear.
Situation:
softphone on laptop with public ip wants to register to trixbox (located in private network) through BSS which is available on public ip also.
softphone (public)-> BSS (public)-> trixbox (private)
Trixbox has registered itself to BSS.
Everything on the inside to trixbox works. Calling via bss to external providers / DTMF etc is all ok. Incoming calls do also work.
The only thing missing is the ability to connect a softphone through BSS on trixbox.
Every dailplan I know of results in either the softphone registering on BSS (which I do not want) or a 403 not allowed header.
My settings:
configuration -> sip:
upper registration:off
thru registration: on
Dial plan:
Match:
$request=^REGISTER
$addr=from public ip
Deploy:
$auth=false
$action=register
&net.registrar.thru.allow=true
&net.registrar.upper.addr=sodasterisk@
(sodasterisk is the user that is registered from trixbox to BSS)
The following happens:
Softphone is registered, but not to trixbox..everything stays at the BSS, and nothing is forwarded to the trixbox.
Any thoughts ?
Situation:
softphone on laptop with public ip wants to register to trixbox (located in private network) through BSS which is available on public ip also.
softphone (public)-> BSS (public)-> trixbox (private)
Trixbox has registered itself to BSS.
Everything on the inside to trixbox works. Calling via bss to external providers / DTMF etc is all ok. Incoming calls do also work.
The only thing missing is the ability to connect a softphone through BSS on trixbox.
Every dailplan I know of results in either the softphone registering on BSS (which I do not want) or a 403 not allowed header.
My settings:
configuration -> sip:
upper registration:off
thru registration: on
Dial plan:
Match:
$request=^REGISTER
$addr=from public ip
Deploy:
$auth=false
$action=register
&net.registrar.thru.allow=true
&net.registrar.upper.addr=sodasterisk@
(sodasterisk is the user that is registered from trixbox to BSS)
The following happens:
Softphone is registered, but not to trixbox..everything stays at the BSS, and nothing is forwarded to the trixbox.
Any thoughts ?
Megamuch..
Try this.
---------------------
[Matching Patterns]
$request = ^REGISTER
$regaddr( "sodasterisk" ) = (.+)
$addr = from public ip
[Deploy Patterns]
$auth = false
$action = register
&net.registrar.upper.allow = true
&net.registrar.upper.addr = %1
---------------------
It this case, &net.registrar.upper.addr will be sodasterisk's IP address/port.
Try this.
---------------------
[Matching Patterns]
$request = ^REGISTER
$regaddr( "sodasterisk" ) = (.+)
$addr = from public ip
[Deploy Patterns]
$auth = false
$action = register
&net.registrar.upper.allow = true
&net.registrar.upper.addr = %1
---------------------
It this case, &net.registrar.upper.addr will be sodasterisk's IP address/port.