Discussions
Screen Pop API "User Not In Experiement"
Hi, we would like access to the screen_pop_api. Based on previous questions here, Dialpad Support has to enable it on our account. Please go ahead and do so.
Cross Origin Issue with CTI
I have integrated Dialpad CTI in my hosted react webapp. I am able to make calls alright. Now i wrote a script to initiate calls using the contentWindow.postmessage() following the api docs. but i get Uncaught DOMException: Failed to read a named property 'globals' from 'Window': Blocked a frame with origin "https://dialpad.com" from accessing a cross-origin frame.
SMS messages not routing correctly
Hi there, I have dialpad sms and calls set up in my application. It works MOST of the time however recently I had two instances where the sms were not sent correctly. How I have it set up is that we have contact centres with individual dialpad numbers inside related to clients. When a call comes in it goes to the dialpad number (client), and then is answered at the contact center level by a user. I can text directly from the app and have it set up to send texts from the contact centre level and uses the current call information to record which dialpad number to send the sms from, to which people reply and users can reply from in dialpad.
SMS Event Subscription (API) process
I'm using Zapier successfully with calls and contacts for integration and I want to work with SMS as well which requires me to create a webhook and then use that to create an SMS event subscription. My understanding is that the steps are these:
Dialpad CTI - Outgoing call event
Currently from the dialpad CTI docs, I could see that there is an event that dialpad sends for incoming call - https://developers.dialpad.com/docs/dialpad-mini-dialer#call_ringing
Delete contact gives response as "Contact shared_contact_pool_Company:{{companyId}}_uid_{{uid}} not found cannot be accessed due to insufficient permissions."
I am trying to delete the shared contact by passing id - sharedcontact_pool_Company:{{companyId}}_uid{{uid}}.
Websocket refresh
I notice that when you refresh a websocket the URL changes. In dotnet the standard websocket client does not have this as a feature, so this means having to create a new web socket which in turn means adding complicated logic in order to make sure that you retire the previous socket correctly, don't process a message twice, and don't miss a message. Is there any other way to refresh the web socket without the URL changing?
Using keyboard to answer calls?
Hi, is there a way to use my keyboard or even a different app w/ different interface?
New colums added to users report
We noticed that new columns were added to User API response
Screenpop API error
I am making the following request to a sandbox account: