OK. I have now seen two replies saying that the call stays up, and one
saying that the UA is broken.
As the two saying the call will stay up have explained, from a sip
standards perspective there is nothing incorrect about the UA and no
reason why the call should be taken down. The registration is only there
to facilitate the initial routing of calls to the UA. Once a session is
established, loss of registration need have no effect.
However, there are systems that do tie registration to other things. In
some cases the authentication done at registration time is used to
authorize the ability to both make and receive calls, receive services
from proxies, etc. Any such tying is over and above the ietf sip
specification. Depending on how it is done, it may still be compliant
with sip specs, or not. Certainly, as long as there are are network
elements involved in the call in some way, they are free to stop
supporting a call at any time.
Paul
Abu Mohammad Muttalib wrote:
> Hi,
>
>
>
> I have a scenario in which I wanted to know what will happen to the
> ongoing outgoing call.
>
>
>
> Let's say a user X is registered with a domain. The registrar and proxy
> are using the same location database record. X has registered with an
> expiration of 3600 sec. He starts a conversation with another user in
> the same domain, say after 50 second of registering to the server. The
> call is being going through the proxy. The UA A doesn't send a REGISTER
> request after the expiration of its time. What will happen to the
> ongoing call at the end of 60th minute? Does RFC 3261 says something
> about this scenario? If yes, where in RFC? If not then whether this
> scenario will depend on the implementation??
>
>
>
> Please help.
>
>
>
> Thanks and regards,
>
> Abu.
>
> _______________________________________________
> 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
