NAT connection issue (cisco+3cx+spa3102)

Discussion in '3CX Phone System - General' started by optix, Mar 19, 2008.

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

    Joined:
    Mar 19, 2008
    Messages:
    7
    Likes Received:
    0
    Hi all,

    I have 3CX system running on machine behind NAT. PSTN gateway is Linksys SPA 3102, router in front of the machine is Cisco 1710 (currently doing static IP translation for that machine). Everything works fine when local clients communicate with each other, and via PSTN. Problems start when client from outside local area network tries to connect to PBX. They can register, initiate the connection, but when the other side picks up there's no sound, disconnecting is impossible and results in blocking 3CX (it shows that client is still dialing, and only reset helps unblocking it / unregistering client).

    Could anyone point me out to direction for solving this? I'm not still sure whether problem lies in router configuration (most likely, but it is doing static NAT so it should 'provide' public IP to the machine), 3CX configuration, Linksys configuration, clients on the other side of the network (also behind NAT), or combination of those...

    Thanks
     
  2. bhavank

    bhavank New Member

    Joined:
    Apr 24, 2007
    Messages:
    109
    Likes Received:
    0
    Have you check the following configuration provided by 3CX team. http://www.3cx.com/support/cisco-configuration.html
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. optix

    Joined:
    Mar 19, 2008
    Messages:
    7
    Likes Received:
    0
    I have.
    All ports are forwarded to the PBX machine (ip nat inside source static 10.10.10.202 89.216.x.x), and firewall is not running.
     
  4. SY

    SY Well-Known Member
    3CX Support

    Joined:
    Jan 26, 2007
    Messages:
    1,825
    Likes Received:
    2
    PBX log (Server Status page) provides some additional information.
    You can post it here. It can give us a chance to help you.

    Thanks
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. optix

    Joined:
    Mar 19, 2008
    Messages:
    7
    Likes Received:
    0
    Here it is:

    I'm copying log when client from outside network has registered on the system, made a call to FXO (no tone on the client side), hung-up (3CX server hasn't noticed that the line is disconnected) and finally unregistered from the server.

    Code:
    01:42:35.468	ExtnCfg::updateContact	[CM504002]: Ext.103: a contact is unregistered. Contact(s): [sip:103@89.186.92.111:52609/103, sip:103@89.216.209.3:52534;transport=udp/103]
    01:42:05.171	CallCtrl::onLegConnected	[CM503007]: Call(1): Device joined: sip:10000@10.10.10.137:5061
    01:42:05.156	CallCtrl::onLegConnected	[CM503007]: Call(1): Device joined: sip:103@89.186.92.111:52609
    01:42:05.156	Line::printEndpointInfo	[CM505002]: Gateway:[Telekom] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Linksys/SPA3102-5.1.7(GW)] Transport: [sip:10.10.10.202:5060]
    01:42:05.031	CallCtrl::onSelectRouteReq	[CM503004]: Call(1): Calling: PSTNline:10000@[Dev:sip:10000@10.10.10.137:5061]
    01:42:04.968	CallCtrl::onIncomingCall	[CM503001]: Call(1): Incoming call from Ext.103 to [sip:03060606@10.10.10.202]
    01:39:23.890 	ExtnCfg::updateContact 	[CM504001]: Ext.103: new contact is registered. Contact(s): [sip:103@77.93.254.233:52609;transport=udp/103, sip:103@89.216.209.3:52534;transport=udp/103]
    
    After unregistering, 3CX is still routing call (FXO line is busy):
    [​IMG]

    Only way to disconnect and free the FXO line is to manually stop all 3CX processes and reboot SPA.
     
Thread Status:
Not open for further replies.