Patton SN4171 interface binding

Status
Not open for further replies.

Kane Wong

Free User
Joined
Oct 13, 2018
Messages
233
Reaction score
9
Hi;

When I compare the startup-config file and the 3CX generated gwcfg file, it is found that the interface binding is different.

On Patton original startup-config, it is... I think the port e1t1 0 0 is for PRI 0/0, correct?

port ethernet 0 0
bind interface ROUTER WAN
no shutdown

port e1t1 0 0
port-type t1
linecode b8zs
clock slave
framing esf
no shutdown

On 3CX gwcfg file, it is... and my Patton SN4171 has one Eth 0/0 and one PRI 0/0 only.

port ethernet 0 0
bind interface ROUTER LAN
no shutdown


port ethernet 0 1
bind interface ROUTER WAN
no shutdown

port e1t1 0 1
shutdown
port e1t1 0 2
shutdown
port e1t1 0 3
shutdown

What should I do to make sure the correct config file for 3CX to be loaded on Patton?
 
This isn't a problem, most Patton gateways come with an ETH 0/1 and ETH 0/0 port so you can assign (if desired) a WAN and LAN interface to either port.

You only have E1 port 0/0 on this device as stated already, this means that the other ports will be in shutdown mode and are un-assignable. If you look at the config file for 3CX you will see that this port will be assigned to something like an interface PRI_IF_0 (depending on the terminology used).

Pattons are very flexible devices interfaces are creatable but ports are static based on the physical amount on the device.

I would disregard what you are seeing in the standard configuration and a @cobaltit says just follow the 3CX guide and you cant go wrong.

Note: Use gateways either locally to 3CX or across a LAN >> LAN connection (not SBC or STUN support currently).
 
thank you.

I also found these settings, should I delete them from 3CX config file and only leave "shut down" for port e1t1 0 1 /port e1t1 0 2 / port e1t1 0 3 ? Because I have one PRI 0/0 port only which is "port e1t1 0 0".

port e1t1 0 3
port-type t1
clock auto
linecode b8zs
framing esf
encapsulation q921

q921
uni-side auto
encapsulation q931

q931
protocol ni2
uni-side user
bchan-number-order ascending
encapsulation cc-isdn
bind interface SWITCH IF_ISDN_03

port e1t1 0 3
no shutdown

port e1t1 0 2
port-type t1
clock auto
linecode b8zs
framing esf
encapsulation q921

q921
uni-side auto
encapsulation q931

q931
protocol ni2
uni-side user
bchan-number-order ascending
encapsulation cc-isdn
bind interface SWITCH IF_ISDN_02

port e1t1 0 2
no shutdown

port e1t1 0 1
port-type t1
clock auto
linecode b8zs
framing esf
encapsulation q921

q921
uni-side auto
encapsulation q931

q931
protocol ni2
uni-side user
bchan-number-order ascending
encapsulation cc-isdn
bind interface SWITCH IF_ISDN_01

port e1t1 0 1
no shutdown
 
Last edited:
No you should follow the guide and do exactly what it says.
 
Good. Thank you.
 
The provisioning file does not require any alterations as standard however please confirm where the Patton is in regards to the system.

If local or via VPN connections to remote PBX just follow the guide as stated.
 
thank you.

After upload the 3CX generated gwcfg file to the Patton device, I can see the "Green Light" in SIP Trunks page lit, I believed, that means the Patton device registered with the 3CX server successful.
 
Yes, test in and outbound calls next and report back if there are any issues
 
Status
Not open for further replies.

Forum statistics

Threads
111,935
Messages
589,823
Members
164,816
Latest member
natedog