Note: Talkdesk can only provide best-efforts support and is not responsible for configuring your specific SIP devices. Since there are so many permutations and models, we are unable to provide guidelines that work seamlessly with all devices. We are also unable to configure or provide details that are specific to your network. However, if you need a more detailed SIP setup, we will be happy to assist you and provide all required information to your network team. Learn more about SIP clients: Networking Details.
SIP phones can be a part of your Talkdesk solution; however, please bear in mind that features and functionalities are limited at this time, once calls are forwarded to a SIP endpoint.
SIP will need to be activated for your account by e-mailing us at: email@example.com.
Once SIP has been enabled and a SIP phone has been configured, you can allow SIP as a device through your account’s Device Settings.
Obtaining Agent’s SIP Credentials for use with SIP Phone
Each agent has their own set of SIP credentials. Agents can access this information by clicking their names in the top-right corner and selecting “Agent Profile” from the drop-down menu:
They should then click the 'Request SIP Credentials' button to receive an email with a link to their SIP credentials:
Note: This link has an expiration period of 10 minutes or one visit.
In case they don't have these permissions, these will need to be provided by an account Admin by accessing the Agents tab, selecting each agent's name and then clicking the 'Request SIP Credentials' button:
An email will be sent to the Admin with a link providing access to the agent's SIP credentials.
Keep this information open to configure the SIP software:
In some SIP phone configurations you might be asked for the Auth ID or the User ID, which in the above image is the username that comes before the @ character.
The SIP Domain is also required, in which case it should be specified as “phone.plivo.com” (the text that comes after the @ character).
General SIP Phone Settings
While we can’t provide a guide to all SIP Phones, there is a set of settings that are normally available across all phones, which is recommended to configure in order to ensure great call quality.
|RTP Packet Size||0.020|
|SIP Transport||TCP (If TCP doesn't work you can try UDP)|
|Preferred Codec||G711u (ensure this is top the of list)|
|Second Preferred Codec||Unspecified|
|Third Preferred Codec||Unspecified|
|Use Remote Pref Codec||Yes|
|Set all codecs||no|
|Use Auth ID||yes|
Using the SIP Phone
Once the SIP software has been configured with the Agents’ SIP endpoints, agents can start receiving calls. To do so, they must have the SIP software opened and be logged in to their Talkdesk Account, with status set to "Available."
When an incoming call comes through, Talkdesk notifies the agents that they need to answer the call on their SIP phone.
Their SIP hardware or software phone will start ringing at the same time.
SIP functionality is limited to our Main web application and Callbar and is not available with our CTI Widgets.
Caller ID will only display the phone number of the caller, not a caller's name.
Also note that for inbound calls, when using the SIP endpoint ID in more than one device (SIP, Bria etc.), the system will randomly pick a device to ring.
Outbound calls using SIP need to be initiated directly from the SIP phones.
It is not possible to initiate an outbound call from a SIP phone from within Talkdesk. This means agents can’t initiate the call in the browser and have the SIP device make that call, since the call button that appears in the contacts list will not work.
Once the call has been connected on the SIP phone, agents will see the call information in the Talkdesk Keypad in the main web application. They can then mute the call, put it on hold, transfer, or add a guest using the browser.
Ending SIP calls must be done directly in the SIP phone, not in Talkdesk:
It is not possible to transfer SIP calls from your SIP device. This can only be done if you are logged in to Talkdesk in the browser.
If the call summary window is not closed in the browser (which will pop in the backend), incoming calls may not come through.