Apologies Anthony... This is the printout from sofia. 2000 does not work sending custom NOTIFY messages and 2001 does. Is it that 2001 is NAT'd, the port 10281 out of range or the contact incorrect or something? Thanks! Call-ID: a7c8c53f-c18596ef@192.168.1.3 User: 2001@192.168.1.120 Contact: 2001 <sip:2001@124.yyy.yyy.yyy:5072;transport=tls> Agent: Linksys/SPA3102-5.1.10(GW) Status: Registered(TLS)(unknown) EXP(2010-01-28 12:54:31) Host: freeswitch IP: 124.yyy.yyy.yyy Port: 5072 Auth-User: 2001 Auth-Realm: mydns.dyndns.org MWI-Account: 2001@192.168.1.120 Call-ID: 2ff39277-fd9a6ab1@10.0.0.1 User: 2000@192.168.1.120 Contact: 2000 <sip:2000@124.xxx.xxx.xxx:5075;transport=tls;fs_nat=yes;fs_path=sip%3A2000%40124.xxx.xxx.xxx%3A10281%3Btransport%3Dtls> Agent: Linksys/SPA3102-5.1.10(GW) Status: Registered(TLS-NAT)(unknown) EXP(2010-01-28 00:29:34) Host: freeswitch IP: 124.xxx.xxx.xxx Port: 10281 Auth-User: 2000 Auth-Realm: mydns.dyndns.org MWI-Account: 2000@192.168.1.120 On Thu, Jan 28, 2010 at 2:25 PM, Anthony Minessale <anthony.minessale@gmail.com> wrote:
you said one was the word freeswitch and one was an ip didn't you?
On Wed, Jan 27, 2010 at 8:34 PM, Mark Campbell-Smith <mcampbellsmith@gmail.com> wrote:
If it works with 2001 doesn't that mean I am using the correct host?
Both 2001 and 2000 register with exactly the same data, except username and password ....
On Thu, Jan 28, 2010 at 12:41 PM, Anthony Minessale <anthony.minessale@gmail.com> wrote:
the host is not resolved it has to be an exact string match with the host that is in the db. if you want to normalize it set force-reg-domain and force-reg-db-domain to the same val
On Wed, Jan 27, 2010 at 7:26 PM, Mark Campbell-Smith <mcampbellsmith@gmail.com> wrote:
Thanks Anthony,
I think user matches (ie the extension 2000 or 2001). What should host be? In the sofia printout, it says 'freeswitch' (freeswitch has ip address 192.168.1.120).
However, if I try to use 'freeswitch' as the host for user 2001, nothing is sent. But using 192.168.1.120 does.
If I do exactly the same thing for 2000, the NOTIFY message is not sent. Are there logs I can send to show you or any ideas what I am doing wrong?
On Thu, Jan 28, 2010 at 12:09 PM, Anthony Minessale <anthony.minessale@gmail.com> wrote:
user and host have to match too
On Wed, Jan 27, 2010 at 7:06 AM, Mark Campbell-Smith <mcampbellsmith@gmail.com> wrote:
Thanks guys. I have this working except for one user who is registered like this:
Call-ID: 2ff39277-fd9a6ab1@10.0.0.1 User: 2000@192.168.1.120 Contact: 2000
<sip:2000@124.xxx.xxx.xxx:5075;transport=tls;fs_nat=yes;fs_path=sip%3A2000%40124.xxx.xxx.xxx%3A10281%3Btransport%3Dtls> Agent: Linksys/SPA3102-5.1.10(GW) Status: Registered(TLS-NAT)(unknown) EXP(2010-01-28 00:29:34) Host: freeswitch IP: 124.xxx.xxx.xxx Port: 10281 Auth-User: 2000 Auth-Realm: mydns.dyndns.org MWI-Account: 2000@192.168.1.120
When I do the following commands via the telnet socket, no notify command is sent to user 2000:
sendevent NOTIFY profile: internal content-type: application/simple-message-summary event-string: reboot_now user: 2000 host: 192.168.1.120 content-length: 0
However, if I do exactly the same thing with user 2001 it works. 2001 is registered as:
Contact: 2001 <sip:2001@124.yyy.yyy.yyy:5066;transport=tls>
Any ideas why that would be?
On Mon, Jan 25, 2010 at 11:50 AM, Ognjen Seslija <oseslija@gmail.com> wrote: > The phone is asking FS to authenticate prior then accepting a > NOTIFY > from > it. > The authentication of notify's from spa endpoints work (afaik) > only > with > Linksys SPA9000 PBX , and FS doesn't have the code for that for > obvious > reasons. > If you have SPA9000 maybe you can collect SIP traces. > > Ognjen > > > > > > On Mon, Jan 25, 2010 at 1:29 AM, Mark Campbell-Smith > <mcampbellsmith@gmail.com> wrote: >> >> Hi Ognjen, >> >> Thanks for the tip on the resync under the EXT tab. It now works >> using mod_event_socket and the following: >> >> sendevent NOTIFY >> profile: internal >> event-string: resync >> user: 1000 >> host: 192.168.1.121 >> content-type: application/simple-message-summary >> >> However, if AUTH is required, why does FS send the wrong >> information >> to >> the SPA? >> >> On Mon, Jan 25, 2010 at 11:15 AM, Ognjen Seslija >> <oseslija@gmail.com> >> wrote: >> > You should not authenticate those NOTIFYs (this will work only >> > with >> > SPA9000 >> > afaik). The option to change for this is in EXT tabs: >> > >> > Auth Resync-Reboot: No >> > >> > Also, FSs code will do a reboot of a phone, not resync (it >> > sends >> > reboot_now >> > event). For that to work a patch is required. >> > >> > I've just tried to reboot my 942 (rev 16506) and it definitely >> > works. >> > >> > Regards, >> > Ognjen >> > >> > >> > On Mon, Jan 25, 2010 at 12:58 AM, Mark Campbell-Smith >> > <mcampbellsmith@gmail.com> wrote: >> >> >> >> Thanks Brian.. this still does not work. Maybe I need to open >> >> a >> >> Jira? >> >> Notice the username in the authorization field. It should be >> >> 1000. >> >> >> >> Cheers >> >> Mark >> >> >> >> freeswitch@internal> sofia status profile internal user >> >> 1000@192.168.1.120 >> >> >> >> Registrations: >> >> >> >> >> >> >> >> >> >> >> >> ================================================================================================= >> >> Call-ID: bd783b73-66877627@192.168.1.121 >> >> User: 1000@192.168.1.120 >> >> Contact: 1000 <sip:1000@192.168.1.121:5060> >> >> Agent: Linksys/PAP2T-5.1.6(LS) >> >> Status: Registered(UDP)(unknown) EXP(2010-01-25 >> >> 11:25:05) >> >> Host: freeswitch >> >> IP: 192.168.1.121 >> >> Port: 5060 >> >> Auth-User: 1000 >> >> Auth-Realm: 192.168.1.120 >> >> MWI-Account: 1000@192.168.1.120 >> >> >> >> >> >> >> >> >> >> >> >> >> >> ================================================================================================= >> >> >> >> freeswitch@internal> sofia profile internal flush_inbound_reg >> >> bd783b73-66877627@192.168.1.121 reboot >> >> +OK rebooting all registrations matching specified call_id >> >> >> >> freeswitch@internal> send 804 bytes to >> >> udp/[192.168.1.121]:5060 >> >> at >> >> 23:55:49.012627: >> >> >> >> >> >> >> >> >> >> ------------------------------------------------------------------------ >> >> NOTIFY sip:1000@192.168.1.121:5060 SIP/2.0 >> >> Via: SIP/2.0/UDP >> >> 192.168.1.120;rport;branch=z9hG4bK1DKgFmj8QDp4g >> >> Max-Forwards: 70 >> >> From: <sip:1000@192.168.1.120>;tag=Z440t7e61ND0g >> >> To: <sip:1000@192.168.1.120> >> >> Call-ID: d65f2a5a-83e6-122d-7ba9-00e04c0312e9 >> >> CSeq: 126070338 NOTIFY >> >> Contact: <sip:mod_sofia@192.168.1.120:5060> >> >> User-Agent: FreeSWITCH-mod_sofia/1.0.trunk-16256 >> >> Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, UPDATE, >> >> INFO, >> >> REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE >> >> Supported: timer, precondition, path, replaces >> >> Event: reboot_now >> >> Allow-Events: talk, presence, dialog, line-seize, call-info, >> >> sla, >> >> include-session-description, presence.winfo, message-summary, >> >> refer >> >> Subscription-State: terminated;reason=timeout >> >> Content-Type: application/simple-message-summary >> >> Content-Length: 0 >> >> >> >> >> >> >> >> >> >> >> >> ------------------------------------------------------------------------ >> >> recv 407 bytes from udp/[192.168.1.121]:5060 at >> >> 23:55:49.045267: >> >> >> >> >> >> >> >> >> >> ------------------------------------------------------------------------ >> >> SIP/2.0 401 Unauthorized >> >> To: <sip:1000@192.168.1.120>;tag=3300b5853719f35di0 >> >> From: <sip:1000@192.168.1.120>;tag=Z440t7e61ND0g >> >> Call-ID: d65f2a5a-83e6-122d-7ba9-00e04c0312e9 >> >> CSeq: 126070338 NOTIFY >> >> Via: SIP/2.0/UDP 192.168.1.120;branch=z9hG4bK1DKgFmj8QDp4g >> >> Server: Linksys/PAP2T-5.1.6(LS) >> >> WWW-Authenticate: Digest realm="192.168.1.120", >> >> nonce="8e54805b", >> >> qop="auth", algorithm=md5 >> >> Content-Length: 0 >> >> >> >> >> >> >> >> >> >> >> >> ------------------------------------------------------------------------ >> >> send 1056 bytes to udp/[192.168.1.121]:5060 at >> >> 23:55:49.060073: >> >> >> >> >> >> >> >> >> >> ------------------------------------------------------------------------ >> >> NOTIFY sip:1000@192.168.1.121:5060 SIP/2.0 >> >> Via: SIP/2.0/UDP >> >> 192.168.1.120;rport;branch=z9hG4bK2pc9gF3BNpcQc >> >> Max-Forwards: 70 >> >> From: <sip:1000@192.168.1.120>;tag=Z440t7e61ND0g >> >> To: <sip:1000@192.168.1.120> >> >> Call-ID: d65f2a5a-83e6-122d-7ba9-00e04c0312e9 >> >> CSeq: 126070339 NOTIFY >> >> Contact: <sip:mod_sofia@192.168.1.120:5060> >> >> Expires: 3590 >> >> User-Agent: FreeSWITCH-mod_sofia/1.0.trunk-16256 >> >> Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, UPDATE, >> >> INFO, >> >> REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE >> >> Supported: timer, precondition, path, replaces >> >> Event: reboot_now >> >> Allow-Events: talk, presence, dialog, line-seize, call-info, >> >> sla, >> >> include-session-description, presence.winfo, message-summary, >> >> refer >> >> Subscription-State: terminated;reason=timeout >> >> Authorization: Digest username="1115633124", >> >> realm="192.168.1.120", >> >> nonce="8e54805b", cnonce="1mWxHoPmEi2pewDgTAMS6Q", >> >> algorithm=MD5, >> >> uri="sip:1000@192.168.1.121:5060", >> >> response="747b4d04544c84535dbbd987f2999ca7", qop=auth, >> >> nc=00000001 >> >> Content-Type: application/simple-message-summary >> >> Content-Length: 0 >> >> >> >> >> >> >> >> >> >> >> >> ------------------------------------------------------------------------ >> >> recv 407 bytes from udp/[192.168.1.121]:5060 at >> >> 23:55:49.086375: >> >> >> >> >> >> >> >> >> >> ------------------------------------------------------------------------ >> >> SIP/2.0 401 Unauthorized >> >> To: <sip:1000@192.168.1.120>;tag=3300b5853719f35di0 >> >> From: <sip:1000@192.168.1.120>;tag=Z440t7e61ND0g >> >> Call-ID: d65f2a5a-83e6-122d-7ba9-00e04c0312e9 >> >> CSeq: 126070339 NOTIFY >> >> Via: SIP/2.0/UDP 192.168.1.120;branch=z9hG4bK2pc9gF3BNpcQc >> >> Server: Linksys/PAP2T-5.1.6(LS) >> >> WWW-Authenticate: Digest realm="192.168.1.120", >> >> nonce="5339c7ba", >> >> qop="auth", algorithm=md5 >> >> Content-Length: 0 >> >> >> >> >> >> >> >> >> >> >> >> ------------------------------------------------------------------------ >> >> >> >> On Mon, Jan 25, 2010 at 4:46 AM, Brian West >> >> <brian@freeswitch.org> >> >> wrote: >> >> > or sofia profile xxx flush_inbound_reg callid reboot >> >> > callid you can get from sofia status profile xxx >> >> > /b >> >> > On Jan 24, 2010, at 5:28 AM, Mark Campbell-Smith wrote: >> >> > >> >> > Actually I just >> >> > found http://wiki.freeswitch.org/wiki/Mod_event_socket >> >> > >> >> > If I telnet to FS as described >> >> > >> >> > http://wiki.freeswitch.org/wiki/Mod_event_socket#Telnet_Client, >> >> > do >> >> > I >> >> > just need to enter somthing like: >> >> > >> >> > sendevent NOTIFY >> >> > profile: internal >> >> > event-string: resync >> >> > user: 1000 >> >> > host: 192.168.1.121 >> >> > content-type: application/simple-message-summary >> >> > >> >> > where 192.168.1.121 is the ip address of one of the Linksys >> >> > devices? >> >> > >> >> > I don't see any messages sent when I do this. What am I >> >> > doing >> >> > wrong? >> >> > >> >> > Thanks >> >> > >> >> > >> >> > _______________________________________________ >> >> > 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 >> >> > >> >> > >> >> >> >> _______________________________________________ >> >> 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 >> > >> > >> > _______________________________________________ >> > 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 >> > >> > >> >> _______________________________________________ >> 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 > > > _______________________________________________ > 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 > >
_______________________________________________ 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
-- Anthony Minessale II
FreeSWITCH http://www.freeswitch.org/ ClueCon http://www.cluecon.com/ Twitter: http://twitter.com/FreeSWITCH_wire
AIM: anthm MSN:anthony_minessale@hotmail.com GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com IRC: irc.freenode.net #freeswitch
FreeSWITCH Developer Conference sip:888@conference.freeswitch.org iax:guest@conference.freeswitch.org/888 googletalk:conf+888@conference.freeswitch.org pstn:+19193869900
_______________________________________________ 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
_______________________________________________ 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
-- Anthony Minessale II
FreeSWITCH http://www.freeswitch.org/ ClueCon http://www.cluecon.com/ Twitter: http://twitter.com/FreeSWITCH_wire
AIM: anthm MSN:anthony_minessale@hotmail.com GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com IRC: irc.freenode.net #freeswitch
FreeSWITCH Developer Conference sip:888@conference.freeswitch.org iax:guest@conference.freeswitch.org/888 googletalk:conf+888@conference.freeswitch.org pstn:+19193869900
_______________________________________________ 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
_______________________________________________ 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
-- Anthony Minessale II
FreeSWITCH http://www.freeswitch.org/ ClueCon http://www.cluecon.com/ Twitter: http://twitter.com/FreeSWITCH_wire
AIM: anthm MSN:anthony_minessale@hotmail.com GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com IRC: irc.freenode.net #freeswitch
FreeSWITCH Developer Conference sip:888@conference.freeswitch.org iax:guest@conference.freeswitch.org/888 googletalk:conf+888@conference.freeswitch.org pstn:+19193869900
_______________________________________________ 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