Hi, >Why would you think Emergency communications systems would not register?
My understanding is that in many countries they are connected more like network equipment than user equipment, so in those cases they may not always register. (And, of course, if the ECS is in the PSTN it won't register, since the MGC does not register.) But, I am not an expert on this, so maybe I'm wrong. But, it's not really relevant for the problem we are trying to solve, so we don't need to discuss it futher within that context. Regards, Christer > > I think we have cross domain issues, but a UA in an ECS > registers with a registrar in that ECS domain. The caller > registers with a registrar in its domain. > > I don't see a problem with the proposed solution. I think it > will work. > > Brian > > > -----Original Message----- > > From: Christer Holmberg (JO/LMF) > > [mailto:[EMAIL PROTECTED] > > Sent: Wednesday, June 13, 2007 4:03 PM > > To: Ted Hardie; Jonathan Rosenberg; IETF SIP List > > Subject: RE: [Sip] UA Loose Routing: Emergency example > > > > > > Hi, > > > > >>This is not very relevant to the loose route solution as such, but > > just > > >>a small comment on the emergency service use-case. > > >> > > >>I am not sure whether the emergency service centers will always > > >>register, and if they don't loose route of course does > not solve the > > >>problem. > > >> > > >>Regards, > > >> > > >>Christer > > > > > >Hi Christer, > > > > > >Can you expand on the issue here? I'm afraid I didn't > understand it > > from this message. > > > > As said in the draft, the loose route mechanism can only be used if > > the UA has registered and indicated support of the loose > route mechanism. > > > > So, entities that do not register will not be able to use > the mechanism. > > And, to my understanding the ESCs will not always register, > which mean > > it's not possible to use the loose route mechanism to forward the > > initial request to them. > > > > Regards, > > > > Christer > > > > > > _______________________________________________ > > 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 > > _______________________________________________ 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
