Patton SN4120 V16 BRI ISDN

[James Dyke]

Hi Guys,

Although not on the supported list, have people got it working?

James.

 

[Saqqara]

Check out https://www.3cx.com/voip-gateways/smartnode-isdn/

If the device is running Trinity firmware check out - https://www.patton.com/support/kb_art.asp?art=478&p=0

 

[James Dyke]

Hi @Saqqara thanks for the above, i have seen this BUT I'm confused as BRI is no longer on the supported list:
https://www.3cx.com/voip-gateways/

 

[Saqqara]

Check my first link, it does show 4120.

You can add the device under SIP gateways.

 

[eddv123]

OK here is the current situation for both software versions of gateway from Patton.
https://www.3cx.com/voip-gateways/

Smartware supported BRI gateway (4120):

Model has fallen off the supported list but the PBX still has a supported template and guide:
https://www.3cx.com/voip-gateways/smartnode-isdn/

Trinity BRI gateway (SN4131).

I have heard (but not official) coming in the next release of 3CX (full support) for the time being:
https://support.patton.com/index.ph...tton-trinity-smartnode-configuration-with-3cx

 

[eddv123]

See the changelog for the next Alpha version here:
https://www.3cx.com/blog/change-log/phone-system-change-log/

 

[James Dyke]

Hi All, patton is registered, but no calls are in or out ? any ideas
i can see
Authentication failed for AuthFail Recv Req REGISTER
but are these not set in the config?
Cheers.

 

[James Dyke]

; Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings

 

[eddv123]

@James Dyke

Do the following (separately 1 for an inbound call/1 for an outbound call) login to the Patton via CLI and run the following commands below (starting with debug):

## SIP Commands ##

debug sip-signaling full-detail
debug sip-transport full-detail

## ISDN Commands ##

debug isdn-signaling full-detail
debug bri full-detail

##Call routing and call control##

debug cr full-detail
debug cc full-detail

Replicate the error for inbound call (then cut and paste onto a notepad file for analysis).
Replicate the error for an outbound call (and do the same).

no debug all to finish

Also ensure you firmware is up to date: https://www.patton.com/support/upgrades/index.asp?um=SmartNode 4131 3.16.0 is supported now.

PM them over to me.

 

[eddv123]

Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings

In that case it is you SIP credentials causing this problem.

If you really want to debug this you can use debug sip-registration full-detail but I think that the issue is pretty self-explanatory.

Check your gateway is not blacklisted in the IP blacklist as well.

 

[James Dyke]

Hi, it was blocked but i added to the allowed list.

 

[eddv123]

Hi, it was blocked but i added to the allowed list.

Has this solved your problem ?

 

[James Dyke]

Has this solved your problem ?

nope.

 

[eddv123]

If the device is not green/registered in 3CX under:
SIP Trunks >>> Gateway

Run the SIP registration debug commands and let the registration attempt be captured. If it is registered and it is just calls now then see the previous post regarding SIP/ISDN etc.

No point in doing the call debugging unless the registration has taken place.

 

[James Dyke]

ok, so i have inbound but, no out? [CM503014]: Call(C:52): No known route from Extn:109 to target: <sip:[email protected]:5060>

 

[eddv123]

Thats an easy one, most likely you do not have an outbound rule on the PBX pointing toward the Patton.
https://www.3cx.com/blog/voip-howto/outbound-rules-a-complete-example/

It needs to match the number you are dialling for example calls starting with 0 would suffice, personally I like to tighten up my outbound rules and make them more specific for security reasons.

 

[James Dyke]

ok, so i didn't set the 1st route "Make outbound calls on " what a plonker !!

thank you.