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.

3CX with OBI 110 as PSTN gateway

Discussion in '3CX Phone System - General' started by Ash91, Dec 7, 2015.

Thread Status:
Not open for further replies.
  1. Ash91

    Joined:
    Dec 7, 2015
    Messages:
    7
    Likes Received:
    0
    Hello everyone,

    I have been struggling to place outbound calls from yealink IP phones. First I installed 3CX software in my windows and added a PSTN gateway & gave the host address as my OBI's web interface. And I managed to register OBI with 3CX. Now comes the hard part, where i can receive calls from outside and at the same time i can call to the other extensions within the network but unable to place outbound calls. I seriously have tried my best by altering everything which is in the internet but still the problem exist. Any help woul;d be much appreciated. This is the error message that i get from server log,

    7-Dec-2015 23:25:26.285 [CM503003]: Call(C:5): Call to <sip:66627128@192.168.1.70:5060> has failed; Cause: 404 Not Found/INVITE from 192.168.1.70:5060
    07-Dec-2015 23:24:27.716 [CM102001]: Authentication failed for AuthFail Recv Req REGISTER from 192.168.1.70:5061 tid=-5452ebc4 Call-ID=083b7717@192.168.1.70:

    REGISTER sip:192.168.1.99:5060 SIP/2.0
    Via: SIP/2.0/UDP 192.168.1.70:5061;branch=z9hG4bK-5452ebc4;rport=5061
    Max-Forwards: 70
    Contact: <sip:90001@192.168.1.70:5061>;expires=60;+sip.instance="<urn:uuid:00000000-0000-0000-0000-9cadef0141d1>"
    To: <sip:90001@192.168.1.99>
    From: <sip:90001@192.168.1.99>;tag=SP21514ba237f45cc9a
    Call-ID: 083b7717@192.168.1.70
    CSeq: 51324 REGISTER
    Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER, UPDATE
    Proxy-Authorization: DIGEST algorithm=MD5,nonce="414d535c0c767bfb61:4400d668f273a07cddadfce596d15a79",realm="3CXPhoneSystem",response="c3c40b74fab5c9de59d2ec71c4490ad9",uri="sip:192.168.1.99:5060",username="90001"
    Supported: replaces
    User-Agent: OBIHAI/OBi110-1.3.0.2872
    Content-Length: 0

    ; Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings
    07-Dec-2015 23:23:57.498 [CM102001]: Authentication failed for AuthFail Recv Req REGISTER from 192.168.1.70:5061 tid=-53392b6d Call-ID=1acde7a7@192.168.1.70:
    REGISTER sip:192.168.1.99:5060 SIP/2.0
    Via: SIP/2.0/UDP 192.168.1.70:5061;branch=z9hG4bK-53392b6d;rport=5061
    Max-Forwards: 70
    Contact: <sip:90001@192.168.1.70:5061>;expires=60;+sip.instance="<urn:uuid:00000000-0000-0000-0000-9cadef0141d1>"
    To: <sip:90001@192.168.1.99>
    From: <sip:90001@192.168.1.99>;tag=SP21514ba237f45cc9a
    Call-ID: 1acde7a7@192.168.1.70
    CSeq: 2129 REGISTER
    Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER, UPDATE
    Proxy-Authorization: DIGEST algorithm=MD5,nonce="414d535c0c767bdd06:46a6953a9a095ed29f325305ceaba904",realm="3CXPhoneSystem",response="e1c3b5625274a7d9837194601dd54dc9",uri="sip:192.168.1.99:5060",username="90001"
    Supported: replaces
    User-Agent: OBIHAI/OBi110-1.3.0.2872
    Content-Length: 0

    ; Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings
    07-Dec-2015 23:23:27.280 [CM102001]: Authentication failed for AuthFail Recv Req REGISTER from 192.168.1.70:5061 tid=-5d2b1a5f Call-ID=5d3c2d31@192.168.1.70:
    REGISTER sip:192.168.1.99:5060 SIP/2.0
    Via: SIP/2.0/UDP 192.168.1.70:5061;branch=z9hG4bK-5d2b1a5f;rport=5061
    Max-Forwards: 70
    Contact: <sip:90001@192.168.1.70:5061>;expires=60;+sip.instance="<urn:uuid:00000000-0000-0000-0000-9cadef0141d1>"
    To: <sip:90001@192.168.1.99>
    From: <sip:90001@192.168.1.99>;tag=SP21514ba237f45cc9a
    Call-ID: 5d3c2d31@192.168.1.70
    CSeq: 4326 REGISTER
    Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER, UPDATE
    Proxy-Authorization: DIGEST algorithm=MD5,nonce="414d535c0c767bbf52:940c3f08145d75b519a2bea3641e834f",realm="3CXPhoneSystem",response="3277123839b2e05ee4bd1569ec5afaa4",uri="sip:192.168.1.99:5060",username="90001"
    Supported: replaces
    User-Agent: OBIHAI/OBi110-1.3.0.2872
    Content-Length: 0

    ; Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings
    07-Dec-2015 23:22:57.062 [CM102001]: Authentication failed for AuthFail Recv Req REGISTER from 192.168.1.70:5061 tid=-283cfdf1 Call-ID=add11a32@192.168.1.70:
    REGISTER sip:192.168.1.99:5060 SIP/2.0
    Via: SIP/2.0/UDP 192.168.1.70:5061;branch=z9hG4bK-283cfdf1;rport=5061
    Max-Forwards: 70
    Contact: <sip:90001@192.168.1.70:5061>;expires=60;+sip.instance="<urn:uuid:00000000-0000-0000-0000-9cadef0141d1>"
    To: <sip:90001@192.168.1.99>
    From: <sip:90001@192.168.1.99>;tag=SP21514ba237f45cc9a
    Call-ID: add11a32@192.168.1.70
    CSeq: 1996 REGISTER
    Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER, UPDATE
    Proxy-Authorization: DIGEST algorithm=MD5,nonce="414d535c0c767b8279:ef88446f454ea77d61b447b41bb45c16",realm="3CXPhoneSystem",response="1ea65c2c74c01f22b6d950585893fd0e",uri="sip:192.168.1.99:5060",username="90001"
    Supported: replaces
    User-Agent: OBIHAI/OBi110-1.3.0.2872
    Content-Length: 0

    ; Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings
    07-Dec-2015 23:19:09.969 [Flow] Target endpoint for 66627128 can not be built!
    07-Dec-2015 23:18:09.696 [Flow] Target endpoint for 66627128 can not be built!
    07-Dec-2015 23:17:08.169 [Flow] Target endpoint for 66627128 can not be built!
    07-Dec-2015 23:16:14.273 [Flow] Target endpoint for 66627128 can not be built!
    07-Dec-2015 23:14:56.739 [CM102001]: Authentication failed for AuthFail Recv Req REGISTER from 192.168.1.70:5061 tid=-6323ff59 Call-ID=d2da8ed2@192.168.1.70:
    REGISTER sip:192.168.1.99:5060 SIP/2.0
    Via: SIP/2.0/UDP 192.168.1.70:5061;branch=z9hG4bK-6323ff59;rport=5061
    Max-Forwards: 70
    Contact: <sip:90001@192.168.1.70:5061>;expires=60;+sip.instance="<urn:uuid:00000000-0000-0000-0000-9cadef0141d1>"
    To: <sip:90001@192.168.1.99>
    From: <sip:90001@192.168.1.99>;tag=SP22a16a4eb23c2f145
    Call-ID: d2da8ed2@192.168.1.70
    CSeq: 49153 REGISTER
    Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER, UPDATE
    Proxy-Authorization: DIGEST algorithm=MD5,nonce="414d535c0c7679c046:df0ff68853cec574a9917aeda4b8c4f3",realm="3CXPhoneSystem",response="0fae6e31a628638d13db84475c712efd",uri="sip:192.168.1.99:5060",username="90001"
    Supported: replaces
    User-Agent: OBIHAI/OBi110-1.3.0.2872
    Content-Length: 0

    ; Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings
    07-Dec-2015 23:14:28.281 [CM102001]: Authentication failed for AuthFail Recv Req REGISTER from 192.168.1.70:5061 tid=-237c5e00 Call-ID=daf2ab4c@192.168.1.70:
    REGISTER sip:192.168.1.99:5060 SIP/2.0
    Via: SIP/2.0/UDP 192.168.1.70:5061;branch=z9hG4bK-237c5e00;rport=5061
    Max-Forwards: 70
    Contact: <sip:90001@192.168.1.70:5061>;expires=60;+sip.instance="<urn:uuid:00000000-0000-0000-0000-9cadef0141d1>"
    To: <sip:90001@192.168.1.99>
    From: <sip:90001@192.168.1.99>;tag=SP22fd6b36564aca7e3
    Call-ID: daf2ab4c@192.168.1.70
    CSeq: 5397 REGISTER
    Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER, UPDATE
    Proxy-Authorization: DIGEST algorithm=MD5,nonce="414d535c0c7679a409:18fefe9f4af1d2974c80a85e4837d295",realm="3CXPhoneSystem",response="9a354ed9df0238b300021a636df0e7f4",uri="sip:192.168.1.99:5060",username="90001"
    Supported: replaces
    User-Agent: OBIHAI/OBi110-1.3.0.2872
    Content-Length: 0

    ; Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings
    07-Dec-2015 23:13:58.060 [CM102001]: Authentication failed for AuthFail Recv Req REGISTER from 192.168.1.70:5061 tid=-6cee2a13 Call-ID=6d030847@192.168.1.70:
    REGISTER sip:192.168.1.99:5060 SIP/2.0
    Via: SIP/2.0/UDP 192.168.1.70:5061;branch=z9hG4bK-6cee2a13;rport=5061
    Max-Forwards: 70
    Contact: <sip:90001@192.168.1.70:5061>;expires=60;+sip.instance="<urn:uuid:00000000-0000-0000-0000-9cadef0141d1>"
    To: <sip:90001@192.168.1.99>
    From: <sip:90001@192.168.1.99>;tag=SP22fd6b36564aca7e3
    Call-ID: 6d030847@192.168.1.70
    CSeq: 37482 REGISTER
    Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER, UPDATE
    Proxy-Authorization: DIGEST algorithm=MD5,nonce="414d535c0c76798564:0ee9bf683d02c4f0344cd925b8ab694e",realm="3CXPhoneSystem",response="5fcb0e2db5c1d21d7cde8d9dcbf62a5e",uri="sip:192.168.1.99:5060",username="90001"
    Supported: replaces
    User-Agent: OBIHAI/OBi110-1.3.0.2872
    Content-Length: 0

    ; Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings
    07-Dec-2015 23:13:27.840 [CM102001]: Authentication failed for AuthFail Recv Req REGISTER from 192.168.1.70:5061 tid=-4c052743 Call-ID=742cbca4@192.168.1.70:
    REGISTER sip:192.168.1.99:5060 SIP/2.0
    Via: SIP/2.0/UDP 192.168.1.70:5061;branch=z9hG4bK-4c052743;rport=5061
    Max-Forwards: 70
    Contact: <sip:90001@192.168.1.70:5061>;expires=60;+sip.instance="<urn:uuid:00000000-0000-0000-0000-9cadef0141d1>"
    To: <sip:90001@192.168.1.99>
    From: <sip:90001@192.168.1.99>;tag=SP22fd6b36564aca7e3
    Call-ID: 742cbca4@192.168.1.70
    CSeq: 47207 REGISTER
    Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER, UPDATE
    Proxy-Authorization: DIGEST algorithm=MD5,nonce="414d535c0c76796734:e78be0c6ec28dd205a1a1ac52904a36d",realm="3CXPhoneSystem",response="0a1e110f7031ed6798b522a125e12b42",uri="sip:192.168.1.99:5060",username="90001"
    Supported: replaces
    User-Agent: OBIHAI/OBi110-1.3.0.2872
    Content-Length: 0

    ; Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings
    07-Dec-2015 23:13:23.567 Set log verbosity to MaxLevel = 2, Severity mask = 7
    07-Dec-2015 23:13:23.519 Supported Mime Type added:MESSAGE(x-chat/control)
    07-Dec-2015 23:13:23.518 [CM506005]: Public IP=37.210.189.47 is used for WAN communications through local interface with IP=192.168.1.99
    07-Dec-2015 23:13:22.758 [EC200002]: Media server is connected:
    application:DESKTOP-P61MJEU:0/MediaServer
    local:127.0.0.1:5482
    remote:127.0.0.1:62892
    07-Dec-2015 23:13:22.451 [CM501006]: Default Local IP address: [192.168.1.99]
    07-Dec-2015 23:13:22.443 [CM501002]: Version: 14.0.45008.0
    07-Dec-2015 23:13:22.443 [CM501001]: Start 3CX PhoneSystem Call Manager
    07-Dec-2015 23:13:22.443 [CM501010]: License Info: Load Failed - 26
    07-Dec-2015 23:13:22.333 Set tenant started signal for MediaServer
    07-Dec-2015 23:13:22.253 [CM501007]: *** Started Calls Controller thread ***
     
  2. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    11,079
    Likes Received:
    324
    I'm seeing two port numbers (5060 and 5061) associated with IP 192.168.1.70 Are you using two devices on the Obi?
    Don't forget that you must specify the correct port number in the 3CX trunk settings to be used in outbound calls.

    While I've had an Obi for quite some time, I have not attempted any outbound calls over it. I used to use it for incoming (only) PSTN and now for Google Voice incoming only. I haven't had the patience to sit down and figure the way they do out their dialling plans.
     
  3. Ash91

    Joined:
    Dec 7, 2015
    Messages:
    7
    Likes Received:
    0
    Thanks for the reply. I just use one OBI device. And i have got the connection from LINE port of the OBI. I dont know why i can receive only incoming calls? I cannot figure out the problem.
     
  4. Ash91

    Joined:
    Dec 7, 2015
    Messages:
    7
    Likes Received:
    0
    Hi please check the attached image of the gateway settings.
     

    Attached Files:

  5. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    11,079
    Likes Received:
    324
    The 3CX settings for the gateway show that outgoing calls will route to it's IP and port 5060. I seem to recall that the Obi is similar to the Cisco SPA-3102 in that there is an FXS and FXO portion and each use a separate local port. If the FXO circuit is assigned port 5061 on the Obi, then 3CX has to be told to use that port for outbound calls.
     
Thread Status:
Not open for further replies.