Menu

#9 UE Registration

1.0
open
nobody
None
2015-10-28
2015-10-24
Nayan Jain
No

Hello,

I am sending below SIP registration message but it goes as a emergency registration.

My Setup -

UE -> eNB -> EPC -> OpenIMS Core

2015 Oct 20 12:11:29.606 [7C] 0x156E IMS SIP Message
Version = 1
Direction = UE_TO_NETWORK
SDP Presence = 0
SIP Call ID Length = 35
SIP Message Length = 714
SIP Message Logged Bytes = 715
Message ID = IMS_SIP_REGISTER
Response Code = INFORMAL_RESPONSE (0)
CM Call ID = 255
SIP Call ID = 4096858046_173873048@192.168.0.232
Sip Message = REGISTER sip:open-ims.test SIP/2.0
f: sip:3000000001@open-ims.test;tag=4096858052
t: sip:3000000001@open-ims.test
CSeq: 875632574 REGISTER
i: 4096858046_173873048@192.168.0.232
v: SIP/2.0/UDP 192.168.0.232:5060;branch=z9hG4bK2837525324
Max-Forwards: 70
m: sip:3000000001@192.168.0.232:5060;+sip.instance="<urn:gsma:imei:35580506-000178-0>";+g.3gpp.smsip
Route: <sip:192.168.0.141:4060;lr>
P-Access-Network-Info: 3GPP-E-UTRAN-FDD; utran-cell-id-3gpp=31148031320000201
l: 0
Authorization: Digest uri="sip:open-ims.test",username="3000000001@open-ims.test",response="",realm="open-ims.test",nonce=""
Expires: 600000
k: path
Allow: INVITE,BYE,CANCEL,ACK,NOTIFY,UPDATE,PRACK,INFO,MESSAGE,OPTIONS</sip:192.168.0.141:4060;lr></urn:gsma:imei:35580506-000178-0>

Related

Issues: #9

Discussion

  • Nayan Jain

    Nayan Jain - 2015-10-24

    I am using SIP native application for UE registration and doing VoLTE call

     
  • Franz Edler

    Franz Edler - 2015-10-25

    Why is it handled as an emergency registration? - Where is you conclusion
    based upon?

    There is no "sos" SIP URI parameter in Contact header, therefore it is not
    an emergency registration.

    BR

    From: Nayan Jain [mailto:nayanjain@users.sf.net]
    Sent: Saturday, October 24, 2015 7:35 PM
    To: Ticket 9 9@issues.openimscore.p.re.sf.net
    Subject: [openimscore:issues] #9 UE Registration


    [issues:#9] http://sourceforge.net/p/openimscore/issues/9/ UE
    Registration

    Status: open
    Milestone: 1.0
    Created: Sat Oct 24, 2015 05:35 PM UTC by Nayan Jain
    Last Updated: Sat Oct 24, 2015 05:35 PM UTC
    Owner: nobody

    Hello,

    I am sending below SIP registration message but it goes as a emergency
    registration.

    My Setup -

    UE -> eNB -> EPC -> OpenIMS Core

    2015 Oct 20 12:11:29.606 [7C] 0x156E IMS SIP Message
    Version = 1
    Direction = UE_TO_NETWORK
    SDP Presence = 0
    SIP Call ID Length = 35
    SIP Message Length = 714
    SIP Message Logged Bytes = 715
    Message ID = IMS_SIP_REGISTER
    Response Code = INFORMAL_RESPONSE (0)
    CM Call ID = 255
    SIP Call ID = 4096858046_173873048@192.168.0.232
    4096858046_173873048@192.168.0.232
    Sip Message = REGISTER <sip:open-ims.test> sip:open-ims.test SIP/2.0
    f: sip:3000000001@open-ims.test
    sip:3000000001@open-ims.test;tag=4096858052
    t: sip:3000000001@open-ims.test sip:3000000001@open-ims.test
    CSeq: 875632574 REGISTER
    i: 4096858046_173873048@192.168.0.232
    4096858046_173873048@192.168.0.232
    v: SIP/2.0/UDP 192.168.0.232:5060;branch=z9hG4bK2837525324
    Max-Forwards: 70
    m: sip:3000000001@192.168.0.232:5060
    sip:3000000001@192.168.0.232:5060;+sip.instance="<urn:gsma:imei:35580506-000 178-0="">";+g.3gpp.smsip
    Route: < <sip:192.168.0.141:4060;lr> sip:192.168.0.141:4060;lr>
    P-Access-Network-Info: 3GPP-E-UTRAN-FDD;
    utran-cell-id-3gpp=31148031320000201
    l: 0
    Authorization: Digest uri=" <sip:open-ims.test>
    sip:open-ims.test",username=" 3000000001@open-ims.test
    3000000001@open-ims.test",response="",realm="open-ims.test",nonce=""
    Expires: 600000
    k: path
    Allow: INVITE,BYE,CANCEL,ACK,NOTIFY,UPDATE,PRACK,INFO,MESSAGE,OPTIONS</sip:open-ims.test></sip:192.168.0.141:4060;lr></urn:gsma:imei:35580506-000></sip:open-ims.test>


    Sent from sourceforge.net because you indicated interest in
    https://sourceforge.net/p/openimscore/issues/9/

    To unsubscribe from further messages, please visit
    https://sourceforge.net/auth/subscriptions/

     

    Related

    Issues: #9

  • Nayan Jain

    Nayan Jain - 2015-10-26

    Thanks Franz Edler for quick response.

    Attached P-CSCF screen shot and IMS tcpdump.

     

    Last edit: Nayan Jain 2015-10-26
    • Franz Edler

      Franz Edler - 2015-10-26

      What I see from the screenshot is, that only a check for emergency flag has
      been done.

      That does not mean that an emergency flag has been detected.

      Check pcscf.cfg for the sequence of function calls.

      BR

      From: Nayan Jain [mailto:nayanjain@users.sf.net]
      Sent: Monday, October 26, 2015 3:29 PM
      To: [openimscore:issues] 9@issues.openimscore.p.re.sf.net
      Subject: [openimscore:issues] #9 UE Registration

      Thanks Franz Edler for quick response.

      Attached P-CSCF screen shot and IMS tcpdump.

      Attachments:


      [issues:#9] http://sourceforge.net/p/openimscore/issues/9/ UE
      Registration

      Status: open
      Milestone: 1.0
      Created: Sat Oct 24, 2015 05:35 PM UTC by Nayan Jain
      Last Updated: Sat Oct 24, 2015 05:41 PM UTC
      Owner: nobody

      Hello,

      I am sending below SIP registration message but it goes as a emergency
      registration.

      My Setup -

      UE -> eNB -> EPC -> OpenIMS Core

      2015 Oct 20 12:11:29.606 [7C] 0x156E IMS SIP Message
      Version = 1
      Direction = UE_TO_NETWORK
      SDP Presence = 0
      SIP Call ID Length = 35
      SIP Message Length = 714
      SIP Message Logged Bytes = 715
      Message ID = IMS_SIP_REGISTER
      Response Code = INFORMAL_RESPONSE (0)
      CM Call ID = 255
      SIP Call ID = 4096858046_173873048@192.168.0.232
      4096858046_173873048@192.168.0.232
      Sip Message = REGISTER sip:open-ims.test SIP/2.0
      f: sip:3000000001@open-ims.test sip:3000000001@open-ims.test
      ;tag=4096858052
      t: sip:3000000001@open-ims.test sip:3000000001@open-ims.test
      CSeq: 875632574 REGISTER
      i: 4096858046_173873048@192.168.0.232
      4096858046_173873048@192.168.0.232
      v: SIP/2.0/UDP 192.168.0.232:5060;branch=z9hG4bK2837525324
      Max-Forwards: 70
      m: sip:3000000001@192.168.0.232:5060
      sip:3000000001@192.168.0.232:5060
      ;+sip.instance="<urn:gsma:imei:35580506-000178-0>";+g.3gpp.smsip
      Route: <sip:192.168.0.141:4060;lr>
      P-Access-Network-Info: 3GPP-E-UTRAN-FDD;
      utran-cell-id-3gpp=31148031320000201
      l: 0
      Authorization: Digest
      uri="sip:open-ims.test",username="3000000001@open-ims.test
      3000000001@open-ims.test
      ",response="",realm="open-ims.test",nonce=""
      Expires: 600000
      k: path
      Allow: INVITE,BYE,CANCEL,ACK,NOTIFY,UPDATE,PRACK,INFO,MESSAGE,OPTIONS</sip:192.168.0.141:4060;lr></urn:gsma:imei:35580506-000178-0>


      Sent from sourceforge.net because you indicated interest in
      https://sourceforge.net/p/openimscore/issues/9/

      To unsubscribe from further messages, please visit
      https://sourceforge.net/auth/subscriptions/

       

      Related

      Issues: #9

  • Nayan Jain

    Nayan Jain - 2015-10-26

    Thanks Franz Edler for clarification.

    I have observed that UE send the" REGISTER" message to IMS and IMS send "401 Unauthorized - Challenging the UE" message.

    "401 Unauthorized - Challenging the UE" message is not reaching up to UE, I can see this message in EPC and eNB log file but it dosn't reach to UE.Attached log file for your reference.

    What can be the issue?

     
    • Franz Edler

      Franz Edler - 2015-10-26

      I wonder anyhow about your configuration.

      REGISTER requests are sent by 192.168.0.230 (the UE?) to 192.168.0.141:4060
      (P-CSCF ?) for three times. Why?

      Where did you trace?

      What is between P-CSCF and the UE in your configuration?

      BR

      From: Nayan Jain [mailto:nayanjain@users.sf.net]
      Sent: Monday, October 26, 2015 6:50 PM
      To: [openimscore:issues] 9@issues.openimscore.p.re.sf.net
      Subject: [openimscore:issues] #9 UE Registration

      Thanks Franz Edler for clarification.

      I have observed that UE send the" REGISTER" message to IMS and IMS send "401
      Unauthorized - Challenging the UE" message.

      "401 Unauthorized - Challenging the UE" message is not reaching up to UE, I
      can see this message in EPC and eNB log file but it dosn't reach to
      UE.Attached log file for your reference.

      What can be the issue?

      Attachments:


      [issues:#9] http://sourceforge.net/p/openimscore/issues/9/ UE
      Registration

      Status: open
      Milestone: 1.0
      Created: Sat Oct 24, 2015 05:35 PM UTC by Nayan Jain
      Last Updated: Mon Oct 26, 2015 02:29 PM UTC
      Owner: nobody

      Hello,

      I am sending below SIP registration message but it goes as a emergency
      registration.

      My Setup -

      UE -> eNB -> EPC -> OpenIMS Core

      2015 Oct 20 12:11:29.606 [7C] 0x156E IMS SIP Message
      Version = 1
      Direction = UE_TO_NETWORK
      SDP Presence = 0
      SIP Call ID Length = 35
      SIP Message Length = 714
      SIP Message Logged Bytes = 715
      Message ID = IMS_SIP_REGISTER
      Response Code = INFORMAL_RESPONSE (0)
      CM Call ID = 255
      SIP Call ID = 4096858046_173873048@192.168.0.232
      4096858046_173873048@192.168.0.232
      Sip Message = REGISTER <sip:open-ims.test> sip:open-ims.test SIP/2.0
      f: sip:3000000001@open-ims.test
      sip:3000000001@open-ims.test;tag=4096858052
      t: sip:3000000001@open-ims.test sip:3000000001@open-ims.test
      CSeq: 875632574 REGISTER
      i: 4096858046_173873048@192.168.0.232
      4096858046_173873048@192.168.0.232
      v: SIP/2.0/UDP 192.168.0.232:5060;branch=z9hG4bK2837525324
      Max-Forwards: 70
      m: sip:3000000001@192.168.0.232:5060
      sip:3000000001@192.168.0.232:5060;+sip.instance="<urn:gsma:imei:35580506-000 178-0="">";+g.3gpp.smsip
      Route: < <sip:192.168.0.141:4060;lr> sip:192.168.0.141:4060;lr>
      P-Access-Network-Info: 3GPP-E-UTRAN-FDD;
      utran-cell-id-3gpp=31148031320000201
      l: 0
      Authorization: Digest uri=" <sip:open-ims.test>
      sip:open-ims.test",username=" 3000000001@open-ims.test
      3000000001@open-ims.test",response="",realm="open-ims.test",nonce=""
      Expires: 600000
      k: path
      Allow: INVITE,BYE,CANCEL,ACK,NOTIFY,UPDATE,PRACK,INFO,MESSAGE,OPTIONS</sip:open-ims.test></sip:192.168.0.141:4060;lr></urn:gsma:imei:35580506-000></sip:open-ims.test>


      Sent from sourceforge.net because you indicated interest in
      https://sourceforge.net/p/openimscore/issues/9/

      To unsubscribe from further messages, please visit
      https://sourceforge.net/auth/subscriptions/

       

      Related

      Issues: #9

  • Nayan Jain

    Nayan Jain - 2015-10-28

    Hello Franz Edler,

    Please find attached setup which I am using for IMS registration.

    Please find below my inline comments on your queries -
    Where did you trace?
    <nayan> I have taken log at EPC and eNB</nayan>

    What is between P-CSCF and the UE in your configuration?
    <nayan> In between UE and P-CSCF - eNB and EPC are there</nayan>

    REGISTER requests are sent by 192.168.0.230 (the UE?) to 192.168.0.141:4060
    <nayan> Yes UE IP is 192.168.0.230 and IMS IP is 192.168.0.141. I am using IMS port 4060 for registration.</nayan>

    Let me know if you need any more information.

    Regards

    Nayan Jain

     

Log in to post a comment.

MongoDB Logo MongoDB