I am Implementing the call back feature and getting error "
Runtime Error
Description:An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine."
Unfortunately not. Originate is on an extension level, so you won't be able to have a hunting facility for this.
We do have a call back feature on the TMS which can be linked to any hunt list on the TMS. For further information regarding that, please do contact our support team on 010 593 4500
I have tested the call and it does seem that there is a fault with your API key. You will see a new API Key under your API Manager. Please try that key and see it that works for you.
Best regards
Bailey
S
Sarika Verma
said
about 3 years ago
Hi Bailey,
I have checked the API Key in API Manager and it is the same as in our code.
Please confirm if we are supposed to use the value of Friendly Name field in Name Tag ?
It would be helpful if you could check the log file of your server and can share the error details when we tried to call the API from our server.
Kindly share the XML string used by you along with the code so that I can compare and fix it.
Thanks,
Sarika
B
Bailey Brooke
said
about 3 years ago
Hi Sarika.
No you would use your actual Tenant Name in the <Name> tag. Not the friendly API key name.
Best Regards
Bailey
S
Sarika Verma
said
about 3 years ago
Hi Bailey,
Can you check the server log and let us know what error it is showing for our web service call as at our end it is giving the same error.
Thanks, Sarika
S
Sarika Verma
said
about 3 years ago
Hi Bailey,
API Seems working at end, can we add hunting facility to the call back feature?
Thanks,
Sarika
S
Sarika Verma
said
about 3 years ago
Hi Bailey,
Thank you for the guidance, need to know if we can add a hunting facility to the call back feature?
Thanks,
Sarika
Divan le Roux
said
about 3 years ago
Answer
Hi Sarika,
Unfortunately not. Originate is on an extension level, so you won't be able to have a hunting facility for this.
We do have a call back feature on the TMS which can be linked to any hunt list on the TMS. For further information regarding that, please do contact our support team on 010 593 4500
Sarika Verma
Hi
I am Implementing the call back feature and getting error "
Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine."<XML>
<Tenant>
<Name>XXXXX</Name>
<Auth>
</Tenant>
<ActionName>Originate</
<extension>107-Multisure</
<dialNumber>Phone Number<
</XML>
Kindly assist to get it fixed
Hi Sarika,
Unfortunately not. Originate is on an extension level, so you won't be able to have a hunting facility for this.
We do have a call back feature on the TMS which can be linked to any hunt list on the TMS. For further information regarding that, please do contact our support team on 010 593 4500
Thank you
- Oldest First
- Popular
- Newest First
Sorted by Oldest FirstBailey Brooke
Good day Sarika
I hope you are well.
I have tested the call and it does seem that there is a fault with your API key. You will see a new API Key under your API Manager. Please try that key and see it that works for you.
Best regards
Bailey
Sarika Verma
Hi Bailey,
I have checked the API Key in API Manager and it is the same as in our code.
Please confirm if we are supposed to use the value of Friendly Name field in Name Tag ?
It would be helpful if you could check the log file of your server and can share the error details when we tried to call the API from our server.
Kindly share the XML string used by you along with the code so that I can compare and fix it.
Thanks,
Sarika
Bailey Brooke
Hi Sarika.
No you would use your actual Tenant Name in the <Name> tag. Not the friendly API key name.
Best Regards
Bailey
Sarika Verma
Hi Bailey,
Can you check the server log and let us know what error it is showing for our web service call as at our end it is giving the same error.
Thanks,
Sarika
Sarika Verma
Hi Bailey,
API Seems working at end, can we add hunting facility to the call back feature?
Thanks,
Sarika
Sarika Verma
Hi Bailey,
Thank you for the guidance, need to know if we can add a hunting facility to the call back feature?
Thanks,
Sarika
Divan le Roux
Hi Sarika,
Unfortunately not. Originate is on an extension level, so you won't be able to have a hunting facility for this.
We do have a call back feature on the TMS which can be linked to any hunt list on the TMS. For further information regarding that, please do contact our support team on 010 593 4500
Thank you
-
How to Download Call Recordings using Particular Phone no using API
-
GetInboundCallingHistory issue
-
Billing cost per call.
-
Provisioning (VC Related)
-
CRM URL Request
-
Data Content Packs
-
sharing contacts in agent manager to yelink phone handset
-
Search for multiple numbers
-
API Call to get total inbound and outbound calls for today
-
Pause Duration on Agent Manager
See all 116 topics