Hi all,
after some discussions on the usage of the Service URN it seems that
most people in ECRIT agreed to move forward with the initially planned
approach. Below, you can find a description of how the Service URN would
be used in various scenarios.
Are there any objections?
Ciao
Hannes
---------------------
== End Host Procedures ==
* UA does not recognize the emergency call.
To: Dial String
Request URI: Dial String
No Route header
* UA runs LoST and determines the PSAP URI:
Request URI: Service URN
To: Service URN
Route Header: PSAP URI
* UA does not run LoST but recognizes the emergency call.
Request URI: Service URN
To: Service URN
No Route header
== Proxy Procedures ==
* Incoming request contains Service URN; Proxy runs LoST
and determines the PSAP URI
--- Input:
Request URI: Service URN
To: Service URN
No Route header
--- Output:
Request URI: Service URN
To: Service URN
Route Header: PSAP URI
* Incoming request contains Dial String; Proxy runs LoST
and determines the PSAP URI:
--- Input:
Request URI: Dial String
To: Dial String
No Route header
--- Output:
Request URI: Service URN
To: Dial String
Route Header: PSAP URI
Remark: "Dial String" refers to http://tools.ietf.org/html/rfc4967
_______________________________________________
Sip mailing list https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use [EMAIL PROTECTED] for questions on current sip
Use [EMAIL PROTECTED] for new developments on the application of sip
