Re: [Freeswitch-users] Can't register with Linksys SPA 3000
On Sunday 29 June 2008 17:44:29 Михаил Кривушин wrote:
В сообщении от 29 июня 2008 вы написали: HO> On Sunday 29 June 2008 15:38:25 Михаил Кривушин wrote: HO> > Are you try to read log file? Can you post lines with error? HO> HO> HO> Many lines of this message: HO> HO> 2008-06-29 17:14:28 [DEBUG] sofia.c:190 sofia_event_callback() event HO> [nua_r_options] status [405][Method Not Allowed] session: n/a HO> 2008-06-29 17:14:59 [DEBUG] sofia.c:190 sofia_event_callback() event HO> [nua_r_options] status [405][Method Not Allowed] session: n/a HO> 2008-06-29 17:15:29 [DEBUG] sofia.c:190 sofia_event_callback() event HO> [nua_r_options] status [405][Method Not Allowed] session: n/a HO> 2008-06-29 17:15:59 [DEBUG] sofia.c:190 sofia_event_callback() event HO> [nua_r_options] status [405][Method Not Allowed] session: n/a
I found that the messages above are caused by SJPhone (which works perfectly with FS) and not by Linksys.
I think <param name="disable-register" value="true"/> in one of your profiles does not allow registration (I see such message when set this param). May be Linksys try to connect to other than 5060 port?
The port I specified is 5060.
On Jun 29, 2008, at 12:08 PM, Henk Oegema wrote:
On Sunday 29 June 2008 17:44:29 Михаил Кривушин wrote:
В сообщении от 29 июня 2008 вы написали: HO> On Sunday 29 June 2008 15:38:25 Михаил Кривушин wrote: HO> > Are you try to read log file? Can you post lines with error? HO> HO> HO> Many lines of this message: HO> HO> 2008-06-29 17:14:28 [DEBUG] sofia.c:190 sofia_event_callback() event HO> [nua_r_options] status [405][Method Not Allowed] session: n/a HO> 2008-06-29 17:14:59 [DEBUG] sofia.c:190 sofia_event_callback() event HO> [nua_r_options] status [405][Method Not Allowed] session: n/a HO> 2008-06-29 17:15:29 [DEBUG] sofia.c:190 sofia_event_callback() event HO> [nua_r_options] status [405][Method Not Allowed] session: n/a HO> 2008-06-29 17:15:59 [DEBUG] sofia.c:190 sofia_event_callback() event HO> [nua_r_options] status [405][Method Not Allowed] session: n/a
I found that the messages above are caused by SJPhone (which works perfectly with FS) and not by Linksys.
We send message-summary to the phone when its registered, perhaps your phone does not support mwi? Mike
On Sunday 29 June 2008 18:42:12 Michael Jerris wrote:
We send message-summary to the phone when its registered, perhaps your phone does not support mwi?
Well, SJPhone does support mwi. Anyhow, it has nothing to do with the fact that Linksys SPA 3000 won't register. I still haven't found out why. :-(
Can you show me the output of "sofia status"? /b On Jun 29, 2008, at 1:22 PM, Henk Oegema wrote:
On Sunday 29 June 2008 18:42:12 Michael Jerris wrote:
We send message-summary to the phone when its registered, perhaps your phone does not support mwi?
Well, SJPhone does support mwi.
Anyhow, it has nothing to do with the fact that Linksys SPA 3000 won't register.
I still haven't found out why. :-(
_______________________________________________ Freeswitch-users mailing list Freeswitch-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
On Sunday 29 June 2008 20:26:53 Brian West wrote:
Can you show me the output of "sofia status"?
freeswitch@ubuntu> sofia status API CALL [sofia(status)] output: Name Type Data State ================================================================================================= internal profile sip:mod_sofia@192.168.1.101:5060 RUNNING (0) external profile sip:mod_sofia@78.21.64.194:5080 RUNNING (0) voipbuster.com gateway sip:henkoegema@voipbuster.com REGED nat profile sip:mod_sofia@78.21.64.194:5070 RUNNING (0) default alias internal ALIASED 192.168.1.101 alias internal ALIASED outbound alias external ALIASED ================================================================================================= 3 profiles 3 aliases freeswitch@ubuntu> sofia status profile default API CALL [sofia(status profile default)] output: ================================================================================================= Name default Domain Name 192.168.1.101 Alias Of internal DBName sofia_reg_internal Dialplan XML RTP-IP 192.168.1.101 SIP-IP 192.168.1.101 URL sip:mod_sofia@192.168.1.101:5060 BIND-URL sip:mod_sofia@192.168.1.101:5060 HOLD-MUSIC local_stream://moh CODECS G722,PCMU,PCMA,GSM TEL-EVENT 101 CNG 13 SESSION-TO 0 MAX-DIALOG 0 Registrations: ================================================================================================= Call-ID EC3EFF8D-5967-43D7-A7A3-0F22D2A76CB3@192.168.1.102 User 1001@192.168.1.101 Contact "user" <sip:1001@192.168.1.102:5060>;nat Agent SJphone/1.61.321a (SJ Labs) Status Registered(AUTO-NAT)(unknown) EXP(2008-06-29 21:15:17) ================================================================================================= freeswitch@ubuntu>
I ran into this once before and I had to do a factory reset on the SPA to make it work correctly. Have you tried that? Everything looks fine in this output otherwise. /b On Jun 29, 2008, at 2:16 PM, Henk Oegema wrote:
On Sunday 29 June 2008 20:26:53 Brian West wrote:
Can you show me the output of "sofia status"?
On Sunday 29 June 2008 21:21:08 Brian West wrote:
I ran into this once before and I had to do a factory reset on the SPA to make it work correctly. Have you tried that? Everything looks fine in this output otherwise.
There are no problems with registering softphones. It's only Linksys that won't register (but it registers ok with Asterisk) I'll try a factory reset and will let you know the outcome. Henk
On Sunday 29 June 2008 21:21:08 Brian West wrote:
I ran into this once before and I had to do a factory reset on the SPA to make it work correctly. Have you tried that? Everything looks fine in this output otherwise.
Thanks everybody for taking time to help me. I finally found the solution to my problem. :-) I was logged into the Linksys in admin mode (basic) In basic mode I could change the proxy address, but the outbound proxy address was not visable, and was still on the old address. When I changed to advanced mode, I could see the outbound proxy address. So after changing that, I could register at once.
participants (3)
-
Brian West
-
Henk Oegema
-
Michael Jerris