[prev in list] [next in list] [prev in thread] [next in thread] 

List:       sip-implementors
Subject:    Re: [Sip-implementors] Information Required
From:       Tomasz Zieleniewski <tzieleniewski () gmail ! com>
Date:       2009-06-25 7:40:00
Message-ID: 5fd52d7a0906250040r5f26d1f2o50ffda2f52d9f3ba () mail ! gmail ! com
[Download RAW message or body]

Hi,

In standard SIP defined by IETF there is no such requirement to terminate
existing sessions.
Actually a session or any SIP message exchange is independent of the
registration.
Registration is needed to map a public SIP AOR with actual physical location
of the endpoint.
But there no problem for the endpoint to communicate and reach each other
directly without
usage of the location service.Contrary to this IMS assigns a crucial role to
the registration process.

And answering Your question, if user initiated deregistration takes place, a
dedicated SIP Proxy called
SCSCF which acts as a registrar server and facilitates the routing path for
originated and terminated session requests,
must terminate ongoin sessions. Any session initiated by or terminated
towards the previously registered
public user identity (also from implicitly registered set of public user
identities) by this contact address must be released.

Kind regards,
- Tomasz Zieleniewski

2009/6/23 Siddhartha Singh <sidvoip@yahoo.com>

> Hi
> I need informartion on  SIP IMS behaviour in follwoing scenario:
> PreCondition:
>
> 1. Mutiple public identities linked to one private identities are
> registered in IMS.
> 2. We have implicit registration enabled meaning we do not need to send
> individual registration messages for all public identity.
> 3.one on public identity is having active session at same time one of
> public identity sends
> registration message with expire header set to 0.
> How should this be handled, should existing session get terminated or there
> should be some error response.
> Please help
>
>
>      ICC World Twenty20 England '09 exclusively on YAHOO! CRICKET
> http://cricket.yahoo.com
> _______________________________________________
> Sip-implementors mailing list
> Sip-implementors@lists.cs.columbia.edu
> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
>

[prev in list] [next in list] [prev in thread] [next in thread]