PSTN Gateway Authentication Failure v10 SP6

Status
Not open for further replies.

Discovery Technology

Joined
Apr 19, 2008
Messages
276
Reaction score
2
Hi All,

After attempting to connect a PATTON Smartnode 4960 gateway to our customers 3CX v10 install unsuccessfully due to failed authentication, I have isolated the issue to the 3CX Phone System & not the PATTON device. I have been able to replicate the failed auth issue even using the 3CX Windows Softphone to connect to the 3CX Phonesystem install.

The IP of the PATTON is 192.168.0.100/24 & the IP of the 3CX server is 192.168.0.200/24
User: 20001, Password; 20001

Test Results
- I can connect 3CX Soft phone to the PATTON device with user/pass 20001
- I cannot connect the 3CX Soft phone to the 3CX Phone System(customers) with user/pass 20001
- I cannot connect the PATTON SN 4960 device to the 3CX Phone System(customers) with user/pass 20001
- I can connect the PATTON SN 4960 device to another install of 3CX Phone System (test lab) with user/pass 20001
- I can connect the 3CX Soft phone device to another install of 3CX Phone System (test lab) with user/pass 20001

The above results, lead me to beleive the issue is with the customers 3CX install, TCP stack or something else on the network. When the customers 3CX PhoneSystem rejects the logon from 3CX Softphone or PATTON SN 4960 the logs appear as below:

Code:
14:50:08.794  [CM102001]: Authentication failed for SipReq:  REGISTER 192.168.1.200:5060 tid=ce7cc44a8667ee1a cseq=REGISTER [email protected]:57346 / 2 from(wire); Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings


The 3CX Phone System is running on a VM under VMWare. The 3CX Guest OS is Windows 2008 R2.

Has anyone seen something similiar before? I would like to avoid reloading 3CX Phone System at all cost.
 
Discovery Technology said:
I would like to avoid reloading 3CX Phone System at all cost.

Understandable, but, you might need to install the working config on the non-working machine to verify that it is (or is not) something in the settings of the non-working version.

Have you completely removed, then re-added the trunk settings in 3CX?

Have you tried adding a second trunk group (different trunks number) then resetting and reconfiguring the Patton with the new settings?
 
Status
Not open for further replies.

Latest Posts

Members Online Now

Forum statistics

Threads
111,852
Messages
589,387
Members
164,691
Latest member
Daz1964