MS Teams Emergency Calling - ELIN update for 911

 Hello All

Hope everyone is doing good, Today we are going to cover , how to update the ELIN for the existing subnets or validated addresses in emergency calling location.

One of our customers  decided to use Session Border Controllers that include Emergency Location Identification Number (ELIN) applications.

What is ELIN

An Emergency Location Identification Number (ELIN) is a ten digit DID number usually we have to  purchase from the local exchange carrier (LEC), and is one way for organizations to provide specific location information to the public safety answering point (PSAP) for a 911  call.

933 is for stimulating the 911 and automated address verification.

Scenario :  

• Confirmed that the ELIN identity of the emergency is updated through the below command and validated that the ID is synced in. However, on SBC side ELIN is empty in the INVITE for US locations
• Set-CsOnlineLisCivicAddress -CivicAddressId XXX-XXXX-XXX2a7ce7fa04 -Elin +1XXXXXXXXXXX
• Collected the calling logs and verified that ELIN tag is Null, which could mean ELIN number would not have been configured properly for this location on MS Teams side
• To validate if the ELIN ID is Collected the output for below and noticed ELIN address is missing:
• 
• Set-CsOnlineLisLocation -LocationId "XXXXXXX-XXXXX-XXXXXX" -Elin +1XXXXXXXXXXXXXX
• Tried updating the ELIN address from the above command , however, i noticed error below  and realised that we cannot update the ELIN number for the validated address locations

Resolution

Engaged Microsoft support and the back end team [PG} and confirmed the failure in propagating of ELIN ID. 

Performed a back end sync and confirmed ELIN number got updated and start populating in SBC logs

Moral of the Story / Leason Learned

As a Microsoft Teams admin, we cannot update / edit the ELIN numbers for the validated address in emergency address calling location, and we should engage Microsoft to propagate the ELIN from the back end. 

Microsoft confirmed this feature is going to update in feature, to provide the privileges  to MS  teams admin, however there  is no ETA.

I hope this would helpfully to all and Happy Learning 😊