Hi, Thank you all.
So I conclude that this behavior on the Part of UA (SIP phone) is illegal. Call won't break. RFC as such doesn't say anything about this scenario. This is implementation defined behavior. Regards, Abu. 1............... UA is responsible for refreshing the bindings it has established, so the behavior you described is illegal. Assume the behavior of your UA is allowed just for the sake of discussion,when a dialog established, all the following requests are in dialog, should be constructed according to rfc 3261, 12.2, request-uri is built from remote target and route set, so the binding it registered previous is not needed. 2........... The call stays... The role of the registrar is to maintain bindings of user agents to their address of record. Whether the registrar and the proxy resides in the same domain space is irrelevant. Registration expiration has no role in mid call operations. You should check your user agent, though. It should be refreshing its registration even if its busy with a call. 3................. PRJ>> The call would stay. Even if the SIP UA failed to refresh the Registration bindings with the Registrar server it does not have any effect on the mid calls operations. Even if a SIP UA is not registered with any Registrar server it can receive incoming calls unless SIP client specific implementation is stopping it & the calling party knows the current location of the SIP client by some other means. Registration is just a mechanism for keeping your current location updated/associated with your AOR & also it does not matter if your Proxy & Registrar are of same domain. _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
