Adding PSTN as SIP Trunk with Patton 4112

Status
Not open for further replies.

Andriy

Forum User
Advanced Certified
Joined
Apr 14, 2018
Messages
183
Reaction score
16
Hello !

I have a PSTN line that I would like to add to 3CX as a Gateway using Patton Smart Node 4112 so that I can use that Analog line as if it was a SIP Trunk in 3CX

I have 3CX 15.5 hosted by 3CX (aka 3CX express). Therefore I beleive this solution is not supported, but I have heard that it is possible with 3CX SBC.

So what I did is -
0) Created a SBC on Raspberry and connected it to my network. (192.168.1.248)
1) upgraded firmware on Patton 4112 and connected it to the PSTN phone line and LAN
2) then I proceeded to 3CX > SIP Trunks > Add Gateway > and Generated device config, replaced 3cx IP with IP address of my Raspberry SBC and uploaded it to my Patton.

my setup still does not work. Are there any additional steps I should take or are any of my settings incorrect?
(Please check screenshots)

Please advise
 

Attachments

  • 1.png
    1.png
    120.4 KB · Views: 14
  • 2.png
    2.png
    78.7 KB · Views: 12
If you do some searches through the forums, you will come across a number of posts where users have attempted to set up a PSTN gateway off a hosted PBX.I seem to recall that one user had it working. It is however not officially supported, and using an SBC for a PSTN gateway is probably not the way to go. VPN should work for you, and I have managed to get a single line unit (SPA3102) working. The big difference is that an ATA simply registers. A PSTN gateway registers, and you have to tell 3CX where to send a call (IP and port) in the trunk settings.
 
Thank you for your reply,
I have searched the forums - and from what I have found - the only way to set this up with 3cx Express - is SBC. Please correct if I am wrong and how should I proceed without SBC.

As for telling 3CX where to send a call - (IP and port) in the trunk settings - that could be a problem - I just put 5060 and IP address of my Patton in there? In that case Patton should have a decicated public IP which it has not. Thus need for SBC ?
 
Well...the issues you are going to encounter, if using the gateway through an SBC will be that while supporting registration of a device, you can't be using the same port (5060?) behind the remote router for the SBC, and that device. For an incoming call, to the gateway, 3CX will address as the remote public IP and the port of the device. For calls the other direction, 3CX will see the device as the public IP and the port of the SBC. This may not only cause issues for call set up, but the audio port routing may have some problems as well.

You may have some luck if you had a public IP available for the gateway.. Short of that, or VPN, it may require some "creative" port forwarding at the remote end, and avoiding the SBC altogether.
 
Status
Not open for further replies.

Forum statistics

Threads
111,898
Messages
589,614
Members
164,764
Latest member
billza209