| 00:26.06 | *** join/#asterisk-dev infobot (~infobot@rikers.org) |
| 00:26.06 | *** topic/#asterisk-dev is Asterisk Development Discussion -=- http://www.asterisk.org/developers -=- Tier 2 and 3.14159265 support is in #asterisk -=- Check out our blog! blogs.asterisk.org -=- Follow on Twitter at @AsteriskDev |
| 00:33.47 | *** join/#asterisk-dev ZX81 (~Adium@190.218.194.116) |
| 03:52.27 | *** join/#asterisk-dev jkroon (~jkroon@165.16.204.165) |
| 04:32.25 | *** join/#asterisk-dev oej (~oej@h-205-12.A165.corp.bahnhof.se) |
| 04:32.25 | *** mode/#asterisk-dev [+o oej] by ChanServ |
| 06:20.29 | *** join/#asterisk-dev jkroon (~jkroon@165.16.204.165) |
| 06:32.13 | *** join/#asterisk-dev joshelson (~joshelson@l136.denver.dsl.forethought.net) |
| 06:50.40 | *** join/#asterisk-dev CELYA_ (~Thunderbi@2a06:a402:100:0:762f:68ff:fedf:4a19) |
| 06:51.03 | *** join/#asterisk-dev pchero_work (~pchero@109.70.54.56) |
| 06:51.35 | *** join/#asterisk-dev tsearle (~tsearle@37.19.10.33) |
| 07:00.35 | *** join/#asterisk-dev tsearle (~tsearle@37.19.10.33) |
| 07:02.45 | *** join/#asterisk-dev hehol (~hehol@gatekeeper.loca.net) |
| 07:21.31 | *** join/#asterisk-dev tzafrir (~tzafrir@local.xorcom.com) |
| 07:21.31 | *** mode/#asterisk-dev [+o tzafrir] by ChanServ |
| 08:09.59 | *** join/#asterisk-dev jkroon (~jkroon@165.16.204.37) |
| 11:21.34 | tsearle | good morning all |
| 11:22.07 | tsearle | I have a question ref pjsip/dialplan_functions.c |
| 11:22.34 | tsearle | how come pjsip_acf_media_offer_read doesn't accquire a lock before accessing channel->session ? |
| 11:28.29 | tsearle | and on a related note, all the *_write() methods access ast_channel_tech_pvt(chan)->session->serializer without accquiring a lock first, is it safe to access tech_pvt / session w/o getting a lock first? |
| 11:52.37 | tsearle | happy 4th of july / Canada day all btw |
| 11:57.35 | *** join/#asterisk-dev pc-m (~pcm@modemcable094.94-70-69.static.videotron.ca) |
| 12:16.34 | *** join/#asterisk-dev oej (~oej@h-205-12.A165.corp.bahnhof.se) |
| 12:16.34 | *** mode/#asterisk-dev [+o oej] by ChanServ |
| 12:16.46 | tsearle | waves to @oej |
| 13:00.08 | *** join/#asterisk-dev oej (~oej@h-205-12.A165.corp.bahnhof.se) |
| 13:00.08 | *** mode/#asterisk-dev [+o oej] by ChanServ |
| 13:07.55 | *** join/#asterisk-dev oej (~oej@h-205-12.A165.corp.bahnhof.se) |
| 13:07.55 | *** mode/#asterisk-dev [+o oej] by ChanServ |
| 13:24.12 | gtjoseph | tsearle: haven't looked at media offer read but using the session serializer is safe without a lock. |
| 14:07.02 | tsearle | @gtjoseph so that means acessing the ->endpoint is also safe? |
| 14:07.26 | gtjoseph | yeah, that's not going to change |
| 14:07.58 | gtjoseph | the serializer specifically is safe because the underlying code locks the serializer itself |
| 14:08.10 | gtjoseph | as long as there's a reference to the session, it'll be fine |
| 14:08.45 | *** join/#asterisk-dev oej (~oej@h-205-12.A165.corp.bahnhof.se) |
| 14:08.45 | *** mode/#asterisk-dev [+o oej] by ChanServ |
| 14:22.38 | *** join/#asterisk-dev bford (d8cff501@gateway/web/freenode/ip.216.207.245.1) |
| 14:24.40 | *** join/#asterisk-dev oej (~oej@h-205-12.A165.corp.bahnhof.se) |
| 14:24.40 | *** mode/#asterisk-dev [+o oej] by ChanServ |
| 14:24.59 | *** join/#asterisk-dev oej (~oej@h-205-12.A165.corp.bahnhof.se) |
| 14:24.59 | *** mode/#asterisk-dev [+o oej] by ChanServ |
| 14:25.27 | *** join/#asterisk-dev oej (~oej@h-205-12.A165.corp.bahnhof.se) |
| 14:25.27 | *** mode/#asterisk-dev [+o oej] by ChanServ |
| 14:46.00 | *** join/#asterisk-dev elguero (~miguel323@74-95-21-41-Connecticut.hfc.comcastbusiness.net) |
| 14:52.33 | *** join/#asterisk-dev newtonr (~newtonr@99-104-129-136.lightspeed.brhmal.sbcglobal.net) |
| 14:52.33 | *** mode/#asterisk-dev [+o newtonr] by ChanServ |
| 15:07.49 | *** join/#asterisk-dev elguero (~miguel323@74-95-21-41-Connecticut.hfc.comcastbusiness.net) |
| 16:09.30 | *** join/#asterisk-dev CELYA_ (~Thunderbi@LFbn-1-5197-25.w90-105.abo.wanadoo.fr) |
| 16:13.55 | *** join/#asterisk-dev joshelson (~joshelson@c-73-34-214-163.hsd1.co.comcast.net) |
| 17:12.38 | *** join/#asterisk-dev jkroon (~jkroon@165.16.204.165) |
| 18:15.27 | *** join/#asterisk-dev bford (18601790@gateway/web/freenode/ip.24.96.23.144) |
| 18:43.24 | *** join/#asterisk-dev oej (~oej@h-205-12.A165.corp.bahnhof.se) |
| 18:43.24 | *** mode/#asterisk-dev [+o oej] by ChanServ |
| 19:09.14 | *** join/#asterisk-dev skirmisha (~skirmisha@213.16.62.70) |
| 19:09.22 | skirmisha | hi guys |
| 19:09.45 | skirmisha | can you confirm something for me |
| 19:10.39 | gtjoseph | skirmisha: like what? |
| 19:10.52 | skirmisha | in 200 OK back from vendor i got Record-Route and Contact header...what header asterisk will use to answer with ACK back - to take the SIP URI - the Record-Route or Contact? |
| 19:11.07 | skirmisha | first is Record-Route and then Contact if that matters |
| 19:11.23 | gtjoseph | iirc it's record-route |
| 19:12.49 | skirmisha | i think so too |
| 19:12.49 | skirmisha | vendor is saying that it's the contact |
| 19:12.49 | skirmisha | call drops after a while... |
| 19:12.49 | gtjoseph | what's "a while"? |
| 19:13.00 | skirmisha | about 30 sec - timeout of ACK not being delivered |
| 19:13.34 | gtjoseph | any way to do a packet capture and see exactly what's happening? |
| 19:13.40 | skirmisha | according to rfc 3261 they say UAS must use contact header |
| 19:14.04 | gtjoseph | which asterisk version and is it chan_sip or chan_pjsip? |
| 19:16.30 | *** join/#asterisk-dev infobot (~infobot@rikers.org) |
| 19:16.30 | *** topic/#asterisk-dev is Asterisk Development Discussion -=- http://www.asterisk.org/developers -=- Tier 2 and 3.14159265 support is in #asterisk -=- Check out our blog! blogs.asterisk.org -=- Follow on Twitter at @AsteriskDev |
| 19:16.30 | skirmisha | yes, just wanted to confirm about rfc |
| 19:16.30 | file | it should use Record-Route |
| 19:16.39 | skirmisha | i think so too, but gonna be hard to explain to vendor |
| 19:18.04 | gtjoseph | https://www.packetizer.com/rfc/rfc5658/ has some examples |
| 19:19.36 | skirmisha | thanks, that will help me a lot |
| 19:27.52 | *** join/#asterisk-dev newtonr (~newtonr@99-104-129-136.lightspeed.brhmal.sbcglobal.net) |
| 19:27.52 | *** mode/#asterisk-dev [+o newtonr] by ChanServ |
| 19:52.31 | tm1000 | Is it CDR_PROP(disable)=true or CDR_PROP(disable)=1 |
| 19:52.48 | tm1000 | in the wiki it says use 1 or 0, everywhere on the internet its written as true |
| 19:52.52 | tm1000 | file: ^? |
| 19:54.25 | file | yes, true, y, t, 1, on |
| 19:54.32 | file | are valid. |
| 19:55.22 | tm1000 | got a bug report from a user that says it doesnt work at all |
| 19:55.41 | tm1000 | will look later... tomorrow or in 10 years |
| 19:55.44 | tm1000 | which ever comes later. |
| 19:58.35 | file | we have test coverage of that and it's not failing, so it's probably a particular scenario if it's being invoked |
| 20:03.03 | tm1000 | file: |
| 20:03.06 | tm1000 | user says |
| 20:03.08 | tm1000 | add any context |
| 20:03.13 | tm1000 | exten => 99999,1,Set(CDR_PROP(disable)=true) |
| 20:03.13 | tm1000 | exten => 99999,n,Congestion |
| 20:03.16 | tm1000 | dial that ^ |
| 20:03.24 | tm1000 | and Congestion will always show up |
| 20:03.33 | tm1000 | You can use Busy rather than Congestion if you like. Make a call to 99999 and if you are on an affected system there will be a CDR entry for the call. Before NoCDR() was deprecated, using NoCDR() would have kept a CDR entry from being generated. |
| 20:03.44 | tm1000 | <PROTECTED> |
| 20:03.49 | file | ok |
| 20:05.25 | file | didn't for me |
| 20:10.23 | file | only if I don't do a CDR_PROP(disable) or if I use a Local channel does one appear for me |
| 20:58.54 | *** join/#asterisk-dev DivideBy0 (~DivideBy0@unaffiliated/divideby0x0) |
| 20:58.54 | *** mode/#asterisk-dev [+o DivideBy0] by ChanServ |
| 21:11.54 | *** join/#asterisk-dev tzafrir (~tzafrir@bzq-179-40-170.cust.bezeqint.net) |
| 21:11.54 | *** mode/#asterisk-dev [+o tzafrir] by ChanServ |
| 22:33.24 | *** join/#asterisk-dev infobot (~infobot@rikers.org) |
| 22:33.24 | *** topic/#asterisk-dev is Asterisk Development Discussion -=- http://www.asterisk.org/developers -=- Tier 2 and 3.14159265 support is in #asterisk -=- Check out our blog! blogs.asterisk.org -=- Follow on Twitter at @AsteriskDev |
| 23:14.01 | *** join/#asterisk-dev infobot (~infobot@rikers.org) |
| 23:14.01 | *** topic/#asterisk-dev is Asterisk Development Discussion -=- http://www.asterisk.org/developers -=- Tier 2 and 3.14159265 support is in #asterisk -=- Check out our blog! blogs.asterisk.org -=- Follow on Twitter at @AsteriskDev |
| 23:51.16 | *** join/#asterisk-dev snuff-work (~snuff-wor@210.9.148.102) |
| 23:51.16 | *** mode/#asterisk-dev [+o snuff-work] by ChanServ |
| 23:54.23 | *** join/#asterisk-dev joshelson (~joshelson@l136.denver.dsl.forethought.net) |