Outbound SIP trunks - Locations for emergency services

[AuraPS]

Hi,

I'm guessing I'm not the only one who has come up against the issue of a centralised global Avaya platform
using a centralised SIP trunk from one location servicing many countries so that routing short codes and emergency services are correct.

Eg.
Say an agent in New York, Ext. 5208 (in Location 10 NR Map) has a 'pub unk' table entry to output a unique ANI/CLI +12127545208 on trunk 10

Trunk 10 = (CM<>SM1) --> to SBCE --> To SIP Provider

The SIP Provider will recognise the ANI/CLI as a US / New York call and route any short code or emergency services to the relevant area.

If agent 5208 goes to another office in another country (UK - Location 20 NR Map) and makes the same call, how can I get the SIP provider to know the user is now in the UK but still show their original ANI/CLI as above.

What SIP headers are relevant and how are they automatically changed and applied at the Avaya Level depending on the users location.
Is this done at CM or SM-SMGR Level

Any help will be much appreciated

Many Thanks

 

[kyle555]

You use ELE in the network map to send a specific DID per IP range to the PSAP.
If the user happened to be in the UK, why would you want the PSAP to know their usual DID from NY? Wouldn't you want to send a DID representative of the office the user is at?

Look into SM and it's emergency call handling. If a dial pattern is dialed and is of type emergency, it overrides some restrictions but it also can use the ELIN provided by an ELIN SIP Entity.

So, if you had a RedSky or Sentry or something that was monitoring registrations/IPs/MACs/SNMP polling switchports and stuff, that e911 system with it's ELIN SIP entity can pump to SM a list of ELINs to use for each registered user, and if SM gets a dialed # of type emergency, then it would substitute whatever number the ELIN SIP entity told it to use. And that could change if buddy is calling from a registered set in the UK or the US.
Remember - you can have up to 10 things registered against your SIP handle - each with their own registration ID. So, if buddy went to the UK, nothing precludes his SIP phone from being on his desk in NY and still being able to call 911. And Buddy can log in to a SIP phone in the UK and that registration can be handled and understood differently than the US one so dialing 999 from that SIP phone would follow emergency rules for the site he is at.

If you have an international SIP provider, don't they have any information about what they can handle/what they expect?

 

[AuraPS]

Hi Kyle,

Thanks, that's a great help, my example isn't telling the whole story - I am talking SIP trunk routing only here, the handsets are H.323

We have a service desk that want to send out CLI of their business DDI (lets say a Paris Number) - If a customer calls back on this numbers the agent might be located in Paris or Madrid. We need to make sure that the Madrid agent (showing a Paris CLI) get's through to the Spanish emergency services not French.

So the ELE in NR MAP ....any extension in that NR dialling an emergency number will apply CLI of the ELE entry in the PUB-UNK table right
(how does the system tie 999, 911 or 112 to the ELE is it based on the 'call type = emer' in the location ARS table ???)

My next question - is it possible to send a different CLI based on a number dialled - I'm guessing this can be manipulated in SM-SMGR

Thanks again

 

[kyle555]

CLI is per the ip-network-map for the subnet, or more specifically, for the station.
For SIP phones, something like a Redsky populates SM with the ELINs for each registration. For H323, it'll use AES's SMS service to configure CM and granularly set ELE on a per set basis.
The trigger for CM to use ELE is if the call is of type alrt in AAR/ARS. The trigger for SM to use the ELIN value populated at registration is whether the dial pattern is of type emergency.

Can you send different CLI based on dialed #? Sure, your public table can specify on a per-trunk group basis, so when I'm in Canada and dialing out trunks in the UK in trunk group 1, my CLID in the public table for trunk 1 sends +44xxx and when I'm calling out trunks in France in group 2, my entry for France sends a local French number. That won't be applying to emergency calls though.

And be careful - CM will step on your idea if things are inconsistent. As in, if you hard-code the location of an IP phone in location 2 but the registered IP is in the network map in region1/location1, when that guy dials 911, CM's going to say "I need to send this out location 2 per the user's configuration, but he has an IP in location 1 - that's obviously inconsistent"

Either way - it doesn't matter if people reach your users in Madrid calling numbers from anywhere in the world. When they call out normally, they use the public table. When they dial emergency numbers, ELE/ELIN/whatever else will override the public table.

Also, there's a little feature on by default about emergency callback. If the ELE is 555-555-1234 and 911 is calltype alrt, should the system see 911 call back 555-555-1234 within 10 minutes, it'll route the call to the phone that made the 911 call - whether that phone has a DID or not - that way the police can call back if the line drops.

 

[AuraPS]

Cool, thanks for your detailed explanation much appreciated