| 00:07.03 | *** join/#asterisk startledmarmot (~startledm@2601:646:c203:75d7:1d11:b534:7be:88b4) |
| 00:14.34 | *** join/#asterisk Inf0r (uid2810@gateway/web/irccloud.com/x-bmvxiuymptxbkdpu) |
| 00:25.44 | *** part/#asterisk kharwell (kharwell@nat/digium/x-wvbgjqtxekvtfppi) |
| 01:18.13 | *** join/#asterisk infobot (ibot@rikers.org) |
| 01:18.13 | *** topic/#asterisk is #asterisk The Open Source PBX and Telephony Platform (asterisk.org) -=- LTS: 13.19.0 (2018/01/11), Standard: 15.2.0 (2018/01/11); DAHDI: DAHDI-linux 2.11.1 (2016/03/01), DAHDI-tools 2.11.1 (2016/03/01); libpri 1.6.0 (2017/01/27) -=- Wiki: wiki.asterisk.org -=- Code of Conduct: bit.ly/1hH6P22 -=- Logs: bit.ly/1s4AKKu |
| 01:25.11 | *** join/#asterisk qxork (~qxork@unaffiliated/qxork) |
| 01:45.46 | *** join/#asterisk mTeK (~quassel@216.249.97.206) |
| 02:46.45 | *** join/#asterisk REDman2k1 (~NOT@6532101hfc04.tampabay.res.rr.com) |
| 02:49.33 | *** join/#asterisk dar123 (~dar@2600:1700:38d0:1470:f56b:78f0:2d2c:3122) |
| 02:53.36 | REDman2k1 | !seen vector |
| 03:06.36 | *** join/#asterisk mutin-s (~s-mutin@85.234.114.134) |
| 03:35.38 | *** join/#asterisk saint_ (~saint_@unaffiliated/saint-/x-0540772) |
| 03:52.52 | *** join/#asterisk robink (~quassel@unaffilated/robink) |
| 04:01.25 | *** join/#asterisk dar123 (~dar@2600:1700:38d0:1470:f56b:78f0:2d2c:3122) |
| 04:42.53 | *** join/#asterisk mahafyi (~chatzilla@182.65.185.124) |
| 05:13.45 | *** join/#asterisk rwb (~Thunderbi@65.183.151.121) |
| 05:16.21 | *** join/#asterisk Worldexe (~Worldexe@95-107-33-134.dsl.orel.ru) |
| 05:42.26 | *** join/#asterisk gerhard7 (~gerhard7@ip5657ee30.direct-adsl.nl) |
| 06:41.38 | *** join/#asterisk jamesaxl (~James_Axl@109.172.62.242) |
| 06:42.30 | *** join/#asterisk mahafyi (~chatzilla@42.111.170.163) |
| 07:17.33 | *** join/#asterisk miralin (~Thunderbi@91.237.94.4) |
| 07:28.29 | *** join/#asterisk jeffspeff (~me@209.141.208.197) |
| 07:33.26 | jeffspeff | I'm setting up BLF with hints. on polycom vvx 411. everything seems to be working, except the notification of CID says "to: 2001 from: 2001" where 2001 is the extension number my phone has subscribed to. what am i missing to make the "from" show the actuall CID? |
| 07:34.04 | *** join/#asterisk justdave (~dave@unaffiliated/justdave) |
| 07:54.09 | *** join/#asterisk startledmarmot (~startledm@2601:646:c203:75d7:f944:5d0e:6bde:da88) |
| 08:02.15 | *** join/#asterisk defsdoor (~andy@cpc120600-sutt6-2-0-cust177.19-1.cable.virginm.net) |
| 08:10.50 | *** join/#asterisk hehol (~hehol@gatekeeper.loca.net) |
| 08:13.11 | *** join/#asterisk polysics (~polysics@host17-71-dynamic.49-79-r.retail.telecomitalia.it) |
| 08:13.19 | polysics | hey! how's things? |
| 08:13.36 | polysics | we are dealing with a weird interop issue on Asterisk 15 SFU using Firefox and Chrome |
| 08:13.53 | polysics | any chance someone has worked on that or can point me to the right mailing list/source? |
| 08:14.02 | jeffspeff | SFU? |
| 08:16.35 | polysics | jeffspeff: Selective Forwarding Unit |
| 08:16.57 | polysics | Asterisk 15 has a great one |
| 08:31.33 | *** join/#asterisk SoBlindWolf (~SoBlindWo@go.pcshost.co) |
| 08:33.44 | *** join/#asterisk justdave_ (~dave@unaffiliated/justdave) |
| 08:43.49 | *** join/#asterisk pchero_work (~pchero@109.70.54.56) |
| 08:45.11 | *** join/#asterisk gerhard7 (~gerhard7@ip5657ee30.direct-adsl.nl) |
| 08:55.02 | *** join/#asterisk areski (~areski@154.red-83-47-211.dynamicip.rima-tde.net) |
| 08:55.43 | *** join/#asterisk boris_t (~boris_t@109.248.217.2) |
| 09:27.17 | *** join/#asterisk mahafyi (~chatzilla@42.111.170.163) |
| 09:37.52 | *** join/#asterisk Catatronic (~corrupt@unaffiliated/catatronic) |
| 09:52.39 | *** join/#asterisk u0m3_ (~u0m3@86.127.131.167) |
| 10:09.04 | *** join/#asterisk Dovid (~dovid@ool-45738ae3.dyn.optonline.net) |
| 10:45.45 | *** join/#asterisk mahafyi (~chatzilla@122.174.13.97) |
| 10:55.15 | z3ntu | Is it recommended to keep an AMI connection all the time or log in, send the action and log out again? |
| 10:55.20 | z3ntu | I didn't find anything about that online |
| 11:22.13 | *** join/#asterisk paulgrmn (~paulgrmn@198-0-107-153-static.hfc.comcastbusiness.net) |
| 11:42.51 | *** join/#asterisk comrad (~comrad@holarse/core/comrad) |
| 11:44.03 | *** join/#asterisk DanB (~DanB@clt-195.192.205.245.ip-anschluss.net) |
| 11:47.19 | *** join/#asterisk gerhard7 (~gerhard7@ip5657ee30.direct-adsl.nl) |
| 11:48.48 | *** join/#asterisk gerhard7 (~gerhard7@ip5657ee30.direct-adsl.nl) |
| 11:50.35 | *** join/#asterisk lankanmon (~LKNnet@CPE64777dd7e053-CM64777dd7e050.cpe.net.cable.rogers.com) |
| 11:58.25 | *** join/#asterisk jkroon (~jkroon@209.203.34.30) |
| 12:10.09 | *** join/#asterisk sotoz (~sotoz@095-097-255-066.static.chello.nl) |
| 12:12.34 | sotoz | hello |
| 12:13.43 | sotoz | I'm getting this wierd situation where Asterisk is sending a re-INVITEs without the connection-address in the connection data (c= field) in the SDP. |
| 12:13.49 | sotoz | Have you guys seen that before? |
| 12:14.09 | sotoz | so the c= field looks like 'c=IN IP4' |
| 12:14.28 | sotoz | although it should look like 'c=IN IP4 10.10.10.1' for example |
| 12:16.05 | sotoz | asterisk version 14.0.2 |
| 12:38.03 | *** join/#asterisk sekil (~sekil@nat-73.net011.net) |
| 13:02.18 | *** join/#asterisk dar123 (~dar@2600:1700:38d0:1470:f56b:78f0:2d2c:3122) |
| 13:39.23 | *** join/#asterisk brad_mssw (~brad@66.129.88.50) |
| 13:48.14 | *** join/#asterisk qxork (~qxork@unaffiliated/qxork) |
| 13:50.39 | *** join/#asterisk [TK]D-Fender (~joe@216.191.106.165) |
| 14:35.13 | *** join/#asterisk cemotyz09 (~cemotyz09@cpe-70-121-157-202.satx.res.rr.com) |
| 14:49.28 | bittis | i have a question regarding asterisk and the h extension: when a call terminates and there is an h extention in the context it is in now then the code in h gets executed, if execution arrived in that context via jump from another context, will the original context's h extension code be executed as well? |
| 14:51.24 | Samot | No |
| 14:54.26 | bittis | so only 1 h section gets executed |
| 14:54.46 | bittis | if that context doesn't have one, will it go to the h section of the "parent" context? |
| 14:55.01 | file | no. |
| 14:55.16 | bittis | so last context is always the final context |
| 14:55.36 | file | if you want behavior like that then hangup handlers are a better fit, https://wiki.asterisk.org/wiki/display/AST/Hangup+Handlers |
| 14:55.55 | bittis | ok thank you guys, was getting some strange behaviour with my ael dial plan and wasn't sure why |
| 14:56.01 | bittis | let me check hangup handlers |
| 14:56.47 | bittis | minimum version 11 |
| 14:56.53 | *** join/#asterisk kharwell (kharwell@nat/digium/x-vblzntlpdqzjqpeh) |
| 14:56.53 | *** mode/#asterisk [+o kharwell] by ChanServ |
| 14:57.36 | bittis | won't work for me as some of my servers are on older versions and until they retire i am force to write in compatibility mode |
| 14:57.52 | bittis | will try and do an #include to save repeating the same code over and over |
| 14:58.20 | Samot | Not in the h |
| 14:58.34 | bittis | won't work in h? |
| 14:58.36 | Samot | Oh wait, I think have can take #includes. |
| 14:58.41 | Samot | er h |
| 14:59.00 | Samot | "Until the retire? |
| 14:59.14 | Samot | Asterisk 13 and 15 are the stable versions. |
| 14:59.20 | Samot | it's been _years" |
| 14:59.28 | bittis | will be replaced with 13 LTS |
| 14:59.38 | bittis | i am all about if it isn't broken don't fix it |
| 14:59.39 | bittis | :P |
| 14:59.42 | Samot | If you are still running 1.8 or less machines, there isn't a "until they" it should be "they are" |
| 14:59.45 | Samot | No. |
| 14:59.48 | Samot | That's wrong. |
| 15:00.12 | bittis | i inherited them, replacing them wasn't possible so far |
| 15:00.14 | bittis | but getting there |
| 15:03.10 | Samot | Wouldnt this be the fuel to help that? |
| 15:12.08 | bittis | couldn't agree more |
| 15:12.20 | *** join/#asterisk mou (~donwillia@37.97.50.103) |
| 15:21.17 | *** join/#asterisk afournier (~admin@80.215.180.210) |
| 15:22.28 | afournier | Hi, when receiving a Q931_PROG_CALL_NOT_E2E_ISDN, "Call is not end-to-end ISDN; further call progress information may be available inband." from a Telco, inband is not forwarded, to the caller on the SIP-side, is it normal ? |
| 15:23.42 | afournier | it's just forwarded as a PRI_EVENT_PROGRESS(17) => PROGRESS with cause code 114 received |
| 15:26.58 | afournier | sip.conf / progressinband=yes might be the answer... |
| 15:33.07 | *** join/#asterisk jeffspeff (~me@209.141.208.197) |
| 15:33.18 | *** join/#asterisk bford (d8cff501@gateway/web/freenode/ip.216.207.245.1) |
| 15:33.19 | *** mode/#asterisk [+o bford] by ChanServ |
| 15:48.45 | *** join/#asterisk Worldexe (~Worldexe@95-107-33-134.dsl.orel.ru) |
| 15:50.57 | *** part/#asterisk afournier (~admin@80.215.180.210) |
| 15:51.50 | *** join/#asterisk Dirk23 (Dirk23@diehildebrands.de) |
| 15:52.36 | *** join/#asterisk rmudgett (rmudgett@nat/digium/x-bbryybjlqgmnxyma) |
| 15:52.36 | *** mode/#asterisk [+o rmudgett] by ChanServ |
| 16:04.16 | *** join/#asterisk ihatewindoze (~jwpierce3@mail.trunkmasters.com) |
| 16:32.55 | *** join/#asterisk hfb (~hfb@47.139.17.73) |
| 16:40.37 | *** join/#asterisk DanB (~DanB@clt-195.192.205.245.ip-anschluss.net) |
| 16:58.21 | *** join/#asterisk cresl1n (~Adium@asterisk/libpri-and-libss7-expert/Cresl1n) |
| 16:58.21 | *** mode/#asterisk [+o cresl1n] by ChanServ |
| 17:29.01 | *** join/#asterisk ChkDigit (~u388mw@74.3.144.66) |
| 17:29.06 | *** join/#asterisk waldo323 (~waldo323@75.151.31.89) |
| 17:30.37 | *** join/#asterisk SoBlindWolf (~SoBlindWo@go.pcshost.co) |
| 17:36.01 | *** join/#asterisk startledmarmot (~startledm@156.39.10.47) |
| 17:51.14 | jeffspeff | I'm setting up BLF with hints. on polycom vvx 411. everything seems to be working, except the notification of CID says "to: 2001 from: 2001" where 2001 is the extension number my phone has subscribed to. what am i missing to make the "from" show the actuall CID? |
| 18:06.32 | Samot | Didnt we fix this yesterday? |
| 18:06.46 | Samot | Thr NOTIFY doesnt have the CID info |
| 18:07.40 | Samot | I thought you added the notifycid setting on the peer? |
| 18:12.13 | jeffspeff | that was on a different system. |
| 18:12.50 | jeffspeff | i tried replicating that setup last night and i put 'notifycid=yes' in the general section of sip.conf |
| 18:12.59 | Samot | OK, the answer is the same. |
| 18:13.48 | jeffspeff | without the notifycid setting, the from field is empty. with the notifycid setting the from field shows the extension that is being dialed not the CID. |
| 18:14.31 | *** join/#asterisk overyander (~Jeff@12.49.160.131) |
| 18:15.40 | jeffspeff | yesterday, adding notifycid=yes to sip.conf fixed the problem of the from field being empty. on this other system, the from field is showing the incorrect value. |
| 18:17.42 | Samot | ; Note that this feature will only work properly when the |
| 18:17.43 | Samot | <PROTECTED> |
| 18:17.43 | Samot | <PROTECTED> |
| 18:17.43 | Samot | <PROTECTED> |
| 18:17.43 | Samot | <PROTECTED> |
| 18:18.26 | jeffspeff | i read that too, the phone context is the same context with the extensions and the hints |
| 18:19.01 | Samot | Including the calling channel? |
| 18:19.11 | Samot | So both channels are in the same context? |
| 18:20.23 | jeffspeff | in order to dial the phone, you have to be in the user-extens context. that is the same context set for the sip peers. |
| 18:21.07 | Samot | No you don't. |
| 18:21.14 | Samot | you just need a Dial() |
| 18:21.22 | Samot | That can be initiated from any context. |
| 18:21.38 | jeffspeff | on my setup, the only dials to the extensions are in the user-extens context |
| 18:22.03 | Samot | So phone A is dialing to Phone B and Phone C is BLFing B? |
| 18:23.14 | jeffspeff | yes |
| 18:24.08 | jeffspeff | the blf shows up and everything works except that the "to" and "from" fields shown on the phone show the same value (the extension being dialed) |
| 18:25.26 | Samot | And what does the actual NOTIFY have in it? |
| 18:25.32 | Samot | What is it sending to the phone? |
| 18:25.46 | Samot | The phone is displaying what is being sent to it. |
| 18:27.53 | *** join/#asterisk batphone (~daddy@cpe-72-183-123-208.stx.res.rr.com) |
| 18:27.56 | jeffspeff | just did a capture, let me sanitize and post |
| 18:28.08 | batphone | been a long time since ive worked on asterisk. can someone tell me what happened to zaptel? |
| 18:28.20 | batphone | ztcfg isnt available any more |
| 18:28.36 | batphone | it looks like it got merged into this dahdi stuff, is that correct? |
| 18:29.16 | Samot | Like a long time ago |
| 18:29.29 | batphone | its been about 11 years since ive worked on them.. |
| 18:29.42 | batphone | but i found a tdm400p i want to try out at home ;) |
| 18:30.13 | Samot | Well you might want to make sure it's even usable. |
| 18:30.19 | batphone | its in this box |
| 18:30.22 | batphone | looks usable |
| 18:30.26 | batphone | lspci shows its there |
| 18:30.26 | Samot | And can run on current versions of DAHDI. |
| 18:30.31 | Samot | OK. |
| 18:30.31 | batphone | ah. |
| 18:30.41 | Samot | I'm talking about Asterisk. |
| 18:33.08 | jeffspeff | Samot https://pastebin.com/mPfccaA0 |
| 18:34.54 | Samot | Show the dialplan context |
| 18:36.09 | jeffspeff | https://pastebin.com/LxKtcvDN |
| 18:41.33 | batphone | damn. it doesnt look like this old card is compatible |
| 18:41.50 | batphone | 06:05.0 Communication controller: Tiger Jet Network Inc. Tiger3XX Modem/ISDN interface |
| 18:42.02 | batphone | according to everything all it requires is the wctdm module to be loaded |
| 18:42.18 | batphone | which it is, and a Telephony device is now registered in the kernel |
| 18:42.26 | batphone | but these dahdi tools dont seem to see the card |
| 18:48.58 | batphone | hmm. so can i use the old zaptel drivers? |
| 18:49.11 | batphone | is asterisk backward-compatible with that stuff? |
| 18:50.45 | jeffspeff | any ideas Samot? |
| 18:55.41 | Samot | Where's the hints context? |
| 18:56.05 | Samot | Never mind, I was thinking of something else. |
| 18:56.54 | Samot | Oh, you're not setting the CallerID |
| 18:57.11 | Samot | You're spawning a new channel with you Dial() |
| 18:57.37 | Samot | I think that could be it. |
| 18:57.43 | Samot | Might try that. |
| 19:03.42 | *** join/#asterisk cresl1n (~Adium@asterisk/libpri-and-libss7-expert/Cresl1n) |
| 19:03.42 | *** mode/#asterisk [+o cresl1n] by ChanServ |
| 19:05.38 | *** join/#asterisk billxx (49958984@gateway/web/freenode/ip.73.149.137.132) |
| 19:06.23 | *** join/#asterisk billxx (49958984@gateway/web/freenode/ip.73.149.137.132) |
| 19:07.14 | *** join/#asterisk robink (~quassel@unaffilated/robink) |
| 19:41.33 | jeffspeff | the first priority of the exten verboses the CID info and it shows correctly there in the * console and the extension that receives the call shows the CID correctly, it's just the "from" field in the BLF notify that shows incorrectly. |
| 19:52.53 | *** join/#asterisk DivideBy0 (~DivideBy0@unaffiliated/divideby0x0) |
| 19:52.53 | *** mode/#asterisk [+o DivideBy0] by ChanServ |
| 19:56.48 | *** join/#asterisk dar123 (~dar@2600:1700:38d0:1470:f56b:78f0:2d2c:3122) |
| 19:59.37 | jeffspeff | I'm starting to think this is a bug in this version of * |
| 20:10.21 | *** join/#asterisk jkroon (~jkroon@165.16.204.167) |
| 20:14.02 | *** join/#asterisk areski (~areski@37.223.2.207) |
| 20:16.22 | *** join/#asterisk malcolmd (malcolmd@pdpc/sponsor/digium/malcolmd) |
| 20:16.23 | *** mode/#asterisk [+o malcolmd] by ChanServ |
| 20:19.01 | *** join/#asterisk cresl1n (~Adium@asterisk/libpri-and-libss7-expert/Cresl1n) |
| 20:19.01 | *** mode/#asterisk [+o cresl1n] by ChanServ |
| 20:26.15 | *** join/#asterisk miralin (~Thunderbi@91.237.94.4) |
| 20:40.04 | *** join/#asterisk miralin (~Thunderbi@91.237.94.4) |
| 20:40.11 | *** part/#asterisk igcewieling (~ewieling@speedy-02.nyigc.net) |
| 20:57.39 | Samot | What version of asterisk? |
| 20:58.26 | *** join/#asterisk imcdona (~imcdona@2607:f0d8:20:1001:30bd:d471:2b1e:a682) |
| 20:59.47 | jeffspeff | Asterisk 13.1-cert2 |
| 21:00.23 | jeffspeff | the box that i got it working on yesterday is version Asterisk 11.2.1 |
| 21:03.07 | Samot | Well |
| 21:03.11 | Samot | Thats old |
| 21:03.29 | *** join/#asterisk gerhard7 (~gerhard7@ip5657ee30.direct-adsl.nl) |
| 21:03.31 | Samot | 13.19 |
| 21:03.43 | Samot | So..highly possible |
| 21:05.31 | jeffspeff | I compared the notify packets on each version. ver 13.1 is sending the same info in the local and remote sections. the remote section is what should contain the CID |
| 21:07.58 | *** join/#asterisk miralin (~Thunderbi@91.237.94.4) |
| 21:15.35 | jeffspeff | Samot read this https://issues.asterisk.org/jira/browse/ASTERISK-24488 and here's the posted 'workaround' https://github.com/kettenbach-it/asterisk-snom-pickup-info-xml-agi |
| 21:16.04 | jeffspeff | from the github page... "The problems with this feature where fixed in some versions somewhere between 1.8 and 12 but are broken again in recent versions." |
| 21:22.44 | *** join/#asterisk chandoo (~chandoo@pool-74-105-13-92.nwrknj.fios.verizon.net) |
| 21:58.14 | *** join/#asterisk startledmarmot (~startledm@cpe-75-82-221-87.socal.res.rr.com) |
| 22:53.42 | *** part/#asterisk qxork (~qxork@unaffiliated/qxork) |
| 23:09.36 | *** part/#asterisk kharwell (kharwell@nat/digium/x-vblzntlpdqzjqpeh) |
| 23:13.12 | *** join/#asterisk [TK]D-Fender (~joe@64.235.216.2) |
| 23:28.17 | *** join/#asterisk Alex_Bkash (84cde528@gateway/web/freenode/ip.132.205.229.40) |
| 23:37.39 | *** join/#asterisk u0m3 (~u0m3@86.127.131.167) |