Using Obi100 as a gateway for other Obi devices
Zopa:
Hello,
I am trying to use older Obi100 I had around as a SIP gateway to Proxy connection to a VoIP provider. The reason I can't connect to a provider directly is because it's a wholesale type setup (Anveo Direct) requiring a static IP and I want to be able to proxy it like this.
Here is what I have setup on a Proxy (Obi100), let's call it Obi1:
SP1\X_InboundCallRoute = {1234567890>(<011:0ABCDEF>xx.):vg1}
SP1\X_UserAgentPort = 5063
SP1\ AuthUserName = 1234567890
SP1\ AuthPassword = Password
Voice Gateway 1\AccessNumber = SP1(sbc.anveo.com;ui=1234567890)
My client Obi (let's call it Obi2), also Obi100 is setup to route calls to Proxy Obi:
Physical Interfaces\PHONE\OutboundCallRoute = {(<011:06FPpE>xx.):vg1}
Voice Gateway 1\AccessNumber = sp1(111.112.113.114:5063)
Voice Gateway 1\DigitMap = (xx.)
Voice Gateway 1\AuthUserID = 1234567890
Voice Gateway 1\AuthPassword = Password
However, when I try to make a phone call from a phone connected to PHONE interface on Obi2, I see in call log that it's trying to connect to OBiTALK1 service instead of Voice Gateway 1 service I was trying to sent it to.
I would appreciate someone checking my setup and telling me where does OBiTALK1 coming from...
TIA
ianobi:
Here's a few ideas:
The routing to OBiTALK 1 is in fact an announcement most likely saying there is no call route available.
In both OBi's sp1 needs to be enabled and "active". Looks like sp1 in OBi1 may be is registered to anveo? OBi2 sp1 can be enabled using fake details such as:
Service Providers -> ITSP Profile A -> SIP -> ProxyServer : 127.0.0.1
Voice Services -> SP1 Service -> Enable : (checked)
Voice Services -> SP1 Service -> AuthUserName : (any letters or numbers not blank)
Voice Services -> SP1 Service -> X_ServProvProfile : A
Voice Services -> SP1 Service -> X_RegisterEnable : unchecked
In both OBi's set both vg1 passwords to blank.
In OBi 2 this digit map:
Voice Gateway 1\DigitMap = (xx.)
will not be able to process the letters that you are trying to send. Try this:
Voice Gateway 1\DigitMap = (@@.)
I'm not sure that will solve all your problems, but should get you some of the way.
Zopa:
Thank you for suggestions. I'm still having problems and wonder if this tidbit in the documentation may be reason why.
Using SPn as a Proxy for a SIP IP Phone -- (Available on OBi202/OBi302 only)
ianobi:
I don't believe that the "Using SPn as a Proxy" is relevant to your situation.
There is another routing problem in your setup:
OBi2:
Physical Interfaces\PHONE\OutboundCallRoute = {(<011:06FPpE>xx.):vg1}
This will remove 011 from the front of number xx. and replace it with 06FPpE. The resulting number "06FPpExx." is sent to OBi1.
OBi1:
SP1\X_InboundCallRoute = {1234567890>(<011:0ABCDEF>xx.):vg1}
This rule will only match numbers starting with 011. However the number you are sending from OBi2 starts with 06FPpE, so the call will fail.
I wonder if you might pick some simple test numbers to get this working before going for the final solution.
Zopa:
Thank you. I have also noticed the incorrect prefix remap and fixed it, however the setup still doesn't work for now.
Side questions:
Q1. What the relevance of SPx() in Voice Gateway setup? The syntax calls for something like SP4(blah.provider.com). In this manner I have it setup at my house to router to Anveo as sp4(sbc.anveo.com;ui=19998887777). At my house I have SP4 on my OBi202 set as Proxy and use it in VG1 as well. I, however, not fully follow why I put SP4 and not SP1 or 2 or 3.
Is SPx in front of the parenthesis there to match the incoming trunk where the request to VG is coming from, or is simply used to signifies which specific trunk to use?
Q2. "Using SPn as a Proxy" only working on OBi202 as per documentation. I read it to mean that using Obi in a proxy mode (X_Proxy parameter) is a function that's only available in OBi202. Are you saying that it is not so?
-----------------------------------------------------------------------
Client OBi100 (OBi2) config:
SP1 is set to Google Voice, I leave it alone.
SP2 is enabled:
Voice Services -> SP2 Service -> Enable : (checked)
Voice Services -> SP2 Service -> AuthUserName : 12223334444
Voice Services -> SP2 Service -> X_ServProvProfile : B
Voice Services -> SP2 Service -> X_RegisterEnable : unchecked <- (I set it, but I don't think it's needed to enable the trunk, as per documentation)
ITSP Profile B -> SIP -> ProxyServer : 127.0.0.1
Physical Interfaces\PHONE\OutboundCallRoute = {([011]xx.):vg1} …
Gateways and Trunk Groups\Voice Gateway1 -> Name : OBi Proxy
Gateways and Trunk Groups\Voice Gateway1 -> AccessNumber : sp2(1.2.3.4:5063) <- Static IP of Proxy OBi (OBi1)
Gateways and Trunk Groups\Voice Gateway1 -> DigitMap : (xx.)
Gateways and Trunk Groups\Voice Gateway1 -> AuthUserID : 12223334444
Gateways and Trunk Groups\Voice Gateway1 -> AuthPassword : Password
-----------------------------------------------------------------------
Proxy OBi200 (OBi1) config:
Voice Services -> SP1 Service -> Enable : (checked)
Voice Services -> SP1 Service -> AuthUserName : 12223334444
Voice Services -> SP1 Service -> AuthPassword : Password
Voice Services -> SP1 Service -> X_ServProvProfile : A
Voice Services -> SP1 Service -> X_RegisterEnable : unchecked
Voice Services -> SP1 Service -> X_InboundCallRoute : {12223334444>(xx.):vg1}
Voice Services -> SP1 Service -> X_UserAgentPort : 5063
Voice Services -> SP1 Service -> X_Proxy : (checked)
ITSP Profile A -> SIP -> ProxyServer : 127.0.0.1
Gateways and Trunk Groups\Voice Gateway1 -> Name : Anveo Direct
Gateways and Trunk Groups\Voice Gateway1 -> AccessNumber : sp1(sbc.anveo.com;ui=12345678900)
Gateways and Trunk Groups\Voice Gateway1 -> DigitMap : (<011:06FPpE>xx.|<06FPpE>xx.) <-- (note: This works perfectly as-is in my other setup, no need to change to "@@.")
Gateways and Trunk Groups\Voice Gateway1 -> AuthUserID : 12223334444
Gateways and Trunk Groups\Voice Gateway1 -> AuthPassword : (not set)
Note on Anveo prefix. They want it set like this:
Sending calls through Anveo Direct is easy!
1. Configure Outbound Trunk(s)
2. Send calls from authorized IPs to:
[PREFIX]PHONENUMBER@SBC.ANVEO.COM
where [PREFIX] is your custom configured prefix for the trunk and PHONENUMBER is destination phone number with country code.
Prefix is used to identify a particular trunk for calls received from a particular IP address.
When Anveo Direct receives a call Outbound Trunk will be matched by source IP and Prefix.
Prefix is optional but it is STRONGLY recommended.
Prefix must start with 0 and it must be 6 alphanumeric characters long.
For example: 0aBCdE and 012345 are both valid prefixes.
When sending calls to Anveo Direct Trunk you need to include prefix in the dialed phone number.
Navigation
[0] Message Index
[#] Next page