×

Discussion Board

Results 1 to 6 of 6

Thread: 603 decline

  1. #1
    Registered User
    Join Date
    May 2005
    Posts
    38

    603 decline

    Hi,

    I now have a perfect output in the server logs for the REGISTER method. Compared it with ChipFlip logs and it matches correctly.

    Problem starts when I send an INVITE.

    I am getting 603 decline message immediately although the second emulator has already registered.

    I am using SIP3.0.

    Any idea ?

    Tom

  2. #2
    Registered User
    Join Date
    May 2005
    Posts
    38

    Log files for 603 decline

    REGISTER by the FIRST EMULATOR

    [0x050c 13:56:36] SipHandleManagerImpl: 4325448 ProcessUdpEvent: received datagram:
    REGISTER sip:192.168.0.45 SIP/2.0

    Route: <sip:192.168.0.45;lr>

    Via: SIP/2.0/UDP 192.168.0.163:5060;branch=z9hG4bKR-_CXHFxcMxSF

    From: sip:p1@192.168.0.45;tag=33fCXwUnhw

    To: sip:p1@192.168.0.45

    Contact: sip:p1@192.168.0.163;expires=3600

    Supported: sec-agree

    CSeq: 1210 REGISTER

    Call-ID: o5_CXCrWH0S1UMk8I-Jfh4AC_j0ViO

    Max-Forwards: 70

    Content-Length: 0



    [0x050c 13:56:36] SipUdpHandle: 4364672 SendMessage: sending datagram:
    SIP/2.0 200 OK

    Contact: <sip:p1@192.168.0.163>;expires=3600

    Call-ID: o5_CXCrWH0S1UMk8I-Jfh4AC_j0ViO

    CSeq: 1210 REGISTER

    From: <sip:p1@192.168.0.45>;tag=33fCXwUnhw

    To: <sip:p1@192.168.0.45>;tag=17409488

    Via: SIP/2.0/UDP 192.168.0.163:5060;branch=z9hG4bKR-_CXHFxcMxSF

    Content-Length: 0



    REGISTER by the SECOND EMULATOR

    [0x050c 13:56:51] SipHandleManagerImpl: 4325448 ProcessUdpEvent: received datagram:
    REGISTER sip:192.168.0.45 SIP/2.0

    Route: <sip:192.168.0.45;lr>

    Via: SIP/2.0/UDP 192.168.0.162:5060;branch=z9hG4bKnNwV2J2P9f7CH

    From: sip:p2@192.168.0.45;tag=PeQV2wMEK_

    To: sip:p2@192.168.0.45

    Contact: sip:p2@192.168.0.162;expires=3600

    Supported: sec-agree

    CSeq: 745 REGISTER

    Call-ID: XrQV2Cj5kvbfdgp_kvbe94OxT61fvN

    Max-Forwards: 70

    Content-Length: 0



    [0x050c 13:56:51] SipUdpHandle: 4364672 SendMessage: sending datagram:
    SIP/2.0 200 OK

    Contact: <sip:p2@192.168.0.162>;expires=3600

    Call-ID: XrQV2Cj5kvbfdgp_kvbe94OxT61fvN

    CSeq: 745 REGISTER

    From: <sip:p2@192.168.0.45>;tag=PeQV2wMEK_

    To: <sip:p2@192.168.0.45>;tag=24551711

    Via: SIP/2.0/UDP 192.168.0.162:5060;branch=z9hG4bKnNwV2J2P9f7CH

    Content-Length: 0


    INVITE SENT by the FIRST EMULATOR to the SECOND


    [0x050c 13:57:03] SipHandleManagerImpl: 4325448 ProcessUdpEvent: received datagram:
    INVITE sip:p2@192.168.0.45 SIP/2.0

    Route: <sip:192.168.0.45;lr>

    Via: SIP/2.0/UDP 192.168.0.163:5060;branch=z9hG4bKddbCXLeKw2O9m

    From: sip:p1@192.168.0.45;tag=9jrCXyYR7O

    To: sip:p2@192.168.0.45

    Supported: 100rel,sec-agree

    Contact: sip:p1@192.168.0.163

    CSeq: 1211 INVITE

    Call-ID: kiTCXAvoZiYRdMGpOwy_73zKtw8xoU

    s: subject

    Max-Forwards: 70

    Content-Type: application/sdp

    Content-Length: 152



    v=0

    o=p1 3326171223 3326171224 IN IP4 192.168.0.163

    s=SipSession

    c=IN IP4 192.168.0.163

    t=0 0

    m=application 49152 TCP SIPBasics

    a=direction:both

    [0x050c 13:57:03] SipUdpHandle: 4392680 SendMessage: sending datagram:
    INVITE sip:p2@192.168.0.162 SIP/2.0

    Via: SIP/2.0/UDP 192.168.0.45;branch=z9hG4bK0510423c50e3bebaae6f4265bb246e6a

    Route: <sip:192.168.0.45;lr>

    Via: SIP/2.0/UDP 192.168.0.163:5060;branch=z9hG4bKddbCXLeKw2O9m

    From: <sip:p1@192.168.0.45>;tag=9jrCXyYR7O

    To: <sip:p2@192.168.0.45>

    Supported: 100rel

    Supported: sec-agree

    Contact: <sip:p1@192.168.0.163>

    CSeq: 1211 INVITE

    Call-ID: kiTCXAvoZiYRdMGpOwy_73zKtw8xoU

    Subject: subject

    Max-Forwards: 69

    Content-Type: application/sdp

    Content-Length: 152



    v=0

    o=p1 3326171223 3326171224 IN IP4 192.168.0.163

    s=SipSession

    c=IN IP4 192.168.0.163

    t=0 0

    m=application 49152 TCP SIPBasics

    a=direction:both



    TRYING PROCEDURE


    [0x050c 13:57:04] SipHandleManagerImpl: 4325448 ProcessUdpEvent: received datagram:
    SIP/2.0 100 Trying

    Via: SIP/2.0/UDP 192.168.0.45;branch=z9hG4bK0510423c50e3bebaae6f4265bb246e6a,SIP/2.0/UDP 192.168.0.163:5060;branch=z9hG4bKddbCXLeKw2O9m

    To: sip:p2@192.168.0.45

    From: sip:p1@192.168.0.45;tag=9jrCXyYR7O

    Call-ID: kiTCXAvoZiYRdMGpOwy_73zKtw8xoU

    CSeq: 1211 INVITE

    Content-Length: 0



    [0x050c 13:57:04] SipUdpHandle: 4392680 SendMessage: sending datagram:
    SIP/2.0 100 Trying

    Via: SIP/2.0/UDP 192.168.0.163:5060;branch=z9hG4bKddbCXLeKw2O9m

    To: <sip:p2@192.168.0.45>

    From: <sip:p1@192.168.0.45>;tag=9jrCXyYR7O

    Call-ID: kiTCXAvoZiYRdMGpOwy_73zKtw8xoU

    CSeq: 1211 INVITE

    Content-Length: 0



    DECLINE PROCEDURE


    [0x050c 13:57:04] SipHandleManagerImpl: 4325448 ProcessUdpEvent: received datagram:
    SIP/2.0 603 Decline

    Via: SIP/2.0/UDP 192.168.0.45;branch=z9hG4bK0510423c50e3bebaae6f4265bb246e6a,SIP/2.0/UDP 192.168.0.163:5060;branch=z9hG4bKddbCXLeKw2O9m

    To: sip:p2@192.168.0.45;tag=IEIV2HxuPL

    From: sip:p1@192.168.0.45;tag=9jrCXyYR7O

    Call-ID: kiTCXAvoZiYRdMGpOwy_73zKtw8xoU

    CSeq: 1211 INVITE

    Content-Length: 0



    [0x050c 13:57:04] SipUdpHandle: 4392680 SendMessage: sending datagram:
    SIP/2.0 603 Decline

    Via: SIP/2.0/UDP 192.168.0.163:5060;branch=z9hG4bKddbCXLeKw2O9m

    To: <sip:p2@192.168.0.45>;tag=IEIV2HxuPL

    From: <sip:p1@192.168.0.45>;tag=9jrCXyYR7O

    Call-ID: kiTCXAvoZiYRdMGpOwy_73zKtw8xoU

    CSeq: 1211 INVITE

    Content-Length: 0

  3. #3
    Registered User
    Join Date
    May 2005
    Posts
    38
    Has anyone else faced this DECLINE problem ?

    Tom

  4. #4
    Registered User
    Join Date
    Jun 2005
    Posts
    5

    I have faced 603 Decline

    I have the same problem. This post probably does not help anyone, but at least the problem seems to be common.

  5. #5
    Registered User
    Join Date
    Mar 2012
    Posts
    1

    Re: 603 decline

    hi everybody i have a problem for 603. i bought nokia 603 it works very good but i couldnt insert simcard into simcard place. i wonder what can i do ?

  6. #6
    Nokia Developer Moderator
    Join Date
    Feb 2006
    Location
    Oslo, Norway
    Posts
    28,748

    Re: 603 decline

    This is a site for software developers, and this particular 6.5 years old discussion addressed an error message containing the number 603. The Nokia 603 did not exist that time.
    Your issue is probably about the the Nokia 603 uses microSIM (http://en.wikipedia.org/wiki/Subscri...module#Formats), ask your mobile operator in order to get the big one replaced.
    Note that there is an end-user site, http://www.nokia.com/discussions

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
×