Hello, Paul Kyzivat wrote: > Also, you typically don't address the registrar. Instead you address the > domain of your AOR in the REGISTER. (I.e. a register for > sip:[EMAIL PROTECTED] is sent to sip:atlanta.com.) Often that is a proxy > that either also acts as a registrar, or else has local policy to route > REGISTER requests to a specific registrar node. So when you talk about > sending OPTIONS to the registrar, I guess you mean alice would send it > to sip:atlanta.com. That would presumably be responded to by the > atlanta.com "proxy" (but acting as a UA). If there is a separate > registrar, atlanta.com probably would not route the OPTIONS to it.
... RFC 3665 specifies SIP basic call flow examples. In these examples the registrar is addresses as "REGISTER sips:ss2.biloxi.example.com SIP/2.0". In this case you do not have the problem mentioned above (proxy might not forward message...), because the separate registrar has an own SIP-URI. Is this true? Thanks, Holger _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
