Discussions

In the V1 API I could send object=device, action=update, domain=, device=, check-sync=yes. This would, I believe, send a SIP INFO message to the device. I don't see an equivalent in the V2 method PUT /v2/domains//users//devices/. What value should I send in the PUT? is it still "check-sync=yes"?

As it stands now, if there is a bug in a client code or even a malicious attempt, a single client can potentially overload the API and as such the rest of the platform which we have seen in real world settings.

I get a 202 accepted but its never updated

How are others in the community handling messaging compliance requirements, specifically with regards to the opt-out message and adding STOP responders to the outbound blocking list? Is the only option manual addition and management by the user/customer or has someone put together a creative solution?

The UI Parameter 'PORTAL_EXTRA_JS' allows for custom JavaScript to be inserted into the portal. Several elegant solutions including prompt-voice has successfully used this to integrate their third party application directly into the Manager Portal.

How to use api v2 to set CUSTOM agent states please ?

When trying to add a new dial rule into a dial plan via the docs, I found that the field "dail-rule-matching-to-uri" is mispelled. I started looking through all of the calls under the Dialrule category and found that it's mispelled in the other calls too. Can we get this fixed?

Is there any detailed documentation on 'agent' events ?

Hi,

Hi,