Hi, I don't have any objections. I have only clarified how it works in IMS, and why. It's up to you to decide what/if to do with that information.
Also, in the ECRIT documentation, I think you should indicate that your solution does not work with MGCs that route the destination number based on the Request-URI (that is not an IMS specific MGC behavior). I do have one question for clarification, though: in the examples there is only one Route header, pointing towards the PSAP. IF there are intermediate entities that also need to be in the path, is it assumed that the one inserting the PSAP Route has information about those, in order to insert Route headers also for those entities if needed? Regards, Christer > -----Original Message----- > From: Hannes Tschofenig [mailto:[EMAIL PROTECTED] > Sent: 10. syyskuuta 2007 10:21 > To: IETF SIP List; ECRIT > Subject: [Ecrit] Service URN Usage (UA Loose Routing) > > 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 > > > > _______________________________________________ > Ecrit mailing list > [EMAIL PROTECTED] > https://www1.ietf.org/mailman/listinfo/ecrit > _______________________________________________ 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
