Outgoing calls set to private

Discussion in '3CX Phone System - General' started by gunners, Jul 7, 2016.

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

    Joined:
    Nov 6, 2014
    Messages:
    20
    Likes Received:
    0
    We are using 3CX with a patton PSTN gateway.

    For some reason outgoing calls are set to private number, where would i go to change this?
     
  2. lneblett

    lneblett Well-Known Member

    Joined:
    Sep 7, 2010
    Messages:
    2,083
    Likes Received:
    61
    If I understand correctly, you are using a Patton gateway to interconnect to the PSTN network (FXO). When a call is made from the 3CX system, the callee receives a caller-ID of "private number" and no number or name is delivered to the callee.

    Caller-ID (CID) info is usually provided by the carrier given your use of a PSTN gateway. You should be able to take a regular analog phone and connect this to one of the lines and dial to a regular phone with CID capability and see what is delivered.

    You may want to contact your service provider about the issue.

    In the US, one can request and pay for an unlisted number in which case the CID will not be delivered. I do not know what country you are in, so your situation may be different, but a call should help.
     
  3. gunners

    Joined:
    Nov 6, 2014
    Messages:
    20
    Likes Received:
    0
    I have plugged an anlog handset directly into the PSTN line and done a test call, when using the analog handset it shows the number.
    I will try changing the CID on 3cx and see how that goes.
     
  4. gunners

    Joined:
    Nov 6, 2014
    Messages:
    20
    Likes Received:
    0
    So I have found the problem. All of the calls are going out of the wrong gateway.

    Our patton PSTN gateway is not registering with 3cx. I have checked the logs on both 3cx and the Patton PSTN Gateway.

    On the 3cx log it appears that the patton gateway is blocking because of too many failed authentication attempts. Below is the log.

    So far I have been though each virtual extension and they all match and I have also generated a new configuration script and uploaded it to the device.

     
  5. NickD_3CX

    NickD_3CX Support Team
    Staff Member 3CX Support

    Joined:
    Jun 2, 2014
    Messages:
    1,367
    Likes Received:
    83
    Is this a V14 3CX Phone System or an earlier version?
     
  6. gunners

    Joined:
    Nov 6, 2014
    Messages:
    20
    Likes Received:
    0
    This is running v12.5.41542.997
     
  7. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,839
    Likes Received:
    298
    Did this just all start...out of the blue, or were some changes made somewhere, then the problems began? Did you do any cutting and pasting with the passwords or authentication information?
     
  8. gunners

    Joined:
    Nov 6, 2014
    Messages:
    20
    Likes Received:
    0
    We added a SIP trunk line to the 3cx
     
  9. lneblett

    lneblett Well-Known Member

    Joined:
    Sep 7, 2010
    Messages:
    2,083
    Likes Received:
    61
    See if the IP of the patton is now blacklisted by 3CX.

    Was the SIP path a secondary on the outbound routes?
     
  10. gunners

    Joined:
    Nov 6, 2014
    Messages:
    20
    Likes Received:
    0
    Yes SIP is the secondary path on the outbound route.

    Yes the IP is blacklisted by 3cx.


    I have also reconfigured a new PSTN Gateway in 3cx and redeployed the configuration file(after resetting the Patton gateway to factory defualts)

    I have added it to the allow list but the problem still persists.
     
  11. gunners

    Joined:
    Nov 6, 2014
    Messages:
    20
    Likes Received:
    0
    Still getting this error

    14-Jul-2016 10:12:24.052 [CM102001]: Authentication failed for AuthFail Recv Req REGISTER from 192.168.15.20:5061 tid=ee9817089c76d6acc Call-ID=8462d544310422ab:
    REGISTER sip:192.168.15.1:5060 SIP/2.0
    Via: SIP/2.0/UDP 192.168.15.20:5061;branch=z9hG4bKee9817089c76d6acc
    Max-Forwards: 70
    Contact: <sip:90002@192.168.15.20:5061>
    To: <sip:90002@192.168.15.1>
    From: <sip:90002@192.168.15.1>;tag=eb66e56abc
    Call-ID: 8462d544310422ab
    CSeq: 1558 REGISTER
    Expires: 300
    Proxy-Authorization: Digest username="90002",realm="3CXPhoneSystem",nonce="414d535c0d9769e771:5c788ec421de5d8be0403ea00f4680c2",uri="sip:192.168.15.1:5060",response="0403462d2ce6cb807b41a4ee2bcbe4d4",algorithm=MD5
    User-Agent: Patton SN4114 JO EUI 00A0BA0A8E6E R6.3 2013-05-01 H323 SIP FXS FXO M5T SIP Stack/4.1.12.18
    Content-Length: 0

    ; Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings
    14-Jul-2016 10:12:23.048 [CM102001]: Authentication failed for AuthFail Recv Req REGISTER from 192.168.15.20:5060 tid=60ebb654e8ee9bc4e Call-ID=7f6d8922455d1bea:
    REGISTER sip:192.168.15.1:5060 SIP/2.0
    Via: SIP/2.0/UDP 192.168.15.20:5060;branch=z9hG4bK60ebb654e8ee9bc4e
     
  12. lneblett

    lneblett Well-Known Member

    Joined:
    Sep 7, 2010
    Messages:
    2,083
    Likes Received:
    61
    Well, for whatever reason, the credentials of the Patton are not liked.

    My suggestion is to manually go into the Patton and validate that the credentials match by manually entering them. I cannot explain why this occurred, but if a manual intervention does the trick, then I guess it solves the issue.

    My only guess is that perhaps the provisioning file did not get re-created and the old one was inserted.
     
Thread Status:
Not open for further replies.