00:12.40 | *** join/#asterisk lankanmon (~LKNnet@CPE64777d632383-CM64777d632380.cpe.net.cable.rogers.com) |
00:14.21 | *** join/#asterisk [d__d] (~d__d]@ec2-54-85-45-223.compute-1.amazonaws.com) |
00:14.30 | *** join/#asterisk remote (~remote@50.116.54.131) |
02:24.48 | *** join/#asterisk infobot (ibot@208.53.50.136) |
02:24.48 | *** topic/#asterisk is #asterisk The Open Source PBX and Telephony Platform (asterisk.org) -=- LTS: 13.23.1 (2018/09/20) 16.0.0 (2018/10/09), Security Only: 15.6.1 (2018/09/20); 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 |
02:31.48 | *** part/#asterisk ssieb (~chatzilla@S010610bf487c4f29.cc.shawcable.net) |
02:45.47 | *** join/#asterisk cemotyz09 (~cemotyz09@cpe-70-121-128-59.satx.res.rr.com) |
02:54.05 | *** join/#asterisk cemotyz09 (~cemotyz09@cpe-70-121-128-59.satx.res.rr.com) |
02:59.55 | *** join/#asterisk awkwardpenguin (~awkwardpe@cpe-172-118-246-147.socal.res.rr.com) |
03:10.45 | *** join/#asterisk _mwoodj_ (~mwoodj@pdpc/sponsor/digium/hyper-eye) |
03:21.57 | *** join/#asterisk Cory (~Cory@unaffiliated/cory) |
03:26.55 | *** join/#asterisk awkwardpenguin (~awkwardpe@cpe-172-118-246-147.socal.res.rr.com) |
04:08.52 | *** join/#asterisk Oatmeal (Suzeanne@gateway/vpn/privateinternetaccess/suzeanne) |
04:09.22 | *** join/#asterisk cemotyz09 (~cemotyz09@cpe-70-121-128-59.satx.res.rr.com) |
04:13.50 | *** join/#asterisk cemotyz09 (~cemotyz09@cpe-70-121-128-59.satx.res.rr.com) |
04:30.50 | *** join/#asterisk gerhard7 (~gerhard7@ip5657ee30.direct-adsl.nl) |
04:59.15 | *** join/#asterisk awkwardpenguin (~awkwardpe@cpe-172-118-246-147.socal.res.rr.com) |
05:33.25 | *** join/#asterisk awkwardpenguin (~awkwardpe@cpe-172-118-246-147.socal.res.rr.com) |
06:22.46 | *** join/#asterisk pchero (~pchero@87.213.247.82) |
06:27.48 | *** join/#asterisk pchero (~pchero@87.213.247.82) |
07:02.11 | *** join/#asterisk awkwardpenguin (~awkwardpe@cpe-172-118-246-147.socal.res.rr.com) |
07:08.24 | *** join/#asterisk awkwardpenguin (~awkwardpe@cpe-172-118-246-147.socal.res.rr.com) |
07:20.54 | *** join/#asterisk tehgooch (tehgooch@unaffiliated/tehgooch) |
07:46.05 | *** join/#asterisk awkwardpenguin (~awkwardpe@cpe-172-118-246-147.socal.res.rr.com) |
07:47.10 | *** join/#asterisk evil_gordita (robert@ip70-188-41-127.rn.hr.cox.net) |
07:58.27 | *** join/#asterisk miralin (~Thunderbi@194.8.128.68) |
08:05.29 | *** join/#asterisk pchero (~pchero@60.30.148.146.bc.googleusercontent.com) |
08:45.02 | *** join/#asterisk stefanauss (~stefanaus@host222-246-static.59-217-b.business.telecomitalia.it) |
08:54.47 | *** join/#asterisk kangtastic (~kangtasti@2600:1700:31e0:5d90:6dde:6c84:759:b5d2) |
10:25.41 | *** join/#asterisk qxork (~qxork@unaffiliated/qxork) |
10:32.58 | *** join/#asterisk bhuddah (~michael@unaffiliated/bhuddah) |
10:48.11 | *** join/#asterisk MarkSX (~MarkSX@unaffiliated/marksx) |
10:49.19 | *** join/#asterisk lankanmon (~LKNnet@CPE64777d632383-CM64777d632380.cpe.net.cable.rogers.com) |
11:11.11 | *** join/#asterisk pchero (~pchero@87.213.247.82) |
11:46.03 | *** join/#asterisk pchero (~pchero@87.213.247.82) |
11:57.24 | *** join/#asterisk sh_smith (~sh_smith@cpe-76-174-26-91.socal.res.rr.com) |
12:08.26 | *** join/#asterisk cemotyz09 (~cemotyz09@cpe-70-121-128-59.satx.res.rr.com) |
12:21.43 | *** join/#asterisk samwierema (~samwierem@195.240.143.134) |
12:29.22 | *** join/#asterisk [TK]D-Fender (~joe@216.191.106.165) |
12:29.30 | *** join/#asterisk pchero (~pchero@87.213.247.82) |
13:06.43 | *** join/#asterisk jjg (~clh@75-147-197-114-Atlanta.hfc.comcastbusiness.net) |
13:06.47 | *** join/#asterisk xyz111 (~Thunderbi@2a02:c7d:3c50:3a00:cbe:abcc:b354:3ba0) |
13:12.10 | *** join/#asterisk soloma (~soloma@5.152.45.182) |
13:13.15 | soloma | Hello all. Could you help me with devices states sharing? Is there a way to subscribe for presence and dialog event from asterisk to kamailio? |
13:13.39 | *** join/#asterisk brad_mssw (~brad@66.129.88.50) |
13:14.26 | *** join/#asterisk cresl1n (uid299068@asterisk/libpri-and-libss7-expert/Cresl1n) |
13:14.26 | *** mode/#asterisk [+o cresl1n] by ChanServ |
13:19.29 | Samot | Not without some serious coding. |
13:19.30 | *** join/#asterisk pchero (~pchero@87.213.247.82) |
13:20.57 | soloma | Samot: What do you propose? |
13:21.18 | Samot | soloma: You would have to take the SUBSCRIBE from the device at the Kamailio level and have it register to the watchters via Kamailio... |
13:21.35 | Samot | Then use the UAC module to send another SUBSCRIBE message to Asterisk. |
13:21.59 | soloma | It is a little bit different from my case. |
13:22.04 | Samot | So that Asterisk will send the NOTIFY to Kamailio and then you'll need to take that NOTIFY and process it to update all the watchers that are subscribed to it. |
13:22.07 | Samot | Or... |
13:22.27 | Samot | You can do what I do. |
13:22.46 | soloma | I have devices registered at Kamailio, and the current dialog and presence states are stored here. |
13:23.01 | soloma | And I need to populate them to Asterisks |
13:23.19 | Samot | Then you're writing code for this. |
13:23.25 | Samot | Just as I outlined above. |
13:25.00 | Samot | Just one small problem to keep in mind. Kamailio doesn't do outbound REGISTER/SUBSCRIBEs. |
13:25.08 | soloma | I already have that. I'm simply update states within pua_publish when I need to change states FROM asterisk. |
13:25.20 | soloma | There is no problem. |
13:25.46 | Samot | In order for Asterisk to update you on a device state, the Hint needs to be SUBSCRIBEd to. |
13:25.55 | Samot | Which means Kamailio is going to have to do that. |
13:26.22 | Samot | But it doesn't so you have to deal with the workaround. |
13:27.04 | soloma | For example, I want to get devices states with simple command from asterisk dialplan |
13:27.12 | Samot | That's AMI |
13:28.01 | soloma | So, there is no other, only push events to some app and updated device stated with setdivstate action? |
13:28.02 | *** join/#asterisk dandann00dle (uid120491@gateway/web/irccloud.com/x-xxumigmbidaluvdp) |
13:28.11 | Samot | Sigh. |
13:28.23 | *** join/#asterisk elcontrastador (~textual@70-90-215-98-BusName-ca.sacra.hfc.comcastbusiness.net) |
13:28.33 | Samot | In order for Asterisk to automatically update and send a NOTIFY for a device/hint... |
13:28.38 | Samot | It needs to be SUBSCRIBEd to. |
13:28.54 | Samot | Otherwise you need to use an AMI event listener for device state event changes. |
13:28.57 | soloma | But I cannot finf how to subscribe asterisk to kamailio |
13:28.57 | file | Samot: soloma is referring to the reverse I think |
13:29.05 | Samot | No. |
13:29.19 | Samot | He wants to use Kamailio for Presence/Watchers. |
13:29.36 | Samot | And let Kamailio push those NOTIFYs and handle the SUBSCRIBEs. |
13:29.38 | soloma | And as publisher |
13:29.45 | *** join/#asterisk u0m3 (~u0m3@82.76.83.7) |
13:29.51 | soloma | ok. |
13:29.53 | soloma | STOP |
13:29.55 | Samot | So in order to get the device states from Asterisk... |
13:30.10 | file | there is no included integration to allow such information from Kamailio to be pushed into Asterisk for usage |
13:30.18 | Samot | Right |
13:30.32 | Samot | 9:26:20 AM <Samot> But it doesn't so you have to deal with the workaround. |
13:30.43 | soloma | crap. |
13:30.55 | Samot | Which is what I've been trying to explain. |
13:31.55 | soloma | I think that it will be expensive to habdle each event and publish state from AMI. |
13:32.00 | Samot | You can create a Hint in Asterisk that can be SUBSCRIBEd to OR you can use an AMI even listener to get the states. |
13:32.45 | soloma | e.g. '1001' => hint: PJSIP/proxy-admin/sip:1001@admin.example.com:5060, [exten_test.conf:12] |
13:32.55 | soloma | It does not work. |
13:33.07 | Samot | Did you SUBSCRIBE to it? |
13:33.32 | Samot | There is a third option. |
13:33.40 | soloma | Do you mean to send subscribe from kamailio? |
13:33.45 | Samot | YES |
13:34.13 | soloma | I need send event in reverse. From Kamailio to Astersik |
13:34.20 | Samot | 9:21:34 AM <Samot> Then use the UAC module to send another SUBSCRIBE message to Asterisk. |
13:34.32 | Samot | Huh? |
13:34.38 | file | Kamailio is the presence source in soloma's case, not Asterisk |
13:34.44 | soloma | yeap |
13:34.46 | Samot | I know. |
13:34.57 | file | but they want to be able to push the calculated presence information in Kamailio to Asterisk |
13:35.06 | soloma | no |
13:35.10 | soloma | backward |
13:35.34 | file | this is too confusing, I give up |
13:35.36 | soloma | sorry. file is RIGHT |
13:35.50 | soloma | from Kamailio to Asterisk )))) |
13:35.57 | Samot | Why? |
13:36.23 | soloma | they are helpful in some application that required to skip busy users. |
13:36.46 | soloma | I think that the best way will be using FUNC_ODBC and database function |
13:36.53 | Samot | Wait... |
13:37.09 | Samot | Do you have individual peers/endpoints set up on Asterisk? |
13:37.41 | soloma | No. It is just media/application. All registration is handled by Kamailio |
13:37.51 | Samot | Then it's not going to work. |
13:38.11 | soloma | what exactly? |
13:38.14 | Samot | There's nothing on Asterisk for it to care about a "device" state. |
13:39.21 | Samot | 9:32:44 AM <soloma> e.g. '1001' => hint: PJSIP/proxy-admin/sip:1001@admin.example.com:5060, [exten_test.conf:12] |
13:39.40 | Samot | If there is no PJSIP endpoint 1001, not a thing is going to update that hint. There's no "device" to update. |
13:41.17 | Samot | The only place that is going to know if that device is "busy" is Kamailio by checking if the device has an active INVITE dialog happening. |
13:42.14 | soloma | I think that it is the better way . Just use func_odbs and function that calculates state |
13:42.28 | soloma | based on presensity table |
13:43.02 | Samot | Or you can use AMI and the AstDB and have Kamailio fire off an AMI action to update the AstDB with the device state. |
13:43.12 | Samot | And then you can look in the AstDB for the current state. |
13:43.20 | soloma | it won't load system as updates through AMI on each event. |
13:44.05 | soloma | The only thing I'm worrying about is queues module. |
13:44.18 | Samot | You need actual endpoints. |
13:44.59 | Samot | I just create an endpoint on Asterisk that I associate to the user on Kamailio. |
13:45.19 | soloma | ok. It works? |
13:45.20 | Samot | I let Asterisk deal with device states/BLF updates. |
13:45.39 | Samot | Yes. I create a static contact that points to the user on Kamailio. |
13:46.02 | Samot | When that endpoint is Dial()'d Asterisk updates the Hint. |
13:46.03 | soloma | and you see the state of device at asterisk? |
13:46.13 | soloma | Hmm |
13:46.32 | Samot | Which sends the NOTIFY to Kamailio. Kamailio in turn just does a lookup() for the user and then sends the NOTIFY to the device. |
13:46.36 | Samot | or devices. |
13:46.43 | Samot | Depending on how many contacts are registered. |
13:46.59 | Samot | When the device sends the SUBSCRIBE, I just route it to the associated endpoint on Asterisk. |
13:47.30 | Samot | It was too much a PITA to get Presentity to play middle man. |
13:47.31 | soloma | No. It won't work for me. |
13:47.47 | Samot | Plus it allows Asterisk to monitor the state of each endpoint. |
13:47.51 | Samot | For things like Queues. |
13:48.31 | soloma | I have a bunch of asterisks behind Kamailio |
13:48.38 | Samot | So do I. |
13:48.57 | Samot | Most of them in a multi-tenant setup on Asterisk. |
13:49.25 | soloma | How about sharing this status between asterisks? |
13:49.30 | soloma | Corosync? |
13:49.41 | Samot | Nope. |
13:49.48 | soloma | ? |
13:49.48 | Samot | I don't bounce them around systems. |
13:50.00 | Samot | There are primary systems then there are backups. |
13:50.05 | soloma | Unfortunatelly I do. |
13:50.08 | Samot | I don't "load balance" like that |
13:50.13 | Samot | Because, why? |
13:50.43 | soloma | To avoid problems with scaling system horizontally. |
13:50.51 | Samot | It's 2018. |
13:50.54 | Samot | VMs. |
13:50.58 | soloma | yeap |
13:51.09 | Samot | First, my boxes where built with a cap. |
13:51.15 | Samot | X user/Y Calls, etc. |
13:51.32 | Samot | When that cap gets to be over 80% full... |
13:51.41 | Samot | I schedule 15 minutes to resize the system. |
13:53.12 | soloma | Ok. But, in this 15 minutes, do you will have a problem with states and application availability? |
13:53.25 | Samot | No. |
13:53.38 | Samot | 9:49:59 AM <Samot> There are primary systems then there are backups. |
13:53.42 | sibiria | we scale stuff like this horizontally instead of vertically, to avoid downtime on any single machine unless necessary |
13:53.57 | soloma | so do I |
13:54.16 | *** join/#asterisk waldo323 (~waldo323@75-151-31-89-Michigan.hfc.comcastbusiness.net) |
13:54.24 | soloma | I do not want to worry that some conference or parking lot became unavailable |
13:54.30 | Samot | Well |
13:54.38 | sibiria | (not that we ever really need to do much scaling - asterisk, the way we use it, is incredibly resource-efficient) |
13:54.40 | Samot | At 5am, it is generally not a concern. |
13:54.55 | Samot | Plus, they move to the _backup_ system. |
13:55.01 | soloma | Of cource it is possible to move services such those to a dedicated server |
13:55.01 | Samot | Well they don't. |
13:55.06 | Samot | They're on Kamailio. |
13:55.35 | soloma | Conferences& Parked calls? |
13:55.42 | Samot | Huh? |
13:55.49 | Samot | I have a BACKUP of the PRIMARY system. |
13:56.04 | Samot | If primary system go buh-bye, Kamailio flips them to the backup. |
13:56.40 | Samot | Will calls go down? Sure. |
13:57.20 | Samot | I also said I do my updates at like 5AM. |
13:57.52 | Samot | I also do silly things like send Maintenance Notices to the end users in advanced. |
13:57.59 | soloma | I'm saying about case when you scale asterisks dynamically. Based on your actual load |
13:58.19 | Samot | "Hey, going to be doing updates between 5AM and 5:30AM. Could (or will be) X amount of downtime." |
13:58.31 | Samot | I don't scale "dynamically" |
13:58.46 | Samot | I setup a system that can support X Y and Z |
13:59.00 | soloma | I understand. I have another case. |
13:59.23 | soloma | I need to have ability to shut off 3 of 5 asterisk by night. |
13:59.58 | Samot | You mean shut off the servers or just stop Asterisk from running? |
14:00.33 | soloma | shut off server. Imagine that system is deployed on AWS. |
14:00.53 | Samot | So you want to shut down the server to save on billable resources? |
14:01.43 | soloma | Yes. |
14:02.16 | soloma | sibiria: Do you have something like I described? |
14:02.43 | sibiria | soloma: no we run the servers 24/7, but i do understand your concern, especially since you're using AWS which is expensive as hell |
14:03.05 | Samot | And a poor choice for running SIP services in general. IMO. |
14:03.20 | Samot | So are you Kamailio boxes on AWS? |
14:03.22 | soloma | It is requiments of few customers. |
14:03.26 | Samot | So are your Kamailio boxes on AWS? |
14:03.33 | sibiria | soloma: you could start with moving from on-demand to reserved. it will reduce your costs a lot |
14:03.52 | soloma | I now |
14:03.59 | soloma | I know |
14:04.00 | Samot | So are your Kamailio boxes on AWS? |
14:04.34 | soloma | No. Primary deal is just scalable multitenant. AWS was asked by few customers. |
14:04.53 | Samot | So are these 5 Asterisk boxes the customers? |
14:06.04 | soloma | Some of sysytems will be customerrs and hosted on their sites. |
14:07.24 | Samot | I personally wouldnt do daily power downs and startups |
14:08.13 | Samot | You are asking for trouble. |
14:08.59 | file | it takes a lot of work to do it right, in the end |
14:09.08 | Samot | Not to mention the added costs |
14:09.09 | soloma | yes... |
14:10.07 | Samot | Because if you power down the system and dont have Elastic IPs.... |
14:10.32 | Samot | You might end up with a different public ip when you power up |
14:10.45 | soloma | I was thinking about role-based system. Which is much more simplier. |
14:11.35 | soloma | No. Dummy load balancer <-> kamaili+failover one <-> asterisks as media/application servers |
14:12.05 | Samot | No to the ip? |
14:12.37 | soloma | Pablic IP is bound to load balancer |
14:12.51 | Samot | On AWS? |
14:13.52 | soloma | AWS is one of the cases which a far away from me now )))) it was just extreme example |
14:14.07 | Samot | Ok but i was refering to tgat |
14:14.25 | *** join/#asterisk jjg (~clh@75-147-197-114-Atlanta.hfc.comcastbusiness.net) |
14:14.55 | Samot | If you do this on AWS and are going to power down instances..you need Elastic IPs to ensure the public ip is always the same when they power back up |
14:15.04 | soloma | Load balancer on Elastic IP, PROXY/REGISTRAR Kamailio could have dynamic IP public IP |
14:16.49 | Samot | So Kamailio will be on AWS |
14:18.36 | soloma | Enywhere. IThere was a few requests about using system on AWS. |
14:19.57 | Samot | 10:11:34 AM <soloma> No. Dummy load balancer <-> kamaili+failover one <-> asterisks as media/application servers |
14:19.59 | soloma | I do not undestand that. Because there is billable traffic besides EC2 instances. |
14:20.10 | Samot | ^^ In that scenario, Kamailio is on AWS. |
14:20.32 | soloma | ))) |
14:20.32 | Samot | AWS just doesn't give you public IPs. |
14:21.03 | Samot | The public IP an EC2 instance is assigned when it is powered up is Dyanmic. |
14:21.06 | Samot | The public IP an EC2 instance is assigned when it is powered up is Dynamic. |
14:21.14 | soloma | I know! |
14:21.51 | Samot | So in the context of doing this on AWS there are some considerations that need to be kept in mind. |
14:22.08 | soloma | The system is not going to be used espesially at AWS. As I mentioned, we had requests from customers about ability to host it there. |
14:22.25 | Samot | The powering down of systems will lose their public IP unless it is an Elastic IP. |
14:22.33 | soloma | Elastic IP is cost $3 per month |
14:22.45 | Samot | Additionally, running Kamailio on AWS means that it is now behind NAT. |
14:22.58 | soloma | Only load balancer requires for static IP address. |
14:23.10 | soloma | symmetric NAT |
14:23.12 | Samot | So Kamailio will need to be setup not only to advertise it's public IP |
14:23.55 | Samot | But also to use that IP as it's "socket" IP instead of the private IP it will be bound to. So that when Kamailio sends out requests it has the proper IP populated. |
14:26.44 | soloma | Samot: please, forget about AWS. I need to make a lot of other things before start thinking about AWS deployment |
14:28.02 | soloma | I have a wroking config of Kamailio and Freeswitch somewhere. Honestly, I did not test it well. And it was a long ago. |
14:30.22 | soloma | I've just remembered one presentation from kamailio world. Which can help to make more efficient device state resolving. |
14:30.39 | soloma | In the queue module |
14:31.35 | Samot | Well was the presentation on FreeSWITCH or Asterisk and Queues? |
14:34.30 | soloma | asterisk and queues |
14:35.45 | sibiria | elastic IPs are free while connected. they only cost while reserved but not allocated or connected to a powered-down instance |
14:36.35 | sibiria | not really a cost to consider if you intent to only have those machines turned off 8 hours per day |
14:36.38 | sibiria | intend* |
14:37.30 | Samot | Sure but then you have that whole, powering up/down daily thing going on. |
14:37.51 | soloma | honestly, I do not understand reason to host system on aws. but its ability was requested. |
14:37.53 | Samot | Someone in #freepbx thought it was a good idea. Since the office was close, just turn off the server each night... |
14:38.05 | Samot | Until one morning, the instance wouldn't boot back up. |
14:38.29 | sibiria | soloma: surely because of its popularity. people without insight in the product still conflate it with quality |
14:38.33 | soloma | Don't touch if works |
14:39.02 | sibiria | to amazon's defense, AWS is a much better choice than GCE for many reasons |
14:39.14 | Samot | Sure. |
14:39.25 | Samot | But as someone who is providing voice services to customers... |
14:39.36 | Samot | Why would you set your voice platform up in the cloud behind NAT? |
14:39.46 | *** join/#asterisk Oatmeal (Suzeanne@gateway/vpn/privateinternetaccess/suzeanne) |
14:39.56 | soloma | some regulations acts, etc... of cource there could be reasons for enterprise or govs |
14:41.16 | *** join/#asterisk rmudgett (rmudgett@nat/digium/x-zgkovsorpnysrwnr) |
14:41.16 | *** mode/#asterisk [+o rmudgett] by ChanServ |
14:43.58 | soloma | Samot: I think that problem with powered off machine has a simple cause... |
14:44.40 | *** join/#asterisk pchero (~pchero@87.213.247.82) |
14:48.56 | soloma | sibiria: you wrote that you're using horizontal scaling. how do you resolve states sharing? |
14:49.49 | soloma | sibiria: or you route calls to exact asterisk? |
14:53.38 | *** join/#asterisk samwierema (~samwierem@195.240.143.134) |
14:56.37 | *** join/#asterisk samwierema (~samwierem@195.240.143.134) |
15:03.41 | sibiria | soloma: for inbound calls we use route53 (aws) to manage distribution/failover. as for outbound calls our application runs in parallel on all available machines; it scales automatically as per us just firing up one more instance |
15:05.26 | sibiria | and, equally, if one machine suddenly dies it just means we're running with less total capacity until the machine is up again |
15:14.32 | *** join/#asterisk pigpen (~mark@216-177-181-17.block0.gvtc.com) |
15:14.40 | soloma | something likes I'm trying to make now, but I guess you have the specific application. |
15:17.33 | pigpen | So, I have a customer who decied to go with a Mitel solution. They are in South Dakota, I'm in Texas, so I understand wanting local support. |
15:17.58 | pigpen | A feature they "touted" was called "Hot Desking". |
15:18.42 | *** join/#asterisk jjg (~clh@107-202-133-88.lightspeed.tukrga.sbcglobal.net) |
15:18.54 | *** join/#asterisk Oatmeal (Suzeanne@gateway/vpn/privateinternetaccess/suzeanne) |
15:18.54 | pigpen | So how it works, is in short, a call comes into the system, and rings both the desk phone and their cell. You answer the cell. You can then hit a button or exten and "pull" it to the desk phone. |
15:19.18 | pigpen | easy. I figure that part out. |
15:19.38 | pigpen | But the "push" part it a little more tricky. Or I'm making it more difficult than it should be. |
15:19.43 | *** join/#asterisk K0HAX (~michael@gateway/tor-sasl/k0hax) |
15:20.20 | pigpen | So with the call activly on the desk phone, they have a "push" button. The call is "seamlessly" transfered/bridged to the cell. |
15:21.02 | pigpen | Timing has to be right for the far end not to notice, but it seems the call must be answered at the cell before the call is bridged and send away from the desk phone. |
15:21.31 | pigpen | ideas? |
15:22.26 | Samot | You could probably setup an In-Call feature that calls the cell phone via an Originate / Local channel and when the cell phone is answered trigger an AMI action to Redirect / bridge the call to the cell phone channel. |
15:23.30 | Samot | The program a softkey on the phone that has that feature code+destination number( or lookup the destination number based on the user's CID) |
15:24.18 | Samot | Probably do the same thing in reverse but would have to use the actual feature code since it's a cell phone.. |
15:24.20 | pigpen | yeah. I like that. I was coming up with pieces of that, but not put together. I was thinking of an "in call" feature too. |
15:25.34 | pigpen | Pulling the call back is pretty easy. in the dialplan I just grab the associated channel and bridge it back to the desk phone. |
15:26.23 | pigpen | I havne't done anything with AMI. I've been more old school with asterisk. May be a good time to play. |
15:27.33 | Samot | AMI is as old school as it gets. |
15:27.48 | Samot | ARI would be the new school. |
15:30.08 | pigpen | Maybe I'm just getting my acronyms wrong. ie: I spend most of my time in extensions.conf since 2006-2007. If this is amy then, yes. AMI. |
15:33.16 | pigpen | heh, just googled AMI. Yeah, I've used that mostly for school districts processing bells and announcements. dam handy. |
15:47.57 | *** join/#asterisk awkwardpenguin (~awkwardpe@cpe-172-118-246-147.socal.res.rr.com) |
15:48.49 | *** join/#asterisk hehol (~hehol@gatekeeper.loca.net) |
15:50.52 | *** join/#asterisk Oatmeal (Suzeanne@gateway/vpn/privateinternetaccess/suzeanne) |
15:51.28 | *** join/#asterisk elcontrastador (~textual@70-90-215-98-BusName-ca.sacra.hfc.comcastbusiness.net) |
16:03.51 | *** join/#asterisk dakudos (~dakudos@c-73-243-106-97.hsd1.co.comcast.net) |
16:06.06 | *** join/#asterisk kharwell (~kharwell@67.231.202.3) |
16:06.06 | *** mode/#asterisk [+o kharwell] by ChanServ |
16:25.27 | *** join/#asterisk Oatmeal (Suzeanne@gateway/vpn/privateinternetaccess/suzeanne) |
16:29.13 | *** join/#asterisk Chotizei (chotaire@unaffiliated/chotaire) |
16:35.40 | *** join/#asterisk Cory (~Cory@unaffiliated/cory) |
16:39.06 | *** part/#asterisk kharwell (~kharwell@67.231.202.3) |
16:57.21 | *** join/#asterisk SeRi (~wtf@unaffiliated/seri) |
16:58.20 | *** join/#asterisk SeRi (~wtf@unaffiliated/seri) |
17:01.06 | SeRi | Penguin: whats going on man. Is been some time..... |
17:04.02 | *** join/#asterisk awkwardpenguin (~awkwardpe@cpe-172-118-246-147.socal.res.rr.com) |
17:12.07 | *** join/#asterisk russellb (~rustlebee@redhat/russellb) |
17:12.07 | *** mode/#asterisk [+o russellb] by ChanServ |
17:17.00 | *** join/#asterisk tripleslash (~triplesla@unaffiliated/imsaguy) |
17:18.20 | *** join/#asterisk tripleslash (~triplesla@unaffiliated/imsaguy) |
17:48.16 | Penguin | SeRi: Hey! Where you been? |
17:50.53 | SeRi | Penguin: dude! |
17:51.03 | SeRi | been around and about! |
17:51.05 | SeRi | LOL |
17:51.22 | SeRi | Penguin: how u been bro? |
17:53.18 | *** join/#asterisk tafa2 (~tafa2@t.ldn.dsrtnet.com) |
17:53.35 | Penguin | Typical stuff here. |
17:53.47 | SeRi | I hear that |
17:54.00 | SeRi | I was in and out... never saw you or dijib online |
17:54.06 | SeRi | so I just quit |
17:54.07 | SeRi | LOL |
17:54.12 | SeRi | Still using asterisk though |
17:54.34 | SeRi | you going to laugh |
17:54.54 | SeRi | I just upgraded from 1.8 to 13 and I am still needing to catch up |
17:54.55 | SeRi | LOL |
17:57.57 | SeRi | moved everything from oVirt to KVM (plain KVM) and shit just went to hell |
17:57.58 | SeRi | lol |
17:59.29 | *** join/#asterisk Penguin (~xwQ5kwYl6@our.systems.are.full.of.penguins.at.penguinsystems.net) |
18:15.00 | *** join/#asterisk cemotyz09 (~cemotyz09@cpe-70-121-128-59.satx.res.rr.com) |
18:16.14 | *** join/#asterisk defsdoor (~Andrew@cpc120600-sutt6-2-0-cust232.19-1.cable.virginm.net) |
19:13.47 | *** join/#asterisk setham (~textual@unaffiliated/setham) |
19:23.29 | *** join/#asterisk Penguin (~xwQ5kwYl6@our.systems.are.full.of.penguins.at.penguinsystems.net) |
19:40.26 | *** join/#asterisk Penguin (~xwQ5kwYl6@our.systems.are.full.of.penguins.at.penguinsystems.net) |
19:41.23 | *** join/#asterisk adhawkins (~adhawkins@musicbrainz/user/adhawkins) |
19:42.27 | *** join/#asterisk fonefreak (~root@c-76-105-87-190.hsd1.ga.comcast.net) |
19:49.38 | *** join/#asterisk Penguin (~xwQ5kwYl6@our.systems.are.full.of.penguins.at.penguinsystems.net) |
20:28.51 | *** join/#asterisk wakko1 (~wakko@176.164.185.84) |
20:48.25 | *** join/#asterisk Penguin (~xwQ5kwYl6@our.systems.are.full.of.penguins.at.penguinsystems.net) |
21:00.20 | *** join/#asterisk miralin (~Thunderbi@194.8.128.68) |
21:10.07 | *** join/#asterisk yokel (~yokel@unaffiliated/contempt) |
21:15.29 | *** join/#asterisk [TK]D-Fender (~joe@64.235.216.2) |
21:24.35 | *** join/#asterisk Jesterboxboy (~Thunderbi@84-115-150-8.cable.dynamic.surfer.at) |
22:06.19 | *** join/#asterisk tomaluca95 (~quassel@kde/developer/tomaluca) |
22:49.35 | *** join/#asterisk forgotmynick (uid24625@gateway/web/irccloud.com/x-zgtwzfhvkezeuyhs) |
23:27.52 | *** join/#asterisk jjg (~clh@mobile-166-172-59-241.mycingular.net) |
23:37.54 | *** join/#asterisk cemotyz09 (~cemotyz09@cpe-70-121-128-59.satx.res.rr.com) |