my w52p phones can't complete an external call...

Discussion in '3CX Phone System - General' started by asinshesq, Jul 26, 2014.

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

    Joined:
    Apr 5, 2014
    Messages:
    72
    Likes Received:
    0
    I have three yealink wired phones (two t20ps and one t46g) and two yealink w52p wireless phones on my lan (connected via 3cx of course), and I am using a patton 4112fxo to connect my voip phones to an outside pstn service. The wired phones work fine, but the wireless phones won't dial out. When I try to dial out with one of the wireless phones (using the outgoing rule that a prefix of 1 means to dial out), the phone appears to connect (the timer on the lcd starts and the phone does not time out), but I never hear the tone indicating the number I have dialed is ringing and no matter how long I wait the number never seems to actually get dialed).

    In 3cx under options for the extension, I have confirmed that I did NOT disable external so that's not the issue.

    I can also confirm that the wireless phones make calls to other extensions without a problem. And I can confirm that the wireless phones receive external and internal calls fine.

    When I look at the log for a failed attempt to dial out via a wireless phone, it looks like it is working but in fact it is not. Here's the nonverbose log for a failed outgoing call:

    And in case it's helpful, here's the verbose log for that call (though I'm not sure if it captures the entire thing in verbose mode):

     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  2. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,762
    Likes Received:
    286
    It may be worthwhile comparing a working call against one that does not, line for line.
    The one thing I noticed id that there are two IPs with port 5062 "attached". When I see a port other than 6060, it "says" additional line or trunk on a device. In the logs I see 192.168.1.202:5062 and 1892.168.1.206:5062 , that raises a red flag right off the bat

    You may want to double check the IPs and ports assigned to the gateway and in the trunk setting of 3CX , to see if they match.
     
  3. asinshesq

    Joined:
    Apr 5, 2014
    Messages:
    72
    Likes Received:
    0
    Thanks, leejor. My gateway has two fxo ports even though I am only using 1. Those ports show up in ports/trunks as virtual extensions 10000 and 10001. I tried deleting the extra gateway port in the gateway itself (and unregistering that port/virtual extension in 3cx) and rebooting 3cx and the gateway and that didn't help. Would love to know how to actually delete that port/virtual extension in 3cx rather than just deregistering. Any idea how to do that?

    But on the original question, the log of calls that worked looks just like the log of calls that didn't work. But then I rebooted the w52p base stations and they suddenly started working again (making and receiving outside calls fine). Not sure what was up with that!
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  4. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,762
    Likes Received:
    286
    The gateway may have two trunks (virtual extensions) assigned, however in most cases this will involve one IP and several ports (5060, 5061, 5062...etc) assigned to that gateway if each trunk (PSTN phone line) is individually accessible. Some gateways do this using a prefix on the dialled number.
    The fact that the logs were showing two different IPs , both using port 5062, led me to believe that something was not data-filled correctly
     
Thread Status:
Not open for further replies.