On 10/12/06, Klaus Darilion <[EMAIL PROTECTED]> wrote:
Support for Location and Emergency Call Routing would be great. This
includes several steps:
1. Getting the location. This can be done for example with DHCP
Geo coordinates:
http://ietf.org/rfc/rfc3825.txt
http://www.ietf.org/internet-drafts/draft-schnizlein-geopriv-binary-lci-00.txt
civil coordinates
http://www.ietf.org/internet-drafts/draft-ietf-geopriv-dhcp-civil-09.txt
or via L7 protocols like HELD or RELO:
http://tools.ietf.org/wg/geopriv/draft-schulzrinne-geopriv-relo-00.txt
http://www.ietf.org/internet-drafts/draft-winterbottom-http-location-delivery-03.txt
2. The next step would be to map an emergency service URN to the
responsible PSAP (public safety access point).
Possible service URNs are defined in
http://www.ietf.org/internet-drafts/draft-ietf-ecrit-service-urn-05.txt
This will be mapped to PSAP URIs (using the current location as input)
using the LOST protocol (Probably there will be LOST servers provided
for example by government):
http://www.ietf.org/internet-drafts/draft-ietf-ecrit-lost-01.txt
3. The SIP client will call the URI received from LOST and providing its
location either using location-by-reference using the "Geolocation"
header defined in
http://www.ietf.org/internet-drafts/draft-ietf-sip-location-conveyance-04.txt
or sending the location as PIDF-LO object using a second body in the
INVITE message:
http://www.rfc-editor.org/rfc/rfc4119.txt
I think this would be feature where openwengo could stand out from the
crowd of other SIP phones.
Feature creep...
could we have a working, standard compliant, SIP soft phone _before_
even thinking about stuff like this?
_______________________________________________
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel
