-
lvlinuxHey guys: when using the channels API to execute a callflow, it seems to be applied to both sides of the call. I tried setting the 'leg' key to 'bleg' (like transfer uses) but looking at the code it doesn't seem to be accepted. So what is the proper way to just send the remote side of a call to a specific callflow?
-
lvlinuxAlso, if I try to park a call by transferring it with the channels API to *3101 for slot 101, one side gets put on hold with music, and the other side gets sent to 'nouser⊙mc' and just rings forever. I do have a transfer metaflow on the account, and if I transfer to a real extension like 2001 it works and rings the appropriate phones for that extension. I also tried sending to a park
-
lvlinuxcallflow, which doesn't work correctly either (it is like both sides parked each other at the same time, but no slot numnber is played or taken up, so neither call actually gets parked).
-
lvlinuxSo any insight on properly using the channels API would be helpful.
-
mc_lvlinux: the command will be executed against the channel you specify
-
mc_but it may affect a bridged leg, depending
-
mc_depends on the action being taken
-
mc_but i suspect you would need to transfer using /channels/{REMOTE_LEG} to get it to a new ext/callflow
-
mc_but might need to unbridge/break it first?
-
lvlinuxmc_ ah maybe that's what I'm missing---the break. I'll experiment with that some and see if I can get it to make sense.
-
lvlinuxHmm well doing a break on both channels didn't seem to stop the callflow from being applied to both. It didn't seem to unbridge them either. Do I need some specific metaflow on the account for break to work or something?
-
lvlinuxThe only metaflow I have on the account is one for transfer.