| 00:40.37 | *** join/#asterisk-dev Qwell (~north@pdpc/sponsor/digium/Qwell) |
| 00:40.37 | *** mode/#asterisk-dev [+o Qwell] by ChanServ |
| 01:21.22 | jsmith | Qwell: Random question -- where do I find the new packaging for pjproject? |
| 01:28.37 | snuff-home | mm i have a question too.. is there a way from ast cli to see the new xml 'config' related entries |
| 01:37.54 | coreyf1513 | jsmith: packages.asterisk.org has pjproject rpm's |
| 01:38.21 | jsmith | coreyf1513: Yeah, I found those -- trying to build an RPM for Fedora though, and the CentOS package is pretty rough |
| 01:38.39 | jsmith | coreyf1513: (and I'm admittedly picky about my packages) |
| 01:43.15 | coreyf1513 | does anyone know if res_sip bug's/patches should be posted against trunk or pimp_my_sip? |
| 01:46.43 | snuff-home | if the part ur working on fixing is pretty 'set'.. i'd say just do trunk.. can't hurt to have patch for both |
| 02:50.35 | jsmith | Anybody started playing with stasis_http yet? |
| 02:50.49 | jsmith | I'm having a hard time getting it to return anything useful :-( |
| 02:52.08 | snuff-home | mm.. i thought there was an 'example' recently committed |
| 02:52.45 | snuff-home | sighs.. my passphrase for commit access has been lost from my mind |
| 02:54.40 | jsmith | snuff-home: I thought so too, but I haven't found it :-( |
| 02:55.52 | snuff-home | https://reviewboard.asterisk.org/r/2460/diff/#index_header |
| 02:56.21 | jsmith | Ok, that's stasis, but not stasis_http |
| 02:56.36 | jsmith | I'm looking for information on the REST API, not on the message bus itself |
| 02:57.05 | snuff-home | https://reviewboard.asterisk.org/r/2376/ |
| 02:57.27 | snuff-home | https://github.com/asterisk/asterisk_rest_libraries |
| 02:57.41 | snuff-home | is 1 of the links off that reviewboard submission |
| 03:14.49 | opticron | snuff-home, on the CLI "config show help <tab>" |
| 03:15.51 | opticron | the first tab completion is modules, the second is config sections, and the next is individual options with descriptions and defaults |
| 03:17.11 | opticron | also, the example that was recently committed was direct consumption of stasis-core, not stasis-http |
| 03:17.53 | opticron | jsmith, a lot of the stasis-http stuff is just stubbed out, not fully implemented |
| 03:26.01 | snuff-home | thanks opticron.. not sure how i didn't find it already |
| 03:34.13 | opticron | :) |
| 03:37.42 | snuff-home | hopefully.. in the next day or so i will get to redoing / adding more to the res_sip doco.. just something that u really need to say 'i'm going to sit for an hr and bore myself with xml' |
| 03:42.32 | opticron | :) |
| 03:43.00 | opticron | I did that last night and a significant portion of today with json in the crazy stuff I'm about to commit to my team branch |
| 05:40.00 | *** join/#asterisk-dev jmls (~jmls@77.107.171.82) |
| 06:09.10 | *** join/#asterisk-dev oej (~Adium@2001:16d8:cc57:1000::42:1005) |
| 06:09.10 | *** mode/#asterisk-dev [+o oej] by ChanServ |
| 06:20.49 | *** join/#asterisk-dev oej (~Adium@2001:16d8:cc57:1000::42:1005) |
| 06:20.49 | *** mode/#asterisk-dev [+o oej] by ChanServ |
| 10:19.00 | *** join/#asterisk-dev oej (~Adium@h87-96-134-129.dynamic.se.alltele.net) |
| 10:19.01 | *** mode/#asterisk-dev [+o oej] by ChanServ |
| 10:23.28 | *** join/#asterisk-dev tzafrir (~tzafrir@local.xorcom.com) |
| 10:23.28 | *** mode/#asterisk-dev [+o tzafrir] by ChanServ |
| 13:04.22 | *** join/#asterisk-dev bkruse (~Adium@107-220-153-105.lightspeed.jcvlfl.sbcglobal.net) |
| 13:09.22 | *** join/#asterisk-dev snuff-home (~snuffy@203-219-29-182.tpgi.com.au) |
| 13:09.23 | *** mode/#asterisk-dev [+o snuff-home] by ChanServ |
| 16:19.18 | *** join/#asterisk-dev oej (~Adium@2001:16d8:cc57:1000::42:1003) |
| 16:19.18 | *** mode/#asterisk-dev [+o oej] by ChanServ |
| 16:35.34 | *** join/#asterisk-dev w9sh (~sph@50-79-224-193-static.hfc.comcastbusiness.net) |
| 17:18.28 | tm1000 | file: Ping |
| 17:18.46 | file | Pong |
| 17:20.15 | tm1000 | file: Did you check your keep alive. I'm assuming it works fine |
| 17:20.44 | file | I checked and it gets sent out |
| 17:21.01 | tm1000 | The people at pbx in a flash are sure that your keep alive is failing because they only see replies from google. Not to google with debug active and asterisk idling. |
| 17:21.32 | file | Debug level has to be at 2 or more, core debug level |
| 17:21.41 | file | Core set debug 3 |
| 17:21.49 | file | Or else the log message is not output |
| 17:22.44 | tm1000 | Ok. They see replies. But I'll have them set that |
| 17:23.28 | file | A firewall should not be tearing down TCP connections like that |
| 17:24.08 | tm1000 | file: A decent firewall shouldn't. I'm sure these guys have cheap ones |
| 17:24.49 | tm1000 | I'm tempted to create a temp account on my google apps server and see if it times out for me. Then give then creds |
| 17:26.07 | file | I'll grab a packet capture when I'm home to be absolutely sure iksemel is sending the packet... But if the nat wants bidirectional traffic it won't get it with that keepalive |
| 17:34.24 | tm1000 | file: Iksemel scares me. Soooo outdated |
| 17:35.20 | file | It doesn't do that much for us |
| 17:37.40 | tm1000 | file: Silly me. I always assumed -rvvvv set the debug higher |
| 17:38.04 | file | Just verbose |
| 17:38.17 | tm1000 | I see successful keep alives on mine. What's the standard google voice port. I'll capture as well |
| 17:38.30 | file | 5222 |
| 17:38.49 | file | It is encrypted so you won't be able to see the contents |
| 17:39.07 | tm1000 | Ah. How do you do it then? Decrypt the packets? |
| 17:40.17 | file | Nah, I just use it to see if traffic is flowing |
| 17:40.41 | file | I use xmpp set debug for the contents |
| 17:41.49 | tm1000 | Ah |
| 17:42.06 | tm1000 | Well mines been up for 48 hours and its getting replies |
| 17:44.51 | file | Yeah I still fail to see a problem I can solve |
| 18:02.36 | tm1000 | file: im honestly about done with this thread... |
| 18:02.57 | file | Understood |
| 18:03.34 | tm1000 | file: the users are now saying that your keep alive is broken because its saying "recieved from" and not "sent to" |
| 18:05.17 | file | Yeah that's a bug, but minor |
| 18:05.47 | tm1000 | file: the bug being that its saying receieved instead of sent right? |
| 18:06.07 | file | Yes |
| 18:06.19 | tm1000 | easy enough to fix.I may just do it myself. |
| 18:06.27 | file | Can you pull up res_xmpp.c and confirm? |
| 18:09.49 | tm1000 | file: http://pastebin.com/JZbfetUw |
| 18:10.34 | tm1000 | "XMPP keep alive from" should be "XMPP keep alive sent to" |
| 18:10.36 | tm1000 | I would think |
| 18:10.49 | file | Correct! |
| 18:11.00 | tm1000 | roger |
| 18:22.24 | tm1000 | might as well just add some more debugging into this file. for my puposes and perhaps pbx in a flash |
| 18:24.28 | file | sure! |
| 18:26.18 | tm1000 | file: how often does the keepalive occur. |
| 18:26.52 | file | 50 seconds I do believe |
| 18:29.31 | tm1000 | file: trying to figure out where you define that |
| 18:30.25 | file | the keep alive code is old so sadly it's hardcoded to 50 in places |
| 18:30.40 | file | if you search for "timeout = 50" you'll find it |
| 18:32.03 | tm1000 | ah! |
| 18:32.04 | tm1000 | in client_thread |
| 20:41.16 | *** join/#asterisk-dev GameGamer43 (uid5533@gateway/web/irccloud.com/x-neinprxdyfficybm) |
| 21:00.31 | *** join/#asterisk-dev italorossi (~italoross@187.61.168.117) |
| 21:19.20 | *** join/#asterisk-dev tzafrir (~tzafrir@212.179.75.202) |
| 21:19.20 | *** mode/#asterisk-dev [+o tzafrir] by ChanServ |
| 22:43.07 | *** join/#asterisk-dev saghul (~saghul@ip3e830637.speed.planet.nl) |
| 22:50.28 | *** join/#asterisk-dev italorossi (~italoross@187.61.168.117) |
| 23:24.57 | *** join/#asterisk-dev w9sh (~sph@50-79-224-193-static.hfc.comcastbusiness.net) |
| 23:39.31 | *** join/#asterisk-dev mwally (~mwally@mwally.opencnam.com) |
| 23:45.21 | *** join/#asterisk-dev italorossi (~italoross@201.76.144.193.digi.com.br) |
| 23:49.04 | *** join/#asterisk-dev italoros_ (~italoross@187.61.168.117) |