Routing 911 over SIP from BCM to CS1000 and out PRI @ CS1000 Guidance

[Stacyjo5]

I have a customer with 60+ BCM400/BCM450 sites - each site has at least 1 analog trunk (originally set up for 911 calls), they also have SIP trunks back to a CS1000 R7 for all of there incoming/outgoing calls as well as 5 digit dialing between all sites. The customer is requesting that we set up 911 calling at the BCM location to route across the SIP trunks and out the PRI trunks at the CS1000. I have looked through all the Avaya E911 documentation and I cannot find the specifics on setting this up. The BCMs are not SRGs, so I cannot use ERL to identify the sets.
Any guidance would be greatly appreciated.
And if Fletch wanted to weigh in I would be eternally grateful!
I am of the opinion that the requested solution is a bad idea so if there is any steadfast reasoning you could offer that I could convey to my customer that would great too.

Thanks in advance!

 

[trvlr1]

Reason not to: In the event of a fire, they may be able to dial 911 but be incapacitated and not able to speak. If calls are going out locally, the number and thus the address can be quickly collected and authorities despatched. If this happens in a scenario where you are shipping it to another site for delivery, authorities will get the wrong address info and dispatch to the wrong location.

 

[Stacyjo5]

Thanks for your response! I am actually looking for the set up that will carry the CLID from the BCM location, across to the CS1000 and then the CS1000 will send out the correct CLID so that the 911 operator relates the call to the correct address. I am wondering if there is a solution that allows this, something along the same lines as ERL settings on an IP phone at a branch office. I am still researching some sort of zone settings or something ERL like on the SIP trunks to specify where the call is coming from. Relying on the caller to provide the address information to the 911 operator is not an option.
Thanks again!

 

[allenmac]

One important thing to consider/test is to determine what the outbound calling line ID looks like on a call from the BCM that hops onto the PSTN at a CS1000 site.

If the outbound Calling line id is the BCM phone's DID, then half the battle is won.

If the calling line ID is good, then you need to consider how you will be shipping the BCM calls to their proper PSAP, or will you just pass calls to 911 under the belief that it is better to get any PSAP rather than no PSAP?

 

[Stacyjo5]

On a normal outbound call the CLID from the BCM is correct (the local BCM OLI is set on a per phone basis), however, when a 911 call is made from the BCM and sent across the SIP trunks to the CS1000 the CS1000 recognizes the call as a 911 (I can see it in the D-channel messaging) and then sends it out with the local (CS1000) default CLID instead of sending it through with the BCM CLID. The d-channel messaging shows the BCM name, the OLI it send and the fact that it is a 911 call, but the CS1000 still sends out the CS1000 CLID instead of the BCM.

I hope that's not as confusing as I think it is!!

Thanks!

 

[allenmac]

I'm not confused (I think...)

So bottom line is that on 911 calls the outbound CLID does not reflect the DID of the BCM phone, so the PSAP will not know that the caller is at a remote location.

 

[Stacyjo5]

Correct! (I think...)

Normal outbound calls from BCM, across SIP and out CS1000 PRI show CLID of main BCM number.

911 calls from BCM, across SIP and out CS1000 PRI show CLID of main CS1000 number.

I need to figure out how to stop the CS1000 from taking control of those calls and stripping the BCM info.

 

[allenmac]

I think the zone based dialing stuff may help you out with that.

 

[Stacyjo5]

Thanks Allenmac - I've been reading up on the Zone Based Dialing, but I am having trouble finding anything speaking specifically to the BCM. I understand ZBD in the PBX world, but the SMB relationship has not shown itself just yet!

Thanks again!
Stacy

 

[allenmac]

You may be right. I think it is used more in configuring the behavior of Survivable Media Gateway, Branch Offices or SIP Line gateways, rather than Virtual Trunk connections.

Sorry.