News:

On Tuesday September 6th the forum will be down for maintenance from 9:30 PM to 11:59 PM PDT

Main Menu

e911 Backup/Failover

Started by Everton, November 04, 2011, 12:44:45 AM

Previous topic - Next topic

Everton

I was up late and decided to access my OBi110 directly through its web Portal.  The System Status Page shows:

SP1 Service Status:  Connected   (GV is setup on SP1)

SP2 Service Status:  Retrying..... (VOIP.ms is setup on SP2 for e911 and toll Free outgoing)

OBiTALK Service Status:  Normal (User Mode)

When I logged into my VOIP.ms account, the Portal: Home Page shows that No registration found for the Registration Status.

What this means if we had dial 911 at that specific time, the call would fail (or would it?).  After multiple refresh of the OBI110 status page, it still shows SP1 as retrying.  I reboot the OBi110 and SP2 became Registered.  This has happen before...not sure what could cause this or now to prevent it from happening.

What I would like to do is to use either SP1 (GV) and Voice Gate 3 (CallWithUs - Unregistered) as a backup for e911 by dialing a non-emergency number, 1aaa2345678, where I can at least reach 911, even though the 911 center would not have the address information.  How can I modify the DigitMap/OutboundCallRoute to provide some form of failover via SP1 (GV) and Voice Gate 3?  Additionally, I have a subaccount setup on VOIP.ms can I could potentially setup on Voice Gateway 4 and use that as a Failover or use the same primary account in an unregistered state.

--------------------------------------------------------------------------------------------
Background Info:
I have a Broadband connection (Comcast) Modem connected to a DDWRT-Router (WRT54G-TM) and the OBi110 connected to one of the 4 ports.  I have STUN Enable (stun.ideasip.com) on the OBi110.

PHONE Port: -> DigitMap:
([1-9]x?*@@.|[1-9]|[1-9][0-9]|911|411|**0|***|#|**1(Msp1)|**2(Msp2)|**3(Mvg3)|**8(Mli)|**9(Mpp)|(Mpli))

PHONE Port: -> OutboundCallRoute:
{([1-9]x?*@@.):pp},{(<#:>):li},{911:sp2},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**3:>(Mvg3)):vg3},{(<**8:>(Mli)):li},{(<**9:>(Mpp)):pp},{(Mpli):pli}

PHONE Port: -> PrimaryLine:  SP1 Service

ITSP Profile A: -> DigitMap:  
(<123:1aa1234567>|<411:18003733411>|<**3>1876xxxxxxxS0|<**3>011xx.|<**2>1800xxxxxxx|<**2>1888xxxxxxx|<**2>1877xxxxxxx|<**2>1866xxxxxxx|<**2>1855xxxxxxx|(Mste))

RonR

Everton,

There's no real failover implmented in the OBi.  The following change to the OutboundCallRoute, however, should provide alternatives if SP2 or SP1 are not registered or connected when the 911 call is placed.


Physical Interfaces -> PHONE Port -> DigitMap:

([1-9]x?*@@.|[1-9]|[1-9][0-9]|911|**0|***|#|**1(Msp1)|**2(Msp2)|**3(Mvg3)|**8(Mli)|**9(Mpp)|(Mpli))

Physical Interfaces -> PHONE Port -> OutboundCallRoute:

{([1-9]x?*@@.):pp},{(<#:>):li},{911:sp2},{(<911:1aaa2345678>):sp1},{(<911:1aaa2345678>):vg3},
{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**3:>(Mvg3)):vg3},
{(<**8:>(Mli)):li},{(<**9:>(Mpp)):pp},{(Mpli):pli}

Physical Interfaces -> PHONE Port -> PrimaryLine:  SP1 Service

Service Providers -> ITSP Profile A -> General -> DigitMap:
 
(<123:1aaa1234567>|<411:18003733411>|<**3>1876xxxxxxxS0|<**3>011xx.|
<**2>18(00|88|77|66|55)xxxxxxx|(Mste))


I also took the liberty of removing 411 from the PHONE Port DigitMap as it serves no purpose and I revised the ITSPA DigitMap for a more compact handling of toll-free numbers.

Ostracus

Quote from: RonR on November 04, 2011, 09:35:19 AM
Everton,

There's no real failover implmented in the OBi.  The following change to the OutboundCallRoute, however, should provide alternatives if SP2 or SP1 are not registered or connected when the 911 call is placed.
------
Physical Interfaces -> PHONE Port -> PrimaryLine:  SP1 Service


Isn't one of the tricks if SP1 or 2 might be unavailable to set the above to a trunk instead?

RonR

Quote from: Ostracus on November 04, 2011, 10:49:08 AM
Isn't one of the tricks if SP1 or 2 might be unavailable to set the above to a trunk instead?

I don't know what that means.

Ostracus

Quote from: RonR on November 04, 2011, 10:52:10 AM
Quote from: Ostracus on November 04, 2011, 10:49:08 AM
Isn't one of the tricks if SP1 or 2 might be unavailable to set the above to a trunk instead?

I don't know what that means.


Physical Interfaces -> PHONE Port -> PrimaryLine:  SP1 Service

One of my choices is Trunk Group 1. I believe I dug the example from one of your previous posts.

RonR

Setting PrimaryLine to Trunk Group 1 would affect all other calls but would not affect 911 calls due to the OutboundCallRoute rule:

{911:sp2}

Changing this rule to:

{911:tg1}

and settiing the Trunk Group 1 TrunkList to : sp2,sp1,vg3

poses a problem of how to get the number sent to be 911 if  SP2 is used or 1aaa2345678 is SP1/VG3 is used.

Everton

Thanks Ron for your assistance as usual.  I did make the changes you suggested and change the password on SP2 which causes the VOIP.ms Trunk to not register(or disable the SP2 Trunk).  I then change 1aaa2345678 to my Mobile number to test and it kept telling me that I "...could not get a response from the service provider".  So with SP2 not registered, it did not move to the next SP1 or VG3.  Any further thoughts as to why it doesn't work?  Thx.


Quote from: RonR on November 04, 2011, 09:35:19 AM
Everton,

There's no real failover implmented in the OBi.  The following change to the OutboundCallRoute, however, should provide alternatives if SP2 or SP1 are not registered or connected when the 911 call is placed.


Physical Interfaces -> PHONE Port -> DigitMap:

([1-9]x?*@@.|[1-9]|[1-9][0-9]|911|**0|***|#|**1(Msp1)|**2(Msp2)|**3(Mvg3)|**8(Mli)|**9(Mpp)|(Mpli))

Physical Interfaces -> PHONE Port -> OutboundCallRoute:

{([1-9]x?*@@.):pp},{(<#:>):li},{911:sp2},{(<911:1aaa2345678>):sp1},{(<911:1aaa2345678>):vg3},
{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**3:>(Mvg3)):vg3},
{(<**8:>(Mli)):li},{(<**9:>(Mpp)):pp},{(Mpli):pli}

Physical Interfaces -> PHONE Port -> PrimaryLine:  SP1 Service

Service Providers -> ITSP Profile A -> General -> DigitMap:
 
(<123:1aaa1234567>|<411:18003733411>|<**3>1876xxxxxxxS0|<**3>011xx.|
<**2>18(00|88|77|66|55)xxxxxxx|(Mste))


I also took the liberty of removing 411 from the PHONE Port DigitMap as it serves no purpose and I revised the ITSPA DigitMap for a more compact handling of toll-free numbers.


RonR

Everton,

It looks like the OBi isn't as smart as I thought it was.  I assumed a service not being ready would be skipped in the OutboundCallRoute and the next rule would be tried, but it appears not to work that way and simply returns the error message.

RonR

#8
The only working solution I've come up with requires the use of a Trunk Group, but it's a little involved.


Physical Interfaces -> PHONE Port -> DigitMap:

((Mtg4)|([1-9]x?*@@.|[1-9]|[1-9][0-9]|**0|***|#|**1(Msp1)|**2(Msp2)|**3(Mvg3)|**8(Mli)|**9(Mpp)|(Mpli))

Physical Interfaces -> PHONE Port -> OutboundCallRoute:

{(Mtg4):tg4},{([1-9]x?*@@.):pp},{(<#:>):li},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},
{(<**2:>(Msp2)):sp2},{(<**3:>(Mvg3)):vg3},{(<**8:>(Mli)):li},{(<**9:>(Mpp)):pp},{(Mpli):pli}

Physical Interfaces -> PHONE Port -> PrimaryLine:  SP1 Service

Service Providers -> ITSP Profile A -> General -> DigitMap:
 
(<E911:1aaa2345678>|<123:1aaa1234567>|<411:18003733411>|<**3>1876xxxxxxxS0|<**3>011xx.|
<**2>18(00|88|77|66|55)xxxxxxx|(Mste))

Service Providers -> ITSP Profile B -> General -> DigitMap : (<E911:911>|...)

Voice Services -> Gateways and Trunk Groups -> Voice Gateway3
DigitMap : (<E911:1aaa2345678>|...)

Voice Services -> Gateways and Trunk Groups -> Trunk Group4
Name : 911
TrunkList : sp2,sp1,vg3
DigitMap : (<E>911|E911)


I have this implmented using a TrunkList of : li,tg1

(Trunk Group 1 has a TrunkList of : sp1,sp2)

911 goes out the LINE Port, but rolls over to SP1 using a replacement number if the LINE Port is disconnected.  If SP1 is not connected, it rolls over to SP2 using a replacement number.

If you support 911 calls from an external phone connected via SIP, don't forget its InboundCallRoute rule:

{pap2>911:sp2}   ->   {pap2>(Mtg4):tg4}

Everton

#9
I made the changes suggested and using by Mobile Number for (1aaa2345678), I first disable SP2. and dial 911.  The call was sent to my Mobile Number as required....GREAT!!!!  

I then proceeded to disable SP1, in addition to the already disable SP2.  I now getting ...."no service available to receive your call", which means the VG3 rollover is not working as plan.  Maybe I am not following you where you said:

Quote from: RonR on November 04, 2011, 06:50:54 PM
I have this implmented using a TrunkList of : li,tg1

(Trunk Group 1 has a TrunkList of : sp1,sp2)

911 goes out the LINE Port, but rolls over to SP1 using a replacement number if the LINE Port is disconnected.  If SP1 is not connected, it rolls over to SP2 using a replacement number.


In my case, I have nothing connected to the LINE port and I have:

Trunk Group 1 has a TrunkList of : sp1,sp2

I to not have any reference to tg1.  Where would I enter tg1 in your previous post....I think this is where the disconnect is!

Again, I have everything identical to what you described in your previous post.  We are close, I just need to get the VG3 rollover working as an additional backup.  Thanks again for your assistance!


RonR

Everton,

You shouldn't be using TG1 nor be concerned with it.  I happen to use TG1 as my PrimaryLine so I used it in my TG4 TrunkList.  I was simply illustrating that I was using this concept successfully here.

Gimme a minute or two and I'll test a scenario using a VG and see if it presents a problem.

You did remove the 911 rules from the PHONE Port DigitMap and OutboundCallRoute, correct?

RonR

#11
Everton,

Using a TG4 TrunkList of : li,sp1,vg3

Everything works as advertised.  With the LINE Port disconnected, 911 calls go out SP1 (with a substitute number).  With a bad password on SP1 so it doesn't register, 911 calls go out VG3 (with a substitute number).

It's a keeper here.

Everton

#12
Here are my settings right now (copied directly from the OBi110, with actual numbers masked):

Physical Interfaces -> PHONE Port -> PrimaryLine:  SP1 Service

Physical Interfaces -> PHONE Port -> DigitMap:
((Mtg4)|[1-9]x?*@@.|[1-9]|[1-9][0-9]|911|411|**0|***|#|**1(Msp1)|**2(Msp2)|**3(Mvg3)|**8(Mli)|**9(Mpp)|(Mpli))


Physical Interfaces -> PHONE Port -> OutboundCallRoute:
{(Mtg4):tg4},{([1-9]x?*@@.):pp},{(<#:>):li},{911:sp2},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**3:>(Mvg3)):vg3},{(<**8:>(Mli)):li},{(<**9:>(Mpp)):pp},{(Mpli):pli}

Service Providers -> ITSP Profile A -> General -> DigitMap:
(<E911:1aaa2345678>|<123:1aaa1234567>|<411:18003733411>|<**3>1876xxxxxxxS0|<**3>011xx.|<**2>18(00|88|77|66|55)xxxxxxx|(Mste))

Service Providers -> ITSP Profile B -> General -> DigitMap :  (<E911:911>|(Mste))

Voice Services -> Gateways and Trunk Groups -> Voice Gateway3
DigitMap : (<E911:1aaa2345678>|<011:>xx.|xx.|(Mste))

Voice Services -> Gateways and Trunk Groups -> Trunk Group4
Name : 911
TrunkList : sp2,sp1,vg3
DigitMap : (<E>911|E911)
.
.
.
I had to add 411 to the "Physical Interfaces -> PHONE Port -> DigitMap" since I added the "18(00|88|77|66|55)xxxxxxx" to "Service Providers -> ITSP Profile A -> General -> DigitMap:", otherwise I get ..."....the number you dialed, 411, was rejected by your service provider, the reason was 404".  If I add the number 411 to "Physical Interfaces -> PHONE Port -> DigitMap", the 411 calls are routed properly to sp1, instead of attempting to send the call through sp2. where it is rejected!

Quote from: RonR on November 05, 2011, 11:28:15 AM
Everton,

You shouldn't be using TG1 nor be concerned with it.  I happen to use TG1 as my PrimaryLine so I used it in my TG4 TrunkList.  I was simply illustrating that I was using this concept successfully here.

Gimme a minute or two and I'll test a scenario using a VG and see if it presents a problem.

You did remove the 911 rules from the PHONE Port DigitMap and OutboundCallRoute, correct?


RonR

#13
1. You didn't remove the old 911 rules from PHONE Port DigitMap and OutboundCallRoute.

2. 411 doesn't need to be in the PHONE Port DigitMap.

The following should correct both of these problems:


Physical Interfaces -> PHONE Port -> DigitMap:
((Mtg4)|[1-9]x?*@@.|[1-9]|[1-9][0-9]|**0|***|#|**1(Msp1)|**2(Msp2)|**3(Mvg3)|**8(Mli)|**9(Mpp)|(Mpli))

Physical Interfaces -> PHONE Port -> OutboundCallRoute:
{(Mtg4):tg4},{([1-9]x?*@@.):pp},{(<#:>):li},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**3:>(Mvg3)):vg3},{(<**8:>(Mli)):li},{(<**9:>(Mpp)):pp},{(Mpli):pli}

Service Providers -> ITSP Profile A -> General -> DigitMap:
(<E911:1aaa2345678>|<123:1aaa1234567>|<411:**218003733411>|<**3>1876xxxxxxxS0|
<**3>011xx.|<**2>18(00|88|77|66|55)xxxxxxx|(Mste))

Everton

Both 411 and 911 failover to SP1 in the event of an unregistered SP2 Trunk and failover to and Voice Gateway 3 in event of both SP1 and SP2 being "unavailable", works perfectly now!!!  I also realize that I cannot disable SP2 and get VG3 to work.  I have to enter a improper password and let SP2 become unregistered, but still "enabled" so since the functionality of the Voice Gateway depends on SP2.

Thanks Ron for your great directions/knowledge base.  I really like the setup I have now, since it allows an alternative 911 path in situations where my main e911 is down for some reason.

RonR

Quote from: Everton on November 05, 2011, 01:34:28 PM
Both 411 and 911 failover to SP1 in the event of an unregistered SP2 Trunk and failover to and Voice Gateway 3 in event of both SP1 and SP2 being "unavailable", works perfectly now!!!

Are you sure about 411?

411 should simply be using SP2 as you wished all 800 numbers to do.  There shouldn't be any failover of 411 going on.

Everton

Quote from: RonR on November 05, 2011, 01:53:39 PM
Quote from: Everton on November 05, 2011, 01:34:28 PM
Both 411 and 911 failover to SP1 in the event of an unregistered SP2 Trunk and failover to and Voice Gateway 3 in event of both SP1 and SP2 being "unavailable", works perfectly now!!!

Are you sure about 411?

411 should simply be using SP2 as you wished all 800 numbers to do.  There shouldn't be any failover of 411 going on.


Sorry Ron, what I meant to say is 411 is working as designed, using SP2 trunk for outgoing when 411 is dialed.  911 failover......... is also working the way it should as described before!!  Thx again.

RonR

Thanks for clearing that up.  Glad to hear everything is working as desired.

This was a good exercise as I like having 911 backed up by two additional routes also.

lhm.

#18
Everton wrote:

"What I would like to do is to use either SP1 (GV) and Voice Gate 3 (CallWithUs - Unregistered) as a backup for e911 by dialing a non-emergency number, 1aaa2345678, where I can at least reach 911, even though the 911 center would not have the address information.  How can I modify the DigitMap/OutboundCallRoute to provide some form of failover via SP1 (GV) and Voice Gate 3?  Additionally, I have a subaccount setup on VOIP.ms can I could potentially setup on Voice Gateway 4 and use that as a Failover or use the same primary account in an unregistered state."

Why?  When you can use gv911.com with <911S0:1424279xxxx> in your Digitmap. Assuming GV# is registered with gv911 you can then caller id spoof that # for Trunk Group failover with/to VoIP.ms and CallWithUs without having to use a non-emergncy #.

(for others Callcentric allows for this as well,  http://www.callcentric.com/features/external_caller_id