IMS/SIP Quick Reference                                                Home : www.sharetechnote.com

 

 

Address in IMS/SIP Messages

 

One of the most confusing thing in analyzing and troubleshooting IMS/SIP related issue is to understand all the correlations of various addresses in multiple messages. If these correlations are not properly implemented, you would get such a famous/notorious error message "404 Not Found".

 

I will keep adding examples of these correlations among various message, but don't expect this to be 100% correct and applies to your implementation. The requirement of these mapping may varies depending on what kind of specification (RFC, 3GPP, Carrier Specification etc) and even with the same specification, the requirement would vary depending on the version of the specification. The purpose of this page is to provide you some guide lines and help you narrow down the scope of search when you troubleshooting those issues caused by 'Addressing'.

 

< REGISTER / INVITE >

 

 

According to 3GPP 34 229-1 V10.2.0 (2013-07) A.1

REGISTER

Header/param

Value/remark

Ref

Request-URI

  • SIP URI formed from home domain name as stored in EFDOMAIN (when using ISIM) or SIP URI formed from home domain name derived from the IMSI (when no ISIM available on the UICC)

RFC 3261

From
  • any IMPU within the set of IMPUs on ISIM (when using ISIM) or public user identity derived from px_IMSI (when no ISIM available on the UICC)
  • same public user identity as in initial REGISTER
  • public user identity derived from px_IMSI
  • px_EmergencyPublicUserIdentity (if the UE is already registered to IMS or if the UE is using ISIM) or public user identity derived from px_IMSI (when UE is using USIM and UE is not yet registered to IMS)

RFC 3261

To
  • any IMPU within the set of IMPUs on ISIM (when using ISIM) or public user identity derived from px_IMSI (when no ISIM available on the UICC)
  • same public user identity as in initial REGISTER
  • public user identity derived from px_IMSI
  • px_EmergencyPublicUserIdentity (if the UE is already registered to IMS or if the UE is using ISIM) or public user identity derived from px_IMSI (when UE is using USIM and UE is not yet registered to IMS)

RFC 3261

Contact

     

     

     

    Feature Param

     

     

 

  • SIP URI with IP address or FQDN and indicating either an unprotected port selected by the UE or no port at all. When A7 the SIP URI shall contain the sos URI parameter.
  • SIP URI with IP address or FQDN and protected server port of UE. When A7 the SIP URI shall contain the sos URI parameter.
  • +g.3gpp.icsi-ref="urn%3Aurn-7%3A3gppservice.ims.icsi.mmtel"
  • +g.3gpp.smsip
  • video
  • +sip.instance media feature tag with the instance ID of the UE
 

 

According to 3GPP 34 229-1 V10.2.0 (2013-07) A.2.9

INVITE (MT)

Header/param

Value/remark

Ref

Request-URI

  • UE"s registered contact address in SIP URI form, as provided in the Contact header of the REGISTER message
  • UE"s contact address in SIP URI form, as provided in the Contact header within any response or request within the dialog

RFC 3261

From
  • an SIP URI of the SS representing the calling UE
  • SIP URI of SS (i.e. the remote UE) as used in any previous request in the same dialog (In the earlier requests within the same dialog this URI appears in To header within requests sent by the UE and in From header within requests sent by the SS)

RFC 3261

To
  • SIP or TEL URI of the UE
  • SIP URI of the UE as used in any previous request in the same dialog (In the earlier requests within the same dialog this URI appears in From header within requests sent by the UE and in To header within requests sent by the SS)

RFC 3261

Contact

 

  • SIP URI with IP address or FQDN and protected server port of the calling UE, for example 'sip:caller@3gpp.org:6543'.
  • SIP URI with IP address or FQDN and unprotected server port of the calling UE.
 

 

 

< SUBSCRIBE / NOTIFY >

 

 

 

< INVITE / BYE(MT) >

 

 

< From / To for whole VoLTE Sequence >