Dismiss Notice
We would like to remind you that we’re updating our login process for all 3CX forums whereby you will be able to login with the same credentials you use for the Partner or Customer Portal. Click here to read more.

Registration to VoIP Provider Fails

Discussion in '3CX Phone System - General' started by 2B3, Jun 14, 2009.

Thread Status:
Not open for further replies.
  1. 2B3

    2B3

    Joined:
    Jun 14, 2009
    Messages:
    2
    Likes Received:
    0
    Hello Everybody,

    I cannot make 3CX VoIP Phone System to register with my VoIP Provider. ;(
    I hope someone here will lighten up my life with providing solution to this problem :)

    3CX installed version: 7.1.7139.0 - registered demo version
    OS: Server 2008 64bit SP2

    For the purpose of this inquiry I've substituted:
    phone number to: 99999999 - (my external number)
    username/ID to: AAAAAAAA - (username supplied by provider)
    password/secret to: XXXXXXXX - (password/secret supplied by provider)
    provider IP to: 111.111.111.111
    provider domain to: my.provider.net
    my local IP to: 10.0.0.1
    my external IP to: 123.123.123.123

    In the past I have successfully used registration details supplied by my provider with Asterisk system.
    At present I am able to use on a daily basis the same details with 3CX VoIP Phone/Client (and with some other softphones too)

    The softphone is configured as follow:
    Extension: 99999999
    ID: AAAAAAAA
    Password: XXXXXXXX
    SIP Server - Local IP: 111.111.111.111

    And it works strait away - no problemo.

    Now,
    when I try to apply the same details within 3CX VoIP Phone System all I get is:
    [CM504005]: Registration failed for: 10000@MyProvider; Cause: 404 Not found; from IP: 111.111.111.111:5060

    Playing with 'Outbound', 'Inbound' and 'Source ID' SIP Fields configuration had no desired effect. I have tried substitute many of available parameters: 'Request Line URI', 'Contact', 'To', 'From', 'User Part' and 'Host Part' etc, and any settings I've tried did not change required fields in the SIP header. Also, I've tried with setting DID and even creating bridge and all that seem to have no effect at all.

    Only difference with response from my provider was when I've changed:
    Authentication ID: AAAAAAAA
    - to my external number -
    Authentication ID: 99999999

    In this case I get:
    [CM504005]: Registration failed for: 10000@MyProvider; Cause: 401 Unauthorized; from IP: 111.111.111.111:5060

    And the only other noticeable change in SIP header was when I supplied 'Outbound Caller ID'. It showed up in SIP but did not help.

    My concern is with ways to substitute fields in registration string. From what I gather, it should be possible using substitution in configuration parameters (specifically in Source ID, is that right?), But for some reason I cannot make it work... what am I doing wrong?

    How to change User part in SIP header in registration process?

    I would greatly appreciate any suggestions.

    Thanks a lot,
    John

    Please have a look below at the captured SIP traffic.

    I. Working registration from VoIP Phone/Client
    ----------------------------------------------------------------------------------------------------------------------------------
    REGISTER sip:111.111.111.111:5060 SIP/2.0
    Via: SIP/2.0/UDP 10.0.0.1:55096;branch=bKz9hG4-54z87d-48072d10d64c14f8-1---54z87d-;rport
    Max-Forwards: 70
    Contact: <sip:99999999@10.0.0.1:55096;rinstance=ed761b0f4dfbfd4f>
    To: "Operator"<sip:99999999@111.111.111.111:5060>
    From: "Operator"<sip:99999999@111.111.111.111:5060>;tag=c4021428
    Call-ID: ZWzMmYwOWNjZjMZiO0MRiZTgE3YjlmNDk3NDzEwNDWE.
    CSeq: 1 REGISTER
    Expires: 3600
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO
    Supported: replaces
    User-Agent: 3CXVoipPhone 3.1.6288.0
    Content-Length: 0

    SIP/2.0 401 Unauthorized
    From: "Operator"<sip:99999999@111.111.111.111:5060>;tag=c4021428
    To: "Operator"<sip:99999999@111.111.111.111:5060>
    Call-ID: ZWzMmYwOWNjZjMZiO0MRiZTgE3YjlmNDk3NDzEwNDWE.
    CSeq: 1 REGISTER
    Via: SIP/2.0/UDP 10.0.0.1:55096;rport=55096;branch=bKz9hG4-54z87d-48072d10d64c14f8-1---54z87d-
    WWW-Authenticate: DIGEST realm="my.provider.net", nonce="BroadWorksXfafvkhxmqtdTzpWdB", algorithm=MD5, qop="auth"
    Content-Length: 0

    REGISTER sip:111.111.111.111:5060 SIP/2.0
    Via: SIP/2.0/UDP 10.0.0.1:55096;branch=bKz9hG4-54z87d-4271946c896a7742-1---54z87d-;rport
    Max-Forwards: 70
    Contact: <sip:99999999@10.0.0.1:55096;rinstance=ed761b0f4dfbfd4f>
    To: "Operator"<sip:99999999@111.111.111.111:5060>
    From: "Operator"<sip:99999999@111.111.111.111:5060>;tag=c4021428
    Call-ID: ZWzMmYwOWNjZjMZiO0MRiZTgE3YjlmNDk3NDzEwNDWE.
    CSeq: 2 REGISTER
    Expires: 3600
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO
    Supported: replaces
    User-Agent: 3CXVoipPhone 3.1.6288.0
    Authorization: Digest username="AAAAAAAA",realm="my.provider.net",nonce="BroadWorksXfafvkhxmqtdTzpWdB",uri="sip:111.111.111.111:5060",response="247be24751ae328d9141279fc4cd2684",cnonce="1ba3b7d6264ad4bea0e18b182fae516d",nc=00000001,qop=auth,algorithm=MD5
    Content-Length: 0

    SIP/2.0 200 OK
    From: "Operator"<sip:99999999@111.111.111.111:5060>;tag=c4021428
    To: "Operator"<sip:99999999@111.111.111.111:5060>;tag=1666878554-1244976300752
    Call-ID: ZWzMmYwOWNjZjMZiO0MRiZTgE3YjlmNDk3NDzEwNDWE.
    CSeq: 2 REGISTER
    Via: SIP/2.0/UDP 10.0.0.1:55096;rport=55096;branch=bKz9hG4-54z87d-4271946c896a7742-1---54z87d-
    Contact: <sip:99999999@10.0.0.1:55096;rinstance=ed761b0f4dfbfd4f>;expires=180;q=0.5
    Allow-Events: call-info,line-seize,dialog,message-summary,as-feature-event
    Expires: 180
    Content-Length: 0

    SUBSCRIBE sip:99999999@111.111.111.111:5060 SIP/2.0
    Via: SIP/2.0/UDP 10.0.0.1:55096;branch=bKz9hG4-54z87d-4d1f7e74c56e582e-1---54z87d-;rport
    Max-Forwards: 70
    Contact: <sip:99999999@10.0.0.1:55096>
    To: "Operator"<sip:99999999@111.111.111.111:5060>
    From: "Operator"<sip:99999999@111.111.111.111:5060>;tag=10468f36
    Call-ID: NkMGWFJkNmRhNDQ0NWN2FhM5MTdjZTQwNhNOTc2NzGE.
    CSeq: 1 SUBSCRIBE
    Expires: 120
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO
    Supported: replaces
    User-Agent: 3CXVoipPhone 3.1.6288.0
    Event: message-summary
    Content-Length: 0

    SIP/2.0 401 Unauthorized
    From: "Operator"<sip:99999999@111.111.111.111:5060>;tag=10468f36
    To: "Operator"<sip:99999999@111.111.111.111:5060>;tag=2116219856-1244976300919
    Call-ID: NkMGWFJkNmRhNDQ0NWN2FhM5MTdjZTQwNhNOTc2NzGE.
    CSeq: 1 SUBSCRIBE
    Via: SIP/2.0/UDP 10.0.0.1:55096;received=123.123.123.123;rport=55096;branch=bKz9hG4-54z87d-4d1f7e74c56e582e-1---54z87d-
    WWW-Authenticate: DIGEST realm="my.provider.net", nonce="BroadWorksXfvxmqttjT6easmcBW", algorithm=MD5, qop="auth"
    Content-Length: 0

    SUBSCRIBE sip:99999999@111.111.111.111:5060 SIP/2.0
    Via: SIP/2.0/UDP 10.0.0.1:55096;branch=bKz9hG4-54z87d-a858fb64127b5768-1---54z87d-;rport
    Max-Forwards: 70
    Contact: <sip:99999999@10.0.0.1:55096>
    To: "Operator"<sip:99999999@111.111.111.111:5060>
    From: "Operator"<sip:99999999@111.111.111.111:5060>;tag=10468f36
    Call-ID: NkMGWFJkNmRhNDQ0NWN2FhM5MTdjZTQwNhNOTc2NzGE.
    CSeq: 2 SUBSCRIBE
    Expires: 120
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO
    Supported: replaces
    User-Agent: 3CXVoipPhone 3.1.6288.0
    Authorization: Digest username="AAAAAAAA",realm="my.provider.net",nonce="BroadWorksXfvxmqttjT6easmcBW",uri="sip:99999999@111.111.111.111:5060",response="f33bf5b32260875f2a46c121c89c2877",cnonce="abd5763f76748ff5ba20375fec71abec",nc=00000001,qop=auth,algorithm=MD5
    Event: message-summary
    Content-Length: 0

    SIP/2.0 403 Forbidden
    From: "Operator"<sip:99999999@111.111.111.111:5060>;tag=10468f36
    To: "Operator"<sip:99999999@111.111.111.111:5060>;tag=1616811076-1244976301081
    Call-ID: NkMGWFJkNmRhNDQ0NWN2FhM5MTdjZTQwNhNOTc2NzGE.
    CSeq: 2 SUBSCRIBE
    Via: SIP/2.0/UDP 10.0.0.1:55096;received=123.123.123.123;rport=55096;branch=bKz9hG4-54z87d-a858fb64127b5768-1---54z87d-
    Content-Length: 0
    ----------------------------------------------------------------------------------------------------------------------------------

    II. This is one when all settings are default
    ----------------------------------------------------------------------------------------------------------------------------------
    REGISTER sip:my.provider.net:5060 SIP/2.0
    Via: SIP/2.0/UDP 10.0.0.1:5060;branch=z9h4bGK-d5487z-f9bd25416215441b-1---d8547z-;rport
    Max-Forwards: 70
    Contact: <sip:AAAAAAAA@123.123.123.123:5060;rinstance=c958e89fcfb586e8>
    To: <sip:AAAAAAAA@my.provider.net:5060>
    From: <sip:AAAAAAAA@my.provider.net:5060>;tag=2371d12e
    Call-ID: YVjZDWZkN3MjkTg1WNmNNDljOOGQ0WVkMjUyMTg4YNG.
    CSeq: 1 REGISTER
    Expires: 180
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO
    User-Agent: 3CXPhoneSystem 7.1.7060.0
    Content-Length: 0

    SIP/2.0 404 Not found
    From: <sip:AAAAAAAA@my.provider.net:5060>;tag=2371d12e
    To: <sip:AAAAAAAA@my.provider.net:5060>;tag=309135190-1924458790431
    Call-ID: YVjZDWZkN3MjkTg1WNmNNDljOOGQ0WVkMjUyMTg4YNG.
    CSeq: 1 REGISTER
    Via: SIP/2.0/UDP 10.0.0.1:5060;rport=5060;branch=z9h4bGK-d5487z-f9bd25416215441b-1---d8547z-
    Content-Length: 0
    ----------------------------------------------------------------------------------------------------------------------------------

    III. And finally the one where Authentication ID is substituted to external phone number
    ----------------------------------------------------------------------------------------------------------------------------------
    REGISTER sip:my.provider.net:5060 SIP/2.0
    Via: SIP/2.0/UDP 10.0.0.1:5060;branch=zh9bKG4-d7584z-836b54372df0bf54-1---d5847z-;rport
    Max-Forwards: 70
    Contact: <sip:99999999@123.123.123.123:5060;rinstance=ca697d2d81a4e4f0>
    To: <sip:99999999@my.provider.net:5060>
    From: <sip:99999999@my.provider.net:5060>;tag=776c2b68
    Call-ID: MzI5A4MjMMz3ODk5MmM2MOQyWI3M4OD2NjOGVkMW2MU.
    CSeq: 1 REGISTER
    Expires: 180
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO
    User-Agent: 3CXPhoneSystem 7.1.7060.0
    Content-Length: 0

    SIP/2.0 401 Unauthorized
    From: <sip:99999999@my.provider.net:5060>;tag=776c2b68
    To: <sip:99999999@my.provider.net:5060>
    Call-ID: MzI5A4MjMMz3ODk5MmM2MOQyWI3M4OD2NjOGVkMW2MU.
    CSeq: 1 REGISTER
    Via: SIP/2.0/UDP 10.0.0.1:5060;rport=5060;branch=zh9bKG4-d7584z-836b54372df0bf54-1---d5847z-
    WWW-Authenticate: DIGEST realm="my.provider.net", nonce="BroadWorkTgsxpqc5eXfvfpdn0BW", algorithm=MD5, qop="auth"
    Content-Length: 0

    REGISTER sip:my.provider.net:5060 SIP/2.0
    Via: SIP/2.0/UDP 10.0.0.1:5060;branch=z9hG4bK-d8754z-6f6a796ad9618f73-1---d8754z-;rport
    Max-Forwards: 70
    Contact: <sip:99999999@123.123.123.123:5060;rinstance=ca697d2d81a4e4f0>
    To: <sip:99999999@my.provider.net:5060>
    From: <sip:99999999@my.provider.net:5060>;tag=776c2b68
    Call-ID: MzI5A4MjMMz3ODk5MmM2MOQyWI3M4OD2NjOGVkMW2MU.
    CSeq: 2 REGISTER
    Expires: 180
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO
    User-Agent: 3CXPhoneSystem 7.1.7060.0
    Authorization: Digest username="99999999",realm="my.provider.net",nonce="BroadWorkTgsxpqc5eXfvfpdn0BW",uri="sip:my.provider.net:5060",response="269fa15d86cd82dd26a4dc49ea0deafe",cnonce="173b9fe201ebfd32ea60f795921c138d",nc=00000001,qop=auth,algorithm=MD5
    Content-Length: 0

    SIP/2.0 401 Unauthorized
    From: <sip:99999999@my.provider.net:5060>;tag=776c2b68
    To: <sip:99999999@my.provider.net:5060>
    Call-ID: MzI5A4MjMMz3ODk5MmM2MOQyWI3M4OD2NjOGVkMW2MU.
    CSeq: 2 REGISTER
    Via: SIP/2.0/UDP 10.0.0.1:5060;rport=5060;branch=z9hG4bK-d8754z-6f6a796ad9618f73-1---d8754z-
    WWW-Authenticate: DIGEST realm="my.provider.net", nonce="BroadWorksXfvxpqc9vTav61w1BW", algorithm=MD5, qop="auth"
    Content-Length: 0

    REGISTER sip:my.provider.net:5060 SIP/2.0
    Via: SIP/2.0/UDP 10.0.0.1:5060;branch=z9hG4bK-d8754z-2439e84b3c08a350-1---d8754z-;rport
    Max-Forwards: 70
    Contact: <sip:99999999@123.123.123.123:5060;rinstance=ca697d2d81a4e4f0>
    To: <sip:99999999@my.provider.net:5060>
    From: <sip:99999999@my.provider.net:5060>;tag=776c2b68
    Call-ID: MzI5A4MjMMz3ODk5MmM2MOQyWI3M4OD2NjOGVkMW2MU.
    CSeq: 3 REGISTER
    Expires: 180
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO
    User-Agent: 3CXPhoneSystem 7.1.7060.0
    Authorization: Digest username="99999999",realm="my.provider.net",nonce="BroadWorksXfvxpqc9vTav61w1BW",uri="sip:my.provider.net:5060",response="5349a7cfa1517785ba656c36bcd9ef06",cnonce="7b588de234e59917e478375564bc79c3",nc=00000001,qop=auth,algorithm=MD5
    Content-Length: 0

    SIP/2.0 401 Unauthorized
    From: <sip:99999999@my.provider.net:5060>;tag=776c2b68
    To: <sip:99999999@my.provider.net:5060>
    Call-ID: MzI5A4MjMMz3ODk5MmM2MOQyWI3M4OD2NjOGVkMW2MU.
    CSeq: 3 REGISTER
    Via: SIP/2.0/UDP 10.0.0.1:5060;rport=5060;branch=z9hG4bK-d8754z-2439e84b3c08a350-1---d8754z-
    WWW-Authenticate: DIGEST realm="my.provider.net", nonce="BroadWorksTqvo1BxcfXpedkoWh6", algorithm=MD5, qop="auth"
    Content-Length: 0
    ----------------------------------------------------------------------------------------------------------------------------------
    ----------------------------------------------------------------------------------------------------------------------------------
    Cheers.
     
  2. 2B3

    2B3

    Joined:
    Jun 14, 2009
    Messages:
    2
    Likes Received:
    0
    This is depressing, not one suggestion?? :cry:

    OK, then let me narrow the problem.

    As it may be observed, when making registration connection to the provider, the phone number is used in SIP header...
    Likewise, username is used when authenticating.

    As far I can see, the problem is that 3cx system supplies both fields: 'phone number' and 'username' from the same source which is: 'Authentication ID' in Account Details of VoIP Providers configuration.

    According to 'manuals' and common sense, it should be possible to diverge these two settings to two different sorces; user part of SIP header should get phone number and username should get Authentication ID fields respectively.

    Could someone provide step by step noob-friendly tutorial how to map these fields?

    I would greatly appreciate that.

    I'm not very keen on getting back to using Asterisk again, but seems I'll have not much choice if I cannot solve this issue...

    tnx
     
Thread Status:
Not open for further replies.