Version 7.2 313 Mediant 800B Gateway & E-SBC
User's Manual 15. Services
Content-Type: application/pidf+xml
2. The device extracts the ELIN number(s) from the "NAM" field in the XML message. The
"NAM" field corresponds to the <CompanyName> column in the Location Information Server
(LIS). The device supports up to five ELIN numbers per XML message. The ELINs are
separated by a semicolon. The digits of the ELIN number can be separated by hyphens (xxx-
xxx-xxx) or they can be adjacent (xxxxxxxxx), as shown below:
<ca:NAM>1111-222-333; 1234567890 </ca:NAM>
3. The device saves the From header value of the SIP INVITE message in its ELIN database
table (Call From column). The ELIN table is used for PSAP callback, as discussed later in
'PSAP Callback to Skype for Business Clients for Dropped E9-1-1 Calls' on page 315. The
ELIN table also stores the following information:
• ELIN: ELIN number
• Time: Time at which the original E9-1-1 call was terminated with the PSAP
• Count: Number of E9-1-1 calls currently using the ELIN
An example of the ELIN database table is shown below:
ELIN Time Count Index Call From
4257275678 22:11:52 0 2 4258359333
4257275999 22:11:57 0 3 4258359444
4257275615 22:12:03 0 0 4258359555
4257275616 22:11:45 0 1 4258359777
The ELIN table stores this information for a user-defined period (see 'Configuring the E9-1-1
Callback Timeout' on page 317), starting from when the E9-1-1 call, established with the
PSAP, terminates. After this time expires, the table entry with its ELIN is disregarded and no
longer used (for PSAP callback). Therefore, table entries of only the most recently
terminated E9-1-1 callers are considered in the ELIN table. The maximum entries in the
ELIN table is 100.
4. The device uses the ELIN number as the E9-1-1 calling number and sends it in the SIP
INVITE or ISDN Setup message (as an ANI / Calling Party Number) to the SIP Trunk or
PSTN.
An example of a SIP INVITE message received from an E9-1-1 caller is shown below. The SIP
Content-Type header indicating the PIDF-LO, and the NAM field listing the ELINs are shown in
bold typeface.
INVITE sip:911;phone-context=Redmond@192.168.1.12;user=phone SIP/2.0
From:
"voip_911_user1"<sip:voip_911_user1@contoso.com>;epid=1D19090AED;tag=d
04d65d924
To: <sip:911;phone-context=Redmond@192.168.1.12;user=phone>
CSeq: 8 INVITE
Call-ID: e6828be1-1cdd-4fb0-bdda-cda7faf46df4
VIA: SIP/2.0/TLS 192.168.0.244:57918;branch=z9hG4bK528b7ad7
CONTACT:
<sip:voip_911_user1@contoso.com;opaque=user:epid:R4bCDaUj51a06PUbkraS0
QAA;gruu>;text;audio;video;image
PRIORITY: emergency
CONTENT-TYPE: multipart/mixed; boundary= ------
=_NextPart_000_4A6D_01CAB3D6.7519F890
geolocation: <cid:voip_911_user1@contoso.com>;inserted-
by="sip:voip_911_user1@contoso .com"
Message-Body:
------=_NextPart_000_4A6D_01CAB3D6.7519F890
Content-Type: application/sdp ; charset=utf-8
To Next Page
Loading...
