search for: doge

...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 tleilax -m "hi" No SRV record: _sip._tcp.tleilax No SRV record: _sip._udp.tleilax using A record: tleilax Max-Forwards set to 0 message received: SIP/2.0 404 Not Found Via: SIP/2.0/UDP 127.0.1.1:56377;branch=z9hG4b...

...: No Sess-Timers : Accept Sess-Refresh : uas Sess-Expires : 1800 secs Sess-Min-SE : 90 secs RTP Engine : asterisk Codec Order : (ulaw:20,gsm:20) Auto-Framing: No tleilax*CLI> tleilax*CLI> exit tleilax:~ # tleilax:~ # exit logout Connection to tleilax closed. thufir at doge:~$ thufir at doge:~$ sudo sipsak -vv -s sip:123 at tleilax [sudo] password for thufir: No SRV record: _sip._tcp.tleilax No SRV record: _sip._udp.tleilax using A record: tleilax message received: SIP/2.0 200 OK Via: SIP/2.0/UDP 127.0.1.1:55238;branch=z9hG4bK.3e59b63f;alias;received=192.168.1.3;r...

...; ACL : No Sess-Timers : Accept Sess-Refresh : uas Sess-Expires : 1800 secs Sess-Min-SE : 90 secs RTP Engine : asterisk Codec Order : (ulaw:20,gsm:20) Auto-Framing: No tleilax*CLI> which would make the URI sip:thufir101 at tleilax.bounceme.net ? thufir at doge:~$ thufir at doge:~$ sudo sipsak -vv -s sip:thufir101 at tleilax No SRV record: _sip._tcp.tleilax No SRV record: _sip._udp.tleilax using A record: tleilax message received: SIP/2.0 200 OK CSeq: 1 OPTIONS Via: SIP/2.0/UDP 127.0.1.1:52173;branch=z9hG4bK.4ca3965f;rport=52173;alias;received=192.168....

...Some sort of "hello world" connection. 192.168.1.1 netgear router 192.168.1.2 asterisk (vicidial) 192.168.1.3 ubuntu client 192.168.1.4 mac OSX client (not shown) Do I have a firewall problem which would impact a soft phone from establishing a connection? thufir at doge:~$ thufir at doge:~$ thufir at doge:~$ nmap 192.168.1.1 Starting Nmap 6.46 ( http://nmap.org ) at 2015-02-18 06:10 PST Nmap scan report for 192.168.1.1 Host is up (0.0086s latency). Not shown: 994 closed ports PORT STATE SERVICE 23/tcp open telnet 53/tcp open domain 80/tcp open...

..., at least it reports "registered". Curiously, when I exit Ekiga and switch to SFLphone, it isn't able to connect with the exact same parameters; it just says "trying" and never resolves. I'm not able to test outside connectivity because of too many hops: thufir at doge:~$ thufir at doge:~$ sudo sipsak -vv -s sip:thufir at ekiga.net -m "hi" No SRV record: _sip._tcp.ekiga.net No SRV record: _sip._udp.ekiga.net using A record: ekiga.net Max-Forwards set to 0 message received: SIP/2.0 483 Too Many Hops Via: SIP/2.0/UDP 192.168.1.3:44370;branch=z9hG4bK.6f...

...bly has to do something with your context/dialplan. > > on tleilax: > > tleilax*CLI> > tleilax*CLI> sip set debug on > SIP Debugging enabled > tleilax*CLI> This is showing nothing so I don't think your test message even made it here. I think it looped in the 'doge' server. > > > on doge: > > thufir at doge:~$ > thufir at doge:~$ sudo sipsak -vv -s sip:devries at tleilax -m "hi" > No SRV record: _sip._tcp.tleilax > No SRV record: _sip._udp.tleilax > using A record: tleilax > Max-Forwards set to 0 > > message r...

...pires : 1800 secs > Sess-Min-SE : 90 secs > RTP Engine : asterisk > Codec Order : (ulaw:20,gsm:20) > Auto-Framing: No > > tleilax*CLI> > tleilax*CLI> exit > tleilax:~ # > tleilax:~ # exit > logout > Connection to tleilax closed. > thufir at doge:~$ > thufir at doge:~$ sudo sipsak -vv -s sip:123 at tleilax > [sudo] password for thufir: > No SRV record: _sip._tcp.tleilax > No SRV record: _sip._udp.tleilax > using A record: tleilax > > message received: > SIP/2.0 200 OK > Via: SIP/2.0/UDP > 127.0.1.1:55238;branch...

Hi ggplot experts, I need to plot two time series of stacked data: a barchart with bars for each month. To compare the data of two years I need to combine both time series with in a single graph via position=doge. How should I do that? I tried the following scenario: I added two layers with the time series of the stacked data for both years. That worked well exept the bars are obscuring each other. How can I shift one of the layers to get them displayed next to each other. Is there an other easier way...

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 ---> OPTIONS sip:345 at tleilax SIP/2.0 Via: SIP/2.0/UDP 127.0.1.1:38154;bran...

I'm reading the O'Reilly "Asterisk the definitive guide", 4th ed, with a starfish on it. In some ways, astonishing that it's not really that definitive, it's more general -- and it only clocks in at one ream of paper! In any event, I'm having some port problems on my home network: http://security.stackexchange.com/questions/81752/ I need to open ports for

...p+geom_bar(position="dodge",stat="identity") dodge <- position_dodge(width=-0.9) > p + geom_bar(position="dodge") + geom_errorbar(limits, position=dodge, > width=0.5) Why do I need to use negative values to get the right errorbar structure, why do I need use doge without quote marks? Thanks Beto -- View this message in context: http://n4.nabble.com/simple-plot-in-ggplot2-wrong-error-bars-tp1589994p1589994.html Sent from the R help mailing list archive at Nabble.com.

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] VERBOSE[3661] chan_sip.c: [Feb 20 15:13:19] > <--- SIP read from UDP:192.168.1.3:38154 ---> > OPTIONS sip:345 at tleilax SIP/2....

I called 102 from 101 successfully! I have everything connected to my home router. Asterisk is running on tleilax, so I used my Android phone to call doge. Worked like a charm. I'd been thinking that the firewall was blocking connections, but not at all. Anyhow, thanks to everyone who's help me out. I'm sure I'll have other problems, but huge milestone. -Thufir

...table/blob/V_7_8_P1/myproposal.h#L102 I was just thinking that if this hasn't been causing a problem for the last 2 releases then maybe its time to disable this by default in the client. This algorithm has been disabled by default in the server since the 6.7 release in October 2014. -- Jon Doge Wrangler X(7): A program for managing terminal windows. See also screen(1) and tmux(1).