<div dir="ltr"><p class="MsoNormal"><span lang="EN-US">Hello Aldo,</span></p>
<p class="MsoNormal"><span lang="EN-US"> </span></p>
<p class="MsoNormal"><span lang="EN-US">We used the
open source Sipp to simulate this Sip client.</span></p>
<p class="MsoNormal"><span lang="EN-US"> </span></p>
<p class="MsoNormal"><span lang="EN-US">In
accordance with i2 architecture- NENA,
the SIP client must send the location information using two ways:</span></p>
<p class="MsoNormal" style="margin-left:36pt"><span lang="EN-US">-<span style="font-stretch:normal;font-size:7pt;font-family:'Times New Roman'">
</span></span><span dir="LTR"><span lang="EN-US">Directly into your body using the PIDF-LO (RFC 4119) Location Object
(LO).</span></span></p>
<p class="MsoNormal" style="margin-left:36pt"><span lang="EN-US">-<span style="font-stretch:normal;font-size:7pt;font-family:'Times New Roman'">
</span></span><span dir="LTR"><span lang="EN-US">Or by reference with Location Key
(LK) through of new header in SIP: Geolocation (RFC 5031), VPC uses this Key to
obtain the location information in consultation with the LIS (Location
Information Server).</span></span></p>
<p class="MsoNormal"><span lang="EN-US"> </span></p>
<p class="MsoNormal"><span lang="EN-US">These
informations should be got by User Agent caller running an LCP - Location
Convey Protocol. LCP can be implemented adapting the DHCP (RFC 4776 / RFC 6225)
or via HELD protocol (RFC RFC 5985). The implementation has to be done in UAC because of LIS with its LO information is located in own ISP(Internet server
provider) that the UA has access network, becoming easier addressing this LIS.</span></p>
<p class="MsoNormal"><span lang="EN-US"> </span></p>
<p class="MsoNormal"><span lang="EN-US">In i2
specification the interface between call server (in case the OpenSIPS) and LIS
isn't expected, because of the difficulty of implementing. The difficulty is in
various factors such as privacy, device identification and mainly because the
call server (OpenSIPS) doesn't know the address of appropriate LIS, It is
required of a search algorithm of this LIS in the source ISP (the RFC 5896/7216
describes this algorimos, however this algorithm is not as trivial).</span></p>
<p class="MsoNormal"><span lang="EN-US"> </span></p>
<p class="MsoNormal"><span lang="EN-US"><b>In practice</b>,
I can not provide any SIP client that has implemented the LCP. </span></p>
<p class="MsoNormal"><span lang="EN-US">For testing
we used the Sipp to simulate this Sip client using these mentioned RFCs, is
attached the XML scenario file that we used in Sipp, with the new Geolocation
header and with PIDF-LO in the body, the OpenSIPS needs only one to handle the
emergency call.</span></p>
<p class="MsoNormal"><span lang="EN-US"> </span></p>
<p class="MsoNormal"><span lang="EN-US">best
regards</span></p>
<p class="MsoNormal"><span lang="EN-US"> </span></p>
<p class="MsoNormal"><span lang="EN-US">Evandro Villaron</span></p></div>