| 00:55.41 | *** join/#asterisk-dev pchero (~pchero@211.178.226.108) |
| 00:55.41 | *** mode/#asterisk-dev [+o pchero] by ChanServ |
| 01:03.01 | *** join/#asterisk-dev spatel (~spatel@pool-96-237-230-175.bstnma.fios.verizon.net) |
| 02:33.16 | *** join/#asterisk-dev spatel (~spatel@pool-96-237-230-175.bstnma.fios.verizon.net) |
| 08:25.57 | *** join/#asterisk-dev spatel (~spatel@pool-96-237-230-175.bstnma.fios.verizon.net) |
| 08:41.52 | *** join/#asterisk-dev AsteriskRoss (~AsteriskR@37.157.48.2) |
| 11:26.35 | *** join/#asterisk-dev spatel (~spatel@pool-96-237-230-175.bstnma.fios.verizon.net) |
| 14:20.28 | *** join/#asterisk-dev AsteriskRoss_ (~AsteriskR@37.157.48.2) |
| 15:00.26 | Dovid | file: Do you see any problem with a patch that would allow a user to set the contact_ruri from the dialplan (http://lists.digium.com/pipermail/asterisk-users/2020-November/295458.html) ? |
| 15:24.29 | file | setting the complete RURI yes, because that is very much shoot yourself in the foot ow it hurts |
| 15:24.49 | file | is there a reason why the option to use the callerid doesn't work? |
| 15:31.09 | Dovid | file: I am not talking about the RURI but the contact header. |
| 15:31.32 | file | I would be very against allowing an individual to set the entire Contact header |
| 15:31.36 | Dovid | Bandwidth requires the contact header to be the call back number if you call 911 (https://support.bandwidth.com/hc/en-us/articles/360006080074-911-Dynamic-Location-Routing-Integration) |
| 15:32.06 | file | the Contact user is safe to |
| 15:32.23 | Dovid | safe to? |
| 15:32.44 | file | change |
| 15:33.04 | Dovid | ah ok. So you mentioned you don't want users changing the entire contact header. How about |
| 15:33.56 | Dovid | if we take their example Contact: Jane Smith <sip:13215551234@example.com> I would want to change "Jane Smith" and "13215551234". This way we let Asterisk do the rest. |
| 15:34.07 | file | yes, those values are safe to modify |
| 15:35.05 | Dovid | ok. I will start working on a patch. It seems 13 is not EOL so we could make it for 13,16-18 ? |
| 15:35.19 | file | 13 does not receive bug fixes or new features |
| 15:35.44 | *** join/#asterisk-dev kharwell (uid358942@gateway/web/irccloud.com/x-gpfwnwitoalpvjfl) |
| 15:35.44 | *** mode/#asterisk-dev [+o kharwell] by ChanServ |
| 15:35.48 | Dovid | :( We are still on 13. I see were past 10/24..... |
| 15:36.03 | Dovid | dont tell anyone were still on 1.8 for some systems. |
| 15:36.18 | Dovid | I am sure this will help others. Let me work on a patch |
| 15:36.21 | seanbright | if it ain't broke don't fix it |
| 15:36.39 | Dovid | seanbright: I hate keeping a list of patches that need to get applied every time |
| 15:37.30 | *** join/#asterisk-dev bford (uid283514@gateway/web/irccloud.com/x-fbgkmctdyztgqsqy) |
| 15:37.30 | *** mode/#asterisk-dev [+o bford] by ChanServ |
| 15:49.29 | seanbright | this year i am thankful for all of the sangoma asterisk developers. even the canadian ones. |
| 15:50.17 | Dovid | Is it that time already? dont we stop work at 4:30? |
| 20:29.30 | *** join/#asterisk-dev elguero (~miguel323@c-73-238-205-3.hsd1.nh.comcast.net) |
| 20:29.30 | *** mode/#asterisk-dev [+o elguero] by ChanServ |
| 21:00.51 | *** join/#asterisk-dev jkroon (~jkroon@165.16.203.107) |
| 21:00.51 | *** mode/#asterisk-dev [+o jkroon] by ChanServ |