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 in Win 2003 server, cannot do outgoing calls

Discussion in '3CX Phone System - General' started by scu, Jan 26, 2008.

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

    scu

    Joined:
    Jan 26, 2008
    Messages:
    19
    Likes Received:
    0
    I have a grandstream 4104 VOIP Gateway, 3cx installed in windows 2003 server, and using a 3cx client. I have followed the instructions to set up 3cx and the gateway, but the call gets terminated when i call out. I am just using straight VOIP Analog Gateway with a PSTN Line so I dont think I will have problems with firewall settings to do outgoing calls right? I can receive calls but not do outgoing. Any resolution is greatly appreciated.

    This is the Server Log:
    17:20:00.437 Call::Terminate [CM503008]: Call(26): Call is terminated
    17:20:00.437 Call::Terminate [CM503008]: Call(26): Call is terminated
    17:19:44.015 CallCtrl::eek:nLegConnected [CM503007]: Call(26): Device joined: sip:10000@192.168.0.160:5060
    17:19:44.000 CallCtrl::eek:nLegConnected [CM503007]: Call(26): Device joined: sip:102@192.168.0.2:5070;rinstance=be73a0101052427c
    17:19:43.984 Line::printEndpointInfo [CM505002]: Gateway:[PSTN1] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Grandstream GXW4104 (HW 0001, Ch:8) 1.0.0.55] Transport: [sip:192.168.0.10:5060]
    17:19:43.890 CallCtrl::eek:nSelectRouteReq [CM503004]: Call(26): Calling: PSTNline:10000@[Dev:sip:10000@192.168.0.160:5060]
    17:19:43.828 CallCtrl::eek:nIncomingCall [CM503001]: Call(26): Incoming call from Ext.102 to [sip:3663002@192.168.0.10:5060]
     
  2. yadac123

    Joined:
    Jan 19, 2008
    Messages:
    24
    Likes Received:
    0
    didn't work with PTSN but I see ur behind a router. port forward 5060 and try again. good luck
     
Thread Status:
Not open for further replies.