3cx 7.1 and Linksys SPA400

[itfoundations.com]

Hello,
I have just upgraded from 3cx 7.0.45 to 7.1 and our SPA400 has stopped working for incoming calls. Outgoing calls still seem to work.
I have backed up and restored the original working configuration to the upgraded version and checked that all the settings are exactly as they were.

Both the 3cx box and the SPA400 have been rebooted and the upgrade has been tried a second time (the 3cx box is in VMWare so I've got a backup clone of the original box incase things didn't work) with the same results.

Has anyone else managed to get a SPA400 to work with 3cx version 7.1?
I can't see any errors in the system logs. Our VoIP gateway and the new Skype Gateway both work fine, just not the SPA400.
Anyone, know of any underlying changes which may have broken the connection to the SPA400 or any ideas how to troubleshoot what the problem is?

thanks for any help,
Dave

 

[bluetel2]

hello Dave, without log it s more difficult. you can't realy not send the log file ?

 

[discovery1]

Hi Dave

Can you please set the 3CX logs to verbose and then restart the 3CX services and replicate the problem - then post the details here?

 

[N_G]

The SPA400 is not suitable for use with 3CX v7.1 It was designed to be used with the Linksys SPA9000

I suggest you get a supported gateway such as the Grandstream GXW4104

 

[itfoundations.com]

Hi,
Where are the log files for 3cx? When I click on Server Activity Log within the managment consoleon 7.1 nothing happens (I have made it a trusted site).
Not sure if this points to a problem in itself?
I can't find the actual log files on the system either?

I do have a log from the SPA400 as an incoming call is being processed with version 7.1:

05-06-2009 10:16:08 Local7.Debug 192.168.254.240 0000174835 - SSMU_RVAUTH_SECRET could NOT Find regEntry
05-06-2009 10:16:08 Local7.Debug 192.168.254.240 0000174736 - Port = 11159
05-06-2009 10:16:08 Local7.Debug 192.168.254.240 0000174730 - SFU: Unexpected ASSIGNED_CALL_STATE when call leg state is 8, XMC_id=0 on tsg_id.port=0
05-06-2009 10:16:08 Local7.Debug 192.168.254.240 0000174730 - SFU: Unexpected ASSIGNED_CALL_STATE when call leg state is 8, XMC_id=0 on tsg_id.port=0
05-06-2009 10:16:05 Local7.Debug 192.168.254.240 0000173365 - SSMU_RVAUTH_SECRET could NOT Find regEntry
05-06-2009 10:16:05 Local7.Debug 192.168.254.240 0000173235 - Port = 11159
05-06-2009 10:16:05 Local7.Debug 192.168.254.240 0000173230 - SFU: Unexpected ASSIGNED_CALL_STATE when call leg state is 8, XMC_id=0 on tsg_id.port=0
05-06-2009 10:16:05 Local7.Debug 192.168.254.240 0000173230 - SFU: Unexpected ASSIGNED_CALL_STATE when call leg state is 8, XMC_id=0 on tsg_id.port=0
05-06-2009 10:16:02 Local7.Debug 192.168.254.240 0000171865 - SSMU_RVAUTH_SECRET could NOT Find regEntry
05-06-2009 10:16:02 Local7.Debug 192.168.254.240 0000171735 - Port = 11159
05-06-2009 10:16:02 Local7.Debug 192.168.254.240 0000171730 - SFU: Unexpected ASSIGNED_CALL_STATE when call leg state is 8, XMC_id=0 on tsg_id.port=0
05-06-2009 10:16:02 Local7.Debug 192.168.254.240 0000171730 - SFU: Unexpected ASSIGNED_CALL_STATE when call leg state is 8, XMC_id=0 on tsg_id.port=0
05-06-2009 10:15:59 Local7.Debug 192.168.254.240 0000170365 - SSMU_RVAUTH_SECRET could NOT Find regEntry
05-06-2009 10:15:59 Local7.Debug 192.168.254.240 0000170236 - Port = 11159
05-06-2009 10:15:59 Local7.Debug 192.168.254.240 0000170230 - SFU: Unexpected ASSIGNED_CALL_STATE when call leg state is 8, XMC_id=0 on tsg_id.port=0
05-06-2009 10:15:59 Local7.Debug 192.168.254.240 0000170230 - SFU: Unexpected ASSIGNED_CALL_STATE when call leg state is 8, XMC_id=0 on tsg_id.port=0
05-06-2009 10:15:56 Local7.Debug 192.168.254.240 0000168865 - SSMU_RVAUTH_SECRET could NOT Find regEntry
05-06-2009 10:15:56 Local7.Debug 192.168.254.240 0000168736 - Port = 11159
05-06-2009 10:15:56 Local7.Debug 192.168.254.240 0000168730 - SFU: Unexpected ASSIGNED_CALL_STATE when call leg state is 8, XMC_id=0 on tsg_id.port=0
05-06-2009 10:15:56 Local7.Debug 192.168.254.240 0000168730 - SFU: Unexpected ASSIGNED_CALL_STATE when call leg state is 8, XMC_id=0 on tsg_id.port=0
05-06-2009 10:15:53 Local7.Debug 192.168.254.240 0000167365 - SSMU_RVAUTH_SECRET could NOT Find regEntry
05-06-2009 10:15:53 Local7.Debug 192.168.254.240 0000167231 - Port = 11159
05-06-2009 10:15:49 Local7.Debug 192.168.254.240 0000165666 - UTIL: number=0772<#callers phone number removed here#>
05-06-2009 10:15:49 Local7.Debug 192.168.254.240 0000165666 - UTIL: param type=2
05-06-2009 10:15:49 Local7.Debug 192.168.254.240 0000165666 - UTIL: time=05061015<001>
05-06-2009 10:15:49 Local7.Debug 192.168.254.240 0000165665 - UTIL: param type=1
05-06-2009 10:15:49 Local7.Debug 192.168.254.240 0000165665 - UTIL: got raw msg = <001><008>05061015<002><011>0772<#callers phone number removed here#>, length=23
05-06-2009 10:15:49 Local7.Debug 192.168.254.240 0000165665 - UTIL: Going to parse MDMF type CID info

And this is the working equvalent when using 3cx 7.0:

05-06-2009 10:40:18 Local7.Debug 192.168.254.240 0000899836 - SPU 0: has voice since last report, reset g_FxoSilenceDetCnt[0]=304, curr time=1241606418
05-06-2009 10:39:27 Local7.Debug 192.168.254.240 0000874526 - SPU 0: no voice since last report, g_FxoSilenceDetCnt[0]=208, curr time=1241606367
05-06-2009 10:39:19 Local7.Debug 192.168.254.240 0000870672 - *** ERROR -- DOES not INCLUDE CNUM
05-06-2009 10:39:19 Local7.Debug 192.168.254.240 0000870672 - Port = 11159
05-06-2009 10:39:11 Local7.Debug 192.168.254.240 0000866526 - SPU 0: no voice since last report, g_FxoSilenceDetCnt[0]=224, curr time=1241606351
05-06-2009 10:39:00 Local7.Debug 192.168.254.240 0000860852 - *** ERROR -- DOES not INCLUDE CNUM
05-06-2009 10:39:00 Local7.Debug 192.168.254.240 0000860847 - Port = 11159
05-06-2009 10:38:55 Local7.Debug 192.168.254.240 0000858526 - SPU 0: no voice since last report, g_FxoSilenceDetCnt[0]=240, curr time=1241606335

thanks,
Dave

 

[itfoundations.com]

Hi,
I found the 3cx logs (c:\Documents and settings\All users\applications\3cx\logs):
And i think I found the problem although I can't see where to fix it:

10:23:27.336|.\Authorization.cpp(103)|Critical0|Authorization|AuthMgr:nAuthFailure:[CM102001]: Authentication failed for SipReq: INVITE [email protected] tid=-4a01651f-ec112b33-53c4a02a cseq=INVITE [email protected]:5060 / 2 from(wire); Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings<br>
10:23:27.946|.\Extension.cpp(352)|Log2||ExtnCfg::updateContact:[CM504001]: Ext.200: new contact is registered. Contact(s): [sip:[email protected]:5060/200]<br>
10:23:30.118|.\Authorization.cpp(363)|Error1||evt::CheckIfAuthIsRequired::not_handled:[CM302001]: Authorization system can not identify source of: SipReq: INVITE [email protected] tid=-4a016522-ec113619-18fa90f7 cseq=INVITE [email protected]:5060 / 1 from(wire)<br>
10:23:30.118|.\Authorization.cpp(367)|Log2||evt::CheckIfAuthIsRequired::not_handled:[CM500002]: Unidentified incoming call. Review INVITE and adjust source identification:
INVITE sip:[email protected] SIP/2.0
Via: SIP/2.0/UDP 192.168.254.240:5060;branch=z9hG4bK-4a016522-ec113619-18fa90f7
Max-Forwards: 70
Contact: <sip:[email protected]:5060;transport=UDP>
To: <sip:[email protected]>
From: "No Name - 10301 - 10301 - 10301 - 10301 - 10301 -"<sip:0772<#phone number removed#>@192.168.254.240>;tag=f0fea8c0-13c4-4a016522-ec113619-3ee494f6
Call-ID: 10195e24-f0fea8c0-13c4-4a016522-ec113619-266f0bb8@192.168.254.240
CSeq: 1 INVITE
Supported: replaces, timer, 100rel
Content-Length: 0

The authentication failed when an incoming call tries to connect to the internal DID 10301 on 3cx. I currently have the DID set up in a port called 10001 with the Authentication ID matching the User ID set up on the SPA400 and the Authentication password is blank. There doesn't look like there is anywhere this can be set on the SPA400?

thanks,
Dave

 

[itfoundations.com]

Hi,
I've tried resetting the user ID on the SPA400 and making sure the password is blank on the 3cx gateway settings (as there isn't anywhere to set a password on SPA400).
I can't see anything else to try?

Also, although I can see the log files when I open them direct and they seem to be working, clicking on 'System Logs' on the console still doesn't work. Has anyone else experienced this?

thanks,
Dave

 

[discovery1]

If you can't see the 3CX logs from the management console then you have problems somewhere that need to be fixed to rule them out as being the cause of your current problems.

 

[itfoundations.com]

I've done a clean reinstall (without restoring the previous settings) and the log files are now working.

I reconfigured 3cx for the SPA400 pbx from scratch and it still doensn't work for incoming calls it still says:

Authentication failed for SipReq: INVITE [email protected] tid=-4a044912-f75b9803-5f35b430 cseq=INVITE [email protected]:5060 / 2 from(wire); Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings<br>

But the usernames match and the password is left blank on 3cx gateway (the SPA400 has no password). I can only think that some underlying change has been made to 3cx which no longer likes the blank password.

I'l have to switch back to the old version for just now.

Dave

 

[Discovery Technology]

Have you tried it with a password, just out of curiosity?

ie: password on SPA400 and 3CX extension.

 

[fricci]

We are having the exact same problem.....we have a lot of these boxes and would like to use them with 3CX. Please post your progress...

Thanks.

 

[fricci]

Got it working......

including disconnection tones....

 

[discovery1]

Can you post your method to get it working so everyone can see?

 

[eafxent]

In case you are still looking for the solution it is actually pretty simple (once you find it )

Under PSTN devices click on your Gateway to edit the Gateway's settings.

Once in the settings go to the Inbound Parameters tab.
In the "call source Identification" section (top part).
Select Contact: Host Part as the SIP Field
Custom Field under variable
and in the Custom Value box enter the ip and pot of your gateway. From the configuration file it appears that it is: 192.168.254.240:5060

Once I did this not only did I get incoming calls to work but shortly afterwards the server activity log would also start "working" or should I say appearing in the configuration application.

Hope this helps.