similar to: OT: Using Sipsak to reboot a Snom phone

Forgot on the Snom 200 it won't reboot if under the Memory tab in the web interface, Connections > 0 then remote reboot is not possible. Manually cycling the power allows the phone to be rebooted by Sipsak remotely. HOWTO: Reboot a Snom with Sipsak Checklist: 1. Under Advanced in the web interface, is Network Identity set to 5060? 2. Under Advanced in the web interface, is Challenge for

try "sipsak -M -O desktop -B "foo" -s sip:<user>@<registrar> -H <ip of registrar>" the trick is to specify the "-O desktop" parameter + the "-H <ip of registrar>" parameter. Sipsak fakes the host-header of the registrar so that the Snom thinks it is coming from your Asterisk server, then lets the message through to the

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

Hi, I **think** that I have user of thufir101, because I get a 200 response below, but I also get a 404. It seems to depend on how I send the ip address/fqdn? tleilax*CLI> tleilax*CLI> sip show users Username Secret Accountcode Def.Context ACL Forcerport 201 password 201 default No Yes

The snom 200 and 220 have five programmable buttons. Each button has a led that can be used to indecate if an extension is idle, in use, or ringing. A button pannel for the 220 is also comming out soon that will have 20'ish programmable buttons on board. This is a killer app for any company that has receptionists handle calls, and pretty usefull for everyone else. As a matter of fact,

Hello, I'm trying to use SipSak to check if my Asterisk server is available/running with the following : sipsak -vv -s sip:username at sip.domain.tld -c sip:username at sip.domain.tld --password guessthis --hostname XX.XX.XX.63 The SIP OPTION is received by Asterisk as follow : OPTIONS sip:username at sip.domain.tld SIP/2.0 Via: SIP/2.0/UDP

Hello, I'm having difficulty with registering a SIP account in a Snom 320 IP-phone. This is what sip debug tells me : [Oct 7 13:28:42] VERBOSE[20314] chan_sip.c: [Oct 7 13:28:42] <--- SIP read from UDP:public_ip:58697 ---> REGISTER sip:sip.domain.tld SIP/2.0 Via: SIP/2.0/UDP 192.168.114.200:2048;branch=z9hG4bK-vj1xvbdnp4dw;rport From: <sip:test3 at

On 2/20/15 6:15 AM, thufir wrote: > What's the difference between user "123" and "devries"? Based on the > output here, they seem the same..? > > tleilax*CLI> > tleilax*CLI> sip show users > Username Secret Accountcode > Def.Context ACL Forcerport > 201 password 201 > default

AHA! # 1 is the case! Seems the user was fooling around with the phone after the firmware upgrade. Shame that that setting couldn't be locked out. Thanks to Mr Tahir and Mr Stredicke for their spot on responses. -----Original Message----- From: Usman Tahir [mailto:Usman.Tahir@snom.de] Sent: Friday, September 23, 2005 12:34 AM To: ColinA@landmarkmasterbuilder.com Cc:

What's the difference between user "123" and "devries"? Based on the output here, they seem the same..? tleilax*CLI> tleilax*CLI> sip show users Username Secret Accountcode Def.Context ACL Forcerport 201 password 201 default No Yes 123

On Fri, 20 Feb 2015 15:07:35 -0500, Andres wrote: > This is showing nothing so I don't think your test message even made it > here. I think it looped in the 'doge' server. I was wondering the same thing :) in tleilax, I looked in /var/log/asterisk/messages and see: [Feb 20 15:13:19] VERBOSE[3661] chan_sip.c: [Feb 20 15:13:19] <--- SIP read from UDP:192.168.1.3:38154

On Fri, 20 Feb 2015 08:46:13 -0500, Andres wrote: > A "sip set debug on" will give you more info on why you are getting the > 404. It probably has to do something with your context/dialplan. on tleilax: tleilax*CLI> tleilax*CLI> sip set debug on SIP Debugging enabled tleilax*CLI> on doge: thufir at doge:~$ thufir at doge:~$ sudo sipsak -vv -s sip:devries at

Le 09/09/2016 ? 18:32, Madushan Geethanga a ?crit : > Hi, If you're not using RTP encryption did you uncheck the option in your RTP TAB from identity ? > > This is the log. ex dialling 0 from snom phone > > > <--- Received SIP request (1230 bytes) from UDP:123.231.72.210:33878 > <http://123.231.72.210:33878> ---> > INVITE sip:0 at 54.206.59.252

On 2/20/15 3:20 PM, thufir wrote: > On Fri, 20 Feb 2015 15:07:35 -0500, Andres wrote: > >> This is showing nothing so I don't think your test message even made it >> here. I think it looped in the 'doge' server. > > I was wondering the same thing :) > > > in tleilax, I looked in /var/log/asterisk/messages and see: > > [Feb 20 15:13:19]

On 2/20/15 2:29 PM, thufir wrote: > On Fri, 20 Feb 2015 08:46:13 -0500, Andres wrote: > > >> A "sip set debug on" will give you more info on why you are getting the >> 404. It probably has to do something with your context/dialplan. > > on tleilax: > > tleilax*CLI> > tleilax*CLI> sip set debug on > SIP Debugging enabled > tleilax*CLI>

Hello List- I'm having a problem getting snom 190 phones to transfer a call to another local extension. Here is the scenario: A call (call1) comes in from the PSTN to (exten1). (via pri, if that matters) Another call (call2) comes in to (exten1). (call1) is put on hold while (call2) is answered. (call2) is then transferred to (exten2) using the "Xfer" button on the snom phone. This

Sorry if this is an obvious question, but I haven't seen an obvious answer on the wiki that I remember. Has anyone managed to make the record button on the snom 360 fire off the Monitor() application? I don't see a bounty, and googling for "snom 360 record button asterisk" returns tons of product specification pages. (Joy!) I don't see a bounty for it, and the only

Have someone running fine Alert-Info with a Snom 370 ( System Information: Phone Type: snom370-SIP MAC-Address: 0004132661BD IP-Address: 192.168.10.170 Firmware-Version: snom370-SIP 7.3.14 14961) i've tried exten => 200,1,SIPAddHeader(Alert-Info:<http://www.notused.com>\;info=alert-external) exten => 200,n,Dial(SIP/${EXTEN},30) Can see into the phone SIP trace is

Hello, I have BLF working on Snom phones. Ringing state (blinking) or "on the phone" state (solid) are working well. So the buttons are configured as "BLF" in the Snom webinterface. Now I would like to add another state for unavailable or dnd. In fact I would like to turn the LED red in the case the phone is not registered or the user pushed the DND button. So I though

I was always puzzled by posts to the list about people having problems getting hints to work on a Snom, since I always seem to have no problem making it work. That is, until today when I tried to get a sidecar to work. All I could do was get a monitored extension light to light up continuously, regardless of state. Frustrating! Going back to my working dialplans where I got 1 or 2 lights working