similar to: Re: asterisk iax2 monitoring

Hello there I''m just testing a module (see merging directories) and it is quite involved, in that it: __generic__ 1) creates a user 2) creates a base directory 3) copies generic files (directory with recursion) 4) generate a configuration file from a template 5) creates a symlink __os specific__ 6) copies os specific files (in my scenario two folders, and an init script) 7)

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

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

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

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

Skipped content of type multipart/alternative-------------- next part -------------- A non-text attachment was scrubbed... Name: iaxping.c Type: text/x-csrc Size: 1272 bytes Desc: not available Url : http://lists.digium.com/pipermail/asterisk-users/attachments/20050919/2f97b5f1/iaxping.c

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

I've been playing around a little bit with the "veto files" option for the [homes] shares we have on our Samba servers (2.2.1a & 2.2.3a). I've discovered that: veto files = /.*/ works marvelously for not letting the users muck with their .dotfiles, which is exactly what we want, however, I've also discovered that it also clobbers the special directory entries

Hi, Following advice in voip-info.org, I could successfully send text to a remote SIP endpoint using sipsak and this command : # sipsak -M -v -s sip:7530 at 192.168.100.123 <sip%3A7530 at 192.168.100.123> -B "Lunch time" warning: ignoring -i option when in usrloc mode timeout after 500 ms timeout after 1000 ms timeout after 2000 ms timeout after 4000 ms timeout after 4000 ms

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]

I have 4 sparc based sun boxes I am about to pay money so I can get rid of them. They are running older versions of Solaris. You should be able to load Solaris 10 and play around with * on them. Time to clean the office: 3 Ultra 5 1 Sparcstation 5 I also have a box full of Sun keyboards and mice. Contact me offline if you want them. I've had many good years of development on them and it

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

I would be very interested in using sipsak for something like this. What have you tried so far? -Thufir On Mon, 16 Jan 2017, Olivier wrote: > Thinking over my previous, I wonder if sipsak could be used to send > outgoing SIP NOTIFY messages. > Would both Asterisk and sipsak be able to share networks resources ? > > Thoughts ? > > 2017-01-16 14:10 GMT+01:00 Olivier

I'm trying to upgrade a very old sparcstation running Solaris 8 which is running dovecot 1.x for few users. All I have for the task is good old gcc 2.95.2. The poor sod complains because it can't compute the sizeof(unsigned char prefix_text[]) at line 13 of log-error-buffer.c. Can I help it by - say - putting a constant between the '[]'? Or is it unfair? :-) I don't think

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

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've compiled openssh 1.2.2 on Solaris 7/SPARC. On most hosts, things are fine. I get EGD going, compile openssh, and I can then generate hostkeys as described in the INSTALL file to get things running. On a few hosts though, the keygen fails like this: root at sylow:/source/USR_LOCAL/OFFICIAL/OPENSSH/ssh_client# ssh-keygen -b 1024 -f /etc/ssh/ssh_host_key -N '' ksh:

Hi, I recently configured Linux HA for Asterisk service (using Asterisk resource agent downloaded from link: https://github.com/ClusterLabs/resource-agents/blob/master/heartbeat/asterisk ). As per configuration it is working good but when I include "monitor_sipuri=" sip:42 at 10.3.152.103" " parameter in primitive section it is giving me an errors like listed below; root at

Chris, > FYI, I completely agree that we shouldn't remove the sparc target. However, it is currently unmaintained, and has some pretty glaring bugs. Is anyone interested in stepping up to maintain the target? > > -Chris We can not let it die and I volunteer to keep the Sparc alive! My SPARCstation pizzaboxes can be ready for action in a day or two. Pawel Wodnicki > On Oct

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