• V20: 3CX Re-engineered. Get V20 for increased security, better call management, a new admin console and Windows softphone. Learn More.

NAT connection issue (cisco+3cx+spa3102)

Status
Not open for further replies.

optix

Joined
Mar 19, 2008
Messages
7
Reaction score
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
 
Have you check the following configuration provided by 3CX team. http://www.3cx.com/support/cisco-configuration.html
 
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.
 
PBX log (Server Status page) provides some additional information.
You can post it here. It can give us a chance to help you.

Thanks
 
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:[email protected]:52609/103, sip:[email protected]:52534;transport=udp/103]
01:42:05.171	CallCtrl::onLegConnected	[CM503007]: Call(1): Device joined: sip:[email protected]:5061
01:42:05.156	CallCtrl::onLegConnected	[CM503007]: Call(1): Device joined: sip:[email protected]: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:[email protected]:5061]
01:42:04.968	CallCtrl::onIncomingCall	[CM503001]: Call(1): Incoming call from Ext.103 to [sip:[email protected]]
01:39:23.890 	ExtnCfg::updateContact 	[CM504001]: Ext.103: new contact is registered. Contact(s): [sip:[email protected]:52609;transport=udp/103, sip:[email protected]:52534;transport=udp/103]

After unregistering, 3CX is still routing call (FXO line is busy):
3cxpbxyz4.jpg


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

Getting Started - Admin

Latest Posts

Forum statistics

Threads
141,930
Messages
751,258
Members
145,371
Latest member
Dozer302
Get 3CX - Absolutely Free!

Link up your team and customers Phone System Live Chat Video Conferencing

Hosted or Self-managed. Up to 10 users free forever. No credit card. Try risk free.

3CX
A 3CX Account with that email already exists. You will be redirected to the Customer Portal to sign in or reset your password if you've forgotten it.