Discussions

In this method post
https://{server}/ns-api/v2/domains/{domain}/phonenumbers the comments for the parm phonenumber says "This is the main phonenumber setting. Should be a formated in a e164 format with country count and number. US domestic numbers should be similiar to 18005551234".

The dialled parameter is spelled with two L's. Is that right?

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,