Future 9 - Just 911
azrobert:
I was going to post the below, but I decided to try it first before posting.
My phone rings, but I have no audio.
Since I previously got this working my ISP upgraded me to a faster service and I have a new modem.
I don't know if the problem was caused by the change in service or I'm forgetting something.
I don't have time to play with this now.
I didn't finish the post.
I was going to explain about dynamic IP addresses.
First the disclaimer:
The following worked for me.
This setup routes the call using an SIP URI.
The OBi devices are famous for having audio problems when routing calls using a URI, so you might have problems.
The SP slot you route calls to must be defined as SIP. This example is using SP4, so it must be defined as SIP.
Login to your Callcentric account.
Click Call Treatments
Click Add a new Call Treatment
Click the circle next to This Number
Enter anything@xx.xx.xx.xx:5063
xx.xx.xx.xx is your public IP Address
If you don't know your public IP address go here: http://www.whatsmyip.org/
On the right side of the page click This Number under Called Number
From the drop down menu select the number
Click Save
In your Router:
Port Forward 5063 to the IP address for your OBi202
Port Forward RTP ports 17100 thru 17198 to the IP address for your OBi202
This is 99 ports.
The RTP ports are found in the OBi202 here:
Service Providers -> ITSP Profile D -> RTP -> LocalPortMin/Max
Edit:
I resolved the audio problem.
The call was being forwarded to an SP registered to a local PBX.
Changing it to an SP registered to a provider on the internet fixed the problem.
Everybody's network seems to act a little differently, but mine requires the SP to be register to a provider outside my local network.
A changing public IP addresses isn't a problem if you use dynamic DNS.
Get a free account here: http://freedns.afraid.org/
If your router doesn't have a service to update the IP address, the OBi can update it.
See: http://www.obitalk.com/forum/index.php?topic=4797.msg36667#msg36667
My public IP address has changed once in the last 12 years.
We have had several power outages and I've re-booted the modem a bazillion times and still only one IP change. The only time it changed is when we had an extended power outage.
Not all ISPs will act the same.
You should also assign a static IP address to your OBi.
This setup might seem overwhelming to a newbie, but it isn't that hard.
Edit2:
To block scanners change the SP4 X_InboundCallRoute to:
{>anything:ph}
After you replace Callcentric with a new service do the following to allow inbound calls from the new service and Callcentric:
{>anything:ph},{>AuthUserName:ph}
You can eliminate the 1st rule by changing the Callcentric Call Treatment to:
AuthUserName@xx.xx.xx.xx:5063
Now change SP4 X_InboundCallRoute to:
{>AuthUserName:ph}
Mango:
Your problem was probably solved by forwarding your RTP ports. Configuring Callcentric to route via SIP URI adds points of failure as it will stop working when your ISP changes your IP address. It is also a security risk and subjects your device to scanner calls.
If you have problems with receiving nuisance calls that do not appear in Callcentric's call records, reconfigure your setup to use registration and remove your port forward for 5063 - but keep your RTP port forward.
If you must use SIP URI forwarding, you should use a high X_UserAgentPort (between 20000 and 65535) and also configure your X_InboundCallRoute as follows:
X_InboundCallRoute: {>('anything'):ph}
I have used 'anything' as the username to be consistent with your example SIP URI.
Note that it may be helpful to register to your 911 service provider in case the 911 operator needs to call you back.
SteveInWA:
Forgetting about Future 9, and given that sir_rob already has Callcentric service, there's no need to set up any "this may or may not work" configurations. Just route 911 calls to one of the two existing Callcentric SP slots. It's one box to click on the portal. As long as you're subscribed to an outbound calling plan of some sort, that includes E911, it will call 911.
giqcass:
When I wrote my initial reply I thought you had F9 functioning reliably at some point. I believed your issues were with getting help with this particular configuration. Now that I have seen your other post on DSLR and know you never even had the basic service working I wouldn't suggest using it for emergency calls. You would never know if something breaks till you need it. I would go with SteveInWA and just keep it simple by using CC for 911.
As others said above you only need one 911 account through CC. Each line can be set up to use that account for 911 and still function independently in all other situations. The good part is it's a heck of a lot simpler then anything else we could suggest.
sir_rob:
Thanks for all of the advice.
Here is how I have it set up. Hopefully this is the optimal solution.
-Two Google Voice accounts for all outgoing calls on two different lines
-One CallCentric account with two free DID's.
-The first CC DID rings on the first GV account.
-The second CC DID uses a call treatment for forward to an extension that is registered on my OBI-202 as the inbound line for the second GV account.
-I started the 911 service from CC today and in the OBI configuration checked the 911 box for both the default and extension CC services.
Hopefully that is done properly. Again, thanks for the help!
Navigation
[0] Message Index
[#] Next page
[*] Previous page