12-10-2015 07:58 AM - edited 03-17-2019 05:11 AM
I managed to initiate calls by the protocol handlers (e.g. tel:+491511232323423) so Jabber dials the number for me on windows...
but for dialing into our seamless communication platform with the respective conference numbers (e.g. "777888999#")
On various mobile phones this is supported by writing down the dial string
1) tel:+491511232323423,,777888999#
This is actually good old modem syntax... anyways...
Alternatives to , or ; are the letters 'w' (for wait for connect) and 'p'
So an alternative to 1 would be
2) tel:+491511232323423w777888999#
but Jabber does not support this logic/protocol but instead the following happens:
So how can I enable this?
Thank you for support!
12-29-2015 05:35 PM
Hello!
When we boil this down to the root of what you're trying to do; you want a way to dial a number with a delayed secondary dial, from the Jabber client.
This really has more to do with the call control server (i.e CCM) than the Jabber client, although the limitation is essentially the same. The Jabber client uses CCM as it's call control server; at the end of the day the Jabber client's dialing abilities are beholden to what the call control server can and can't do. Every time you dial an external (PSTN) number from a Jabber client, it works because your dialed digits ultimately matched a PSTN capable route in the call control server.
CCM's call processing engine does not support the old-style 'pause/delay' tricks (, , w, p, ; ... etc) outside of speed dials that are associated with devices. The RegEx engine won't even validate it (i.e you can't save a pattern with those characters in it).
In other words, you can use the 'pause/delay tricks' in speed dials that you can create for IP phones but you cannot use them in route patterns, translation patterns or transform masks (which is what would interact with dialed digits coming from a Jabber client).
However, there are usually ways to bend or work around rules, right?
If your PSTN gateway interfaces with CCM via SIP/H.323, then you can insert the delay behavior in dial peer destination patterns. Applied to your example, you would match the dialed digits from the Jabber client to a route in CCM that could send a transformed called party mask (if needed to avoid overlaps ... etc) to the SIP/H.323 gateway which then would match a dial-peer with a destination pattern using the required delayed dialing behavior.
Thanks,
Ryan
(: ... Please rate helpful posts ... :)
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide