Skip to main content

Custom Trunk for e911 Configuration

Posted by ottcomputing on Sun, 03/13/2016

Hi everyone,

We're almost done evaluating the MTE version of ThirdLane and are really pleased. The one thing we're trying to test is the configuration of e911.

In our FreePBX configs we were using Custom Trunks with a custom Dial String of:

SIP/ourusername_911@gateway1.update911.info

We want to do the same in ThirdLane but the only kind of trunk we're allowed to create is a SIP, IAX or DAHDI, no Custom option even though the wiki seems to think it should be there.

The integration guide is here:

https://update911.info/sp/downloads/VoIP%20911%20Integration%20-%202010…

But the interesting bit is:

Calls should be connected to your_rid_911@gateway1.update911.info or your_rid_911@gateway2.update911.info

For example, if you use asterisk and your rid is “abctelecom”, configure the
emergency dial plan as follows:

[outboundcontext]
exten => 911,1,Macro(voip911)
[macro-voip911]
exten => s,1,NoOp(Connecting a 911 call for ${CALLERID(all)})
exten => s,n,Dial(SIP/abctelecom_911@gateway1.update911.info)
exten => s,n,Dial(SIP/abctelecom_911@gateway2.update911.info)
exten => s,n,Playback
(im-sorry&cannot-complete-network-error&hangup-try-again)
exten => s,n,Congestion

Any help from the gurus out there?

Thanks!
Chris


Submitted by eugene.voityuk on Mon, 03/14/2016 Permalink

Hi Chris! You can create custom script in script library, name it voip911, and copy-paste yours code to pbx commands frame:

exten => s,1,NoOp(Connecting a 911 call for ${CALLERID(all)})
exten => s,n,Dial(SIP/abctelecom_911@gateway1.update911.info)
exten => s,n,Dial(SIP/abctelecom_911@gateway2.update911.info)
exten => s,n,Playback(im-sorry&cannot-complete-network-error&hangup-try-again)
exten => s,n,Congestion

Don't forget to mark checkbox, that it can be used in outbound routes and save.
Then go to outbound routes and configure route where Pattern will be 911 and in "Associated Script", select voip911. That's it.