Several Problems

Discussion in '3CX Phone System - General' started by Bob Denny, Feb 13, 2010.

Thread Status:
Not open for further replies.
  1. Bob Denny

    Bob Denny New Member

    Joined:
    Feb 21, 2009
    Messages:
    131
    Likes Received:
    2
    I am using Gateway 2.0.8743 with 3CX 7.1.7139. I cannot get outbound calling working, and I had a big problem with the gateway 2.0.9919.

    I have port 10003/6060 working for inbound calls just fine. PSTN 10003 is set to inbound calls only. I have created a PSTN port 10004/6062 in 3CX and set up outbound rule 02+ to route to it, with it set for outbound calls only. Then I created a second port in the gateway, using the same numbers (10004/6062) and tied it to a separate Skype account which I successfully created. When I start the gateway, both ports connect to both 3CX and Skype and show registered and connected-on hook.

    Now for the first problem: After doing this, inbound calls stopped working. A remote Skype calling into the inbound Skype account immediately disconnects with Call Failed. Prior to creating the second port in the gateway, calls to this Skype account worked fine. If I then remove the second (1004/6062) port from the gateway, inbound calls again work.

    Second problem: With the second (outbound) gateway port configured, I cannot make outbound calls. I can see the routing i correct in the 3CX log, the number is correctly stripped, and it is routing to the correct PSTN port (10004). Yet an outbound call fails with device offline.

    Third problem: I downloaded the 2.0.9919 update from http://www.3cx.com/forums/3cx-gateway-for-skype-v2-10511.html and installed it. The result was the gateway software was removed except for a few stray DLLs in the Program Files\3CX Gateway For Skype\ folder! The new Start menu entry contained only Uninstall, no entry for the Gateway Monitor. TO recover I had to uninstall 2.0.9919 and reinstall 2.0.8743 (thank heaven I had archived the installer!), and reconfigure the master/inbound port. That went well, and I am now back to being able to receive calls.

    Any thoughts on the above three issues would be appreciated. I'd like to solve the first one first, as that is a showstopper. It seems as though adding that second port to the gateway kills its ability to receive calls.
     
  2. Vali_3CX

    Vali_3CX Well-Known Member
    Staff Member 3CX Support

    Joined:
    Dec 12, 2008
    Messages:
    1,496
    Likes Received:
    67
    Hi Bob

    If I properly understand, it seems to be a case of improper use of "master"- type configuration. Master channel is designed to act as an inbound calls dispatcher, "routing" these to available "slaves". Because of this role, it does not accept outbound calls. Also, it is the last one which really answer a call.
    Therefore, my advice is to make the "master" channel a normal one, by simply unchecking this flag on its configuration and tell me how it's going.
    Also, you may read this topic, http://www.3cx.com/forums/skype-outgoing-calls-10519.html#p53917 describing quite well master channel behavior.

    Regards
    vali

    P.S. The third problem I will forward it to our tech support since it appears to be an installer issue.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. Bob Denny

    Bob Denny New Member

    Joined:
    Feb 21, 2009
    Messages:
    131
    Likes Received:
    2
    Vali --

    Thank you that did it!!! I only have the one port, but since we rarely yse Skype, that should be sufficient. I appreciate your help.

    My other question is "Why did adding the slave prevent incoming calls?" Should 3CX be configured for BOTH incoming AND outgoing on BOTH the master and the slave? I didn't do that.
     
  4. Vali_3CX

    Vali_3CX Well-Known Member
    Staff Member 3CX Support

    Joined:
    Dec 12, 2008
    Messages:
    1,496
    Likes Received:
    67
    Hi, Bob
    In master-slave configuration, incoming calls are routed by master to first available slave. From now, you have to check what's happen with this slave's corresponding PSTN line incoming calls on the PBX - end call, connect to extension, ring group and so on. If this one is set to "End call", for instance, you will get Not Available. If is set to "connect to extension" but this extension is not registered or busy, also you will get not available.
    I suggest you that, while skype gateway is running, when such kind of issue happens, to do a right-click on the slave and, from menu, choose Tracelog and try to see what's happening (traces are quite "user-friendly")
    Regards
    vali
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
Thread Status:
Not open for further replies.