Yes, that's why I posted it in category Community > Features suggestions ;-) I'm looking forward to hear from you after a decision was taken. BR C
I confirm that it is working again. Merci.
See also Case 00638324 + 00638322 + 00638320
Baptiste CANDELIER told me:You have to raise a Product Enhancement Request at your ALE Sales Manager.Today we have just the following actions and information for incoming calls available: ${localUs...
Doesn't work for me in the current WebRTC version. Have posted here instead:https://support.openrainbow.com/hc/en-us/community/posts/360010252139-SNMP-support-on-WebRTC-server?page=1#community_comm...
Hi, the feature is still listed as planned? The current implementation is not very detailed.I need IP Tickets like in OXE to identify the exact connections.The chart just tells me something is wron...
Hallo Michael, Stand heute gibt es nur die Aktion für Ankommende Anrufe mit folgenden Informationen: ${localUser.firstName}${localUser.lastName}${localUser.phoneNumber}${localUser.email}${localUser...
Hi Stefan, this should be finally fixed in the current Rainbow version even for big customers. ;o) Liebe GrüßeChristian
It's possible but can be done by ALE PS only. (not free of charge) And it's cheaper in a bunch. BR Christian
There is also an error: [telephonyService] getTelephonyState -- failure -- <error xmlns="jabber:client" type="modify"><bad-request xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/><text xmlns="urn:ietf...