V20 w/Patton SN4141FXO configuration not working

[PatM]

Have a new instance of V20 on a local machine and a Patton SN4141FXO. 3 POTS lines coming in and 3CX all setup. The problem is with getting the SN4141 working and registered properly. Have followed the few recommendations of setting up the 4141 as a new Generic Gateway which the manual references the old GUI of the Patton SN. Have tried using the Patton web wizard, but get constant Password encryption failures. Have gotten the unit to actually register, but have then had 0 luck with actually making or receiving calls. I have used 5 different browsers and 2 computers and nothing will generate a config file that doesn't come back with the password authentication failure.

If I look in the Patton error logs, I get this for any inbound calls " 2025 Jun 23 18:28:29 SIP-SIG # [EP IF_SIP-0xa73b1a00 SES 0xb02f2000] NO AUTHENTICATION CREDENTIALS FOUND. User: sip:[email protected]:5060, realm: 3CXPhoneSystem


For outbound calls I get nothing in the Patton for errors as it never reaches it, but looking at the 3CX call log, it shows the following, which I can say is false on the answers side as my mobile never rang and I most certainly never terminated the call.



Have reached out to Patton and have gotten no responses from them. Have contacted my distributor for Patton and they tell me that the config file is setup properly, but this most certainly is not working. Anyone have any insightful ideas to get this working. Way too much time staring at a computer screen and trying different things to get no further than I was when I first installed this.

Pat

 

[PatM]

Well thanks to Patton and a lot of back and forth, was able to finally get this resolved. So a couple of things were going on. Re-invites from the server were not responding, so had to enter in some scripting in order to resolve that issue.

enable
configure
location-service LOC_SVC
identity-group DEFAULT
authentication outbound
authenticate authentication-service AUTH_SVC username 10000
write

But after that issue was resolved and we were able to receive Inbound calls, had to figure out why the lines were scratchy, but also no Outbound calls were being routed. So some more scripts needed to be entered.

enable
configure
system pcm law-select ulaw
profile fxo DEFAULT
electrical-standard us
caller-id standard fsk-bell
disconnect-signal busy-tone
no disconnect-signal loop-break
write

So after all the back and forth and now a functional system, we can finally move on to the next one. Hopefully this helps someone at the end of the day!