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

List:       sip-implementors
Subject:    Re: [Sip-implementors] Query on SIM swap
From:       Ranjit Avasarala <ranjitkav12 () gmail ! com>
Date:       2020-05-12 14:32:22
Message-ID: CAFXT-ptgRCHrwVmNGt7_TbabR30vE46_6i24wKug_bZcSoq8uQ () mail ! gmail ! com
[Download RAW message or body]

thank you Paul for guidance

Regards
Ranjit

On Tue, May 12, 2020 at 8:13 AM Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:

> Since this discussion seems to be specific to 3gpp use of SIP I suggest
> you continue this discussion in some 3gpp-specific forum.
>
> On 5/11/20 7:50 PM, ankur bansal wrote:
> > Hi Ranjit
> >
> > There is no clear specification saying UE should deregister when SIM is
> > removed .
> > But if refer multiple specs , we can reach a point where UE supposed to
> do
> > it .
> >
> > As per 3gpp 24.301
> > 5.5.2.1 General
> >
> > *The detach procedure with appropriate detach type shall be invoked by
> the
> > UE* if the UE is switched off,
> > *the USIM cardis removed from the UE* or the EPS capability of the UE is
> > disabled or the UE wishes to detach for non-EPS services
> >
> > As per FCM0.1 VoLTE Service Description and Implementation Guidelines
> >
> > 3.2.2 VoLTE UE Initiated Detach and IMS Deregistration
> > 3.2.2.1 General
> > *A VoLTE UE shall automatically deregister from IMS before performing an
> > LTE Detach*
> >
> >
> > Even we have seen use-cases where there are services linked with SIM ,and
> > UE can do refresh registration removing those capabilities
> > when SIM is removed .
> >
> > SIM swap anyway will be taken care if UE does IMS deregistration or
> > refresh-registration while SIM is removed.
> >
> > Hope this helps.
> >
> > Regards
> > Ankur Bansal
> >
> >
> > On Sun, May 3, 2020 at 8:37 PM Ranjit Avasarala <ranjitkav12@gmail.com>
> > wrote:
> >
> >> Thank you Dale.  as part of SIM swap testing, I came across the below
> >> scenario:
> >> the Phone number (MSISDN-1) was registered with IMSI (IMSI-1).  when SIM
> >> Swap occurred, the INVITE came with a different IMSI and CSCF sends
> >> diameter SAR with "Unregistered user". But HSS thinks user is registered
> >> and sends SAA with DIAMETER_UNABLE_TO_COMPLY error.  CSCF translates
> this
> >> error to 500 Internal Server Error.
> >> So is this the expected behavior?
> >>
> >> Regards
> >> Ranjit
> >>
> >> On Sun, May 3, 2020 at 9:07 PM Dale R. Worley <worley@ariadne.com>
> wrote:
> >>
> >>> Ranjit Avasarala <ranjitkav12@gmail.com> writes:
> >>>> Does SIM swap procedure on a SIP UE trigger re-registration?  if not
> >> when
> >>>> calls are made from the device, the INVITE would have the IMSI of the
> >> new
> >>>> SIM card?
> >>>
> >>> The answers aren't set by the SIP standards.  However, given that the
> >>> SIM gives the Directory Number of a PSTN telephone, I would expect that
> >> if
> >>> you change the SIM on a UE, the UE would register for the new DN.
> >>>
> >>> In SIP, the From address in an INVITE is not necessarily connected with
> >>> any AOR that the UE registers for.  But in a PSTN telephone, I would
> >>> expect it to use the SIM's DN as the From URI.
> >>>
> >>> Dale
> >>>
> >> _______________________________________________
> >> Sip-implementors mailing list
> >> Sip-implementors@lists.cs.columbia.edu
> >> https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
> >>
> > _______________________________________________
> > Sip-implementors mailing list
> > Sip-implementors@lists.cs.columbia.edu
> > https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
> >
>
> _______________________________________________
> Sip-implementors mailing list
> Sip-implementors@lists.cs.columbia.edu
> https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
>
_______________________________________________
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
[prev in list] [next in list] [prev in thread] [next in thread]