I'm using sipsak to send messages to Snoms in my subnet. At work, works fine: sipsak -M -O desktop -B "foo" -s sip:1001@192.168.1.220 -H 192.168.1.46 displays "foo" on the Snom display On my home LAN (AAH 1.5, Snom 190 3.60s, switched 100, no VLAN, no routing) the same command (modified for my LAN) always yields: (type: 3, code: 3): from 192.168.171.8 at the console of the sending machine. Same if I use FQDN. Type 3 Code 3 means "ICMP port unreachable" Doing a PCAP from the phone indicates that the Snom gets the message, but nothing shows up in the SIP log. Doing tcpdump on the originating machine yields something like "Reply from 192.168.171.8 > 192.168.171.10 UDP port 5060 unreachable" Same phones, same firmware rev, same version of sipsak, no IPTABLES on the originating machine, DNS lookups work, call behavior is normal, other SIP behavior like MWI works fine. I got nuthin here, anyone got a tip?
snom phones by default do not accept SIP messages from other destinations that the registrar (in this case they send a error response) and they dont listen on port 5060 by default. Reason: SECURITY!!! If you want to lower your security, you can manually specify the SIP port to 5060 and manually disable the filering from the proxy/registrar. But then dont complain if people make a fun out of themselves by making your phone ring with funny SIPSAK requests!!! I think the best practice on this is to send the requests to the proxy which then will forward the packets depending on the proxy's security policy. Replace proxy with Asterisk! Christian> -----Original Message----- > From: asterisk-users-bounces@lists.digium.com > [mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of > Colin Anderson > Sent: Friday, September 30, 2005 4:31 PM > To: 'Asterisk Users Mailing List - Non-Commercial Discussion' > Subject: RE: [Asterisk-Users] OT: SIPSAK usage > > I'm using sipsak to send messages to Snoms in my subnet. At > work, works > fine: > > sipsak -M -O desktop -B "foo" -s sip:1001@192.168.1.220 -H > 192.168.1.46 > > displays "foo" on the Snom display > > On my home LAN (AAH 1.5, Snom 190 3.60s, switched 100, no > VLAN, no routing) the same command (modified for my LAN) > always yields: > > (type: 3, code: 3): from 192.168.171.8 > > at the console of the sending machine. Same if I use FQDN. > Type 3 Code 3 means "ICMP port unreachable" > > Doing a PCAP from the phone indicates that the Snom gets the > message, but nothing shows up in the SIP log. Doing tcpdump > on the originating machine yields something like "Reply from > 192.168.171.8 > 192.168.171.10 UDP port 5060 unreachable" > > Same phones, same firmware rev, same version of sipsak, no > IPTABLES on the originating machine, DNS lookups work, call > behavior is normal, other SIP behavior like MWI works fine. I > got nuthin here, anyone got a tip? > _______________________________________________ > --Bandwidth and Colocation sponsored by Easynews.com -- > > Asterisk-Users mailing list > Asterisk-Users@lists.digium.com > http://lists.digium.com/mailman/listinfo/asterisk-users > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users > > >
Thanks for the reply. I am using the -H option to specify the IP address of the registrar, so no problem there. It would seem then that my port 5060 has to be explicitly set, which I *think* is under Advanced > Advanced Network > Network identity (port): - the default setting is blank. Would adding 5060 here cause this to work? Not worried about security here since 100% of my users are boneheads and still think we are using our Meridian with Centrex and that the Snom is just a fancy Meridian phone. SIP and VoIP in general is completely lost on them. -----Original Message----- From: Christian Stredicke [mailto:Christian.Stredicke@snom.de] Sent: Friday, September 30, 2005 9:50 AM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: RE: [Asterisk-Users] OT: SIPSAK usage snom phones by default do not accept SIP messages from other destinations that the registrar (in this case they send a error response) and they dont listen on port 5060 by default. Reason: SECURITY!!! If you want to lower your security, you can manually specify the SIP port to 5060 and manually disable the filering from the proxy/registrar. But then dont complain if people make a fun out of themselves by making your phone ring with funny SIPSAK requests!!! I think the best practice on this is to send the requests to the proxy which then will forward the packets depending on the proxy's security policy. Replace proxy with Asterisk! Christian> -----Original Message----- > From: asterisk-users-bounces@lists.digium.com > [mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of > Colin Anderson > Sent: Friday, September 30, 2005 4:31 PM > To: 'Asterisk Users Mailing List - Non-Commercial Discussion' > Subject: RE: [Asterisk-Users] OT: SIPSAK usage > > I'm using sipsak to send messages to Snoms in my subnet. At > work, works > fine: > > sipsak -M -O desktop -B "foo" -s sip:1001@192.168.1.220 -H > 192.168.1.46 > > displays "foo" on the Snom display > > On my home LAN (AAH 1.5, Snom 190 3.60s, switched 100, no > VLAN, no routing) the same command (modified for my LAN) > always yields: > > (type: 3, code: 3): from 192.168.171.8 > > at the console of the sending machine. Same if I use FQDN. > Type 3 Code 3 means "ICMP port unreachable" > > Doing a PCAP from the phone indicates that the Snom gets the > message, but nothing shows up in the SIP log. Doing tcpdump > on the originating machine yields something like "Reply from > 192.168.171.8 > 192.168.171.10 UDP port 5060 unreachable" > > Same phones, same firmware rev, same version of sipsak, no > IPTABLES on the originating machine, DNS lookups work, call > behavior is normal, other SIP behavior like MWI works fine. I > got nuthin here, anyone got a tip? > _______________________________________________ > --Bandwidth and Colocation sponsored by Easynews.com -- > > Asterisk-Users mailing list > Asterisk-Users@lists.digium.com > http://lists.digium.com/mailman/listinfo/asterisk-users > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users > > >_______________________________________________ --Bandwidth and Colocation sponsored by Easynews.com -- Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Possibly Parallel Threads
- OT: Snom 320, displaying text on the scree n from *
- SipSak: error: this FQDN or IP is not valid: voicegw
- SipSak: Send SIP OPTION with password
- OT: Using Sipsak to reboot a Snom phone < -a nswered my own question
- sipsak 200 for a user, but 404 for a different user...why?