Multiple SIP trunks with one Patton Gateway (SN4114)

[Syed hamza Faiz]

Hey Everyone , i want to configure multiple sip trunks with my patton gateway , i am unable make trunk up even after configuring a new gateway in patton with correct Registration settings and using different ports as welll like 5061 , 5062 .

 

[providencetg]

Hi, not sure I am understanding your question because a Patton SN4114 is not for SIP trunks but for four analog lines.

Alexander

 

[eddv123]

I believe this is what you want to achieve. It is a common request on this forum in regards to Patton Please read this guide attached.

 

[Syed hamza Faiz]

I believe this is what you want to achieve. It is a common request on this forum in regards to Patton Please read this guide attached.

yes , i have followed the same manual can you see where i am wrong , stats attached below

Gateway 1



Gateway 2


Status


Configuration of patton also attached

 

[Syed hamza Faiz]

Hi, not sure I am understanding your question because a Patton SN4114 is not for SIP trunks but for four analog lines.

Alexander

Sorry , yeah its a gateway

 

[eddv123]

I will PM you my example template shortly so you can make a comparison.

 

[eddv123]

I have instead compared templates using ExamDiff, I think this will help you more if you see my points. Lots of issues with your template here. For example:

* You dont need "service hunt-group HG_TO_FXO" calls are not hunting in this setup method - they are individual trunks. HG_TO_FXO call routing.

* You have only 2 SIP interfaces in this template - this is a 4114 no ? please advise if you are using all 4 ports.

* Your authentication realm looks like:

authentication-service AS_ALL_LINES
realm 1 3CXPhoneSystem
username 10000 password *********

And should look like:

authentication-service AUTH_SVC_3CX
realm 1 3CXPhoneSystem
username 10001 password *************
username 10002 password *************
username 10003 password *************
username 10004 password *************

One set for each trunk you are using - if 2 (as per the above ) then just 2 are needed.

* You only have a single location service - you need 4 (or 2 if you are only using 2 ports):

location-service LS_10000
domain 1 192.168.1.122

identity-group default
authentication outbound
authenticate 1 authentication-service AS_ALL_LINES username 10000

identity 10000
authentication outbound
authenticate 1 authentication-service AS_ALL_LINES

registration outbound
registrar 192.168.1.122 5060
lifetime 300
register auto

For example a full set of the above for LS_10000, 10001,10002 etc.

Your Ethernet and FXO ports seem fine, please check it out and if you want my template for reference then I can provide still, the only point being however is that mine is for a Trintiy based 4141 FXO so there are a few minor differences.

 

[Syed hamza Faiz]

I have instead compared templates using ExamDiff, I think this will help you more if you see my points. Lots of issues with your template here. For example:

* You dont need "service hunt-group HG_TO_FXO" calls are not hunting in this setup method - they are individual trunks. HG_TO_FXO call routing.

* You have only 2 SIP interfaces in this template - this is a 4114 no ? please advise if you are using all 4 ports.

* Your authentication realm looks like:

authentication-service AS_ALL_LINES
realm 1 3CXPhoneSystem
username 10000 password *********

And should look like:

authentication-service AUTH_SVC_3CX
realm 1 3CXPhoneSystem
username 10001 password *************
username 10002 password *************
username 10003 password *************
username 10004 password *************

One set for each trunk you are using - if 2 (as per the above ) then just 2 are needed.

* You only have a single location service - you need 4 (or 2 if you are only using 2 ports):

location-service LS_10000
domain 1 192.168.1.122

identity-group default
authentication outbound
authenticate 1 authentication-service AS_ALL_LINES username 10000

identity 10000
authentication outbound
authenticate 1 authentication-service AS_ALL_LINES

registration outbound
registrar 192.168.1.122 5060
lifetime 300
register auto

For example a full set of the above for LS_10000, 10001,10002 etc.

Your Ethernet and FXO ports seem fine, please check it out and if you want my template for reference then I can provide still, the only point being however is that mine is for a Trintiy based 4141 FXO so there are a few minor differences.

Thanks mate , the manual you shared really helped . it worked . now my both trunks are up also i altered the routing table as well now both lines i manage separately , thats why no hunting group .

if a call comes from sip 1 it will be out from fXO-0 and vise versa .
if a call comes from sip 2 it will be out from FXO-1 and vise versa .

 

[eddv123]

Yes that's it - generally part of the problem for this scenario is generically 3CX will provision the gateway with the ability to try each port on an outbound call, in the event one is in use it will move onto the next.

If you have a working Smartware config it would be useful to post it up (obviously removing any sensitive information) as I said previously I only deal mostly with the Trinity based models these days and don't in fact have any older Smartware variants to hand there are slight differences in the configuration file.

 

[Syed hamza Faiz]

here is my patton configuration

 

[eddv123]

Ive checked it over and all good, the one area where problems sometimes arise (and including this merely for the sake of the ticket) is that the add the increments (5060,5062,5063 etc) on the SIP interfaces also:

interface sip IF_SIP
bind context sip-gateway GW_SIP
early-disconnect
route call dest-table RT_SIP_TO_FXO
remote 192.168.1.122 5060

If using multiple interfaces these all need to stay on 5060 as 3CX will ignore the incoming SIP INVITE on incoming calls (3CX only supports a single port for SIP - by default 5060).