Hi Naveen, I think it is based on individual UAC implementation where probably they assume that a device has to be registered before it can place a call for ensuring that only registered devices in the user-network place the call. This is probably done for preventing un-authorized devices from originating call in a user-network.
But protocol gives flexibility w.r.t registration.Say for example if we have a subscriber which is statically registered ( with registered always ) on the registrar server. Then in that case it does not really need to send a REGISTERation request prior to placing a call. Normally the static registration option is used by gateways in the network, but it is possible on the server side to create a pre-registered subscriber with static ip. So from the UAC side it should be flexible in considering that UAS may have created this subscriber as statically registered device with no registration required ( pre-registered ) option and thus allow placing calls. But as I said above it may have been done with specific intent in the UAC implementation That is my thoughts :) Regards, Indresh K Singh -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Naveen Chandra Sent: Thursday, March 29, 2007 12:07 AM To: [email protected] Subject: [Sip-implementors] INIVITE sent to outbound proxy We have a UAC which is configured with a registrar and an outbound proxy (registrar and outbound proxy are physically separate entities). If we disable registrations to be sent to registrar , then INIVITE is not being sent to outbound proxy. Is this implementation correct ? can anybody point where in 3261 this behaviour is defined. AFAIK, registrations only make sense if a proxy receives a request and wants to route to proper UAS. -Naveen _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
