...
| Table of Contents | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Overview
Sangoma Talk is a mobile client that supports Android and iOS mobile devices. The client is provisioned automatically based on a deep link URL, and access is granted to users entirely within the PBX User Management Module. The client maintains contact with the Sangoma Talk push servers and the PBX. Both the push servers and the Sangoma Talk client will register directly to the PBX using SIP registration via the public IP address of the PBX. When the client is active the registration will come directly from the mobile device. When the client is in standby, registration will come from a push server. It is necessary, therefore for the PBX to allow inbound SIP registrations from the internet, and also necessary for the extensions to support multiple active registrations.
...
| Note |
|---|
This list of IPs is in addition to the responsive firewall used to protect against bad actors on other IP addresses. This address list is subject to change , you without notice. One can confirm the current address list of push servers at any time by getting all A records from the FQDN "all.sipis.acrobits.cz" |
| Code Block |
|---|
all.sipis.acrobits.cz
159.65.167.207
159.65.186.176
159.65.251.173
159.65.252.186
159.65.253.49
159.89.179.103
162.243.226.164
165.227.65.164
165.227.115.186
165.227.182.9
165.227.184.188
165.227.190.186
165.227.210.221
165.227.223.68
167.99.48.91
167.99.119.203
167.99.119.244
159.203.120.54 |
The call media uses the RTP port range as defined in Asterisk SIP Settings, (default is 10000-20000).
...
Misconfiguration of the NAT settings.
Lack of forwarding rule for the entire RTP range at the NAT router.
Firewall Settings for Sangoma Talk Applications
Please ensure to whitelist “159.203.120.54” IP in your internal or external firewall in order to allow Talk applications like Visual Voicemails to work properly.
Changing SIP Credentials
If you change the SIP credentials for a user with an existing Sangoma Talk registration (PJSIP username and/or PJSIP secret) you will need to reprovision the Sangoma Talk Client. Browse to User Management and send a new email invitation to the user. The user will view the email on their mobile device and follow instructions to reprovision the client.
...
The contacts that are included in the Talk app include the PBX's internal extensions as seen in User Management. A user's globally recognized avatar from Gravatar is automatically displayed.
...
Let us assume you have an existing chan_sip extension number 1100 and an existing User Management user with name 1100. You will not touch the settings on either of these except for Follow Me.
Create a new dummy Extension and User. There are no requirements for the extension and user number/name, but it's conventional for the dummy to be the same as the primary with a prefix. In this case we'll create a pjsip extension and user of 881100
Edit the new extension 881100 and click the 'advanced' tab. Locate the 'mailbox' field and change it to match the primary extension, in this case '1100@device'.
On this same tab, locate the “CID Num Alias” field and change it to 1100 so that local calls from 881100 appear to come from the primary extension number.
If voicemail was enabled as part of the create process, disable it now on the voicemail tab.
On the General tab, Set Outbound CID and Emergency CID to match primary extension.
Submit changes to extension 881100
Browse to Applications, Follow Me and edit the primary extension, 1100
Enable FMFM with a ring strategy of 'ringall' and a follow-me list that includes the primary extension and the dummy extension, 1100 and 881100. If you wish to add mobile numbers to this list, you can do so. Make the Destination if no answer be 'Follow Me - normal expected behavior'
submit FMFM page
Browse to Admin, User Management and edit the new user 881100
Ensure that this user has an email address set correctly.
Enable Sangoma Talk and submit
Apply config
Edit the user again and on the Sangoma Talk tab click the button to send invite.
You can now follow the directions for a normal Sangoma Talk install. The user should receive an email with Sangoma Talk client config instructions. Calls to extension 1100 should immediately ring both extension 1100 and the 881100 Sangoma Talk client. Calls from the Sangoma Talk client should appear to come from extension 1100. When dialing *97 or *98 from the Sangoma Talk client, you will prompted to enter a mailbox number and pin, and from there check voicemail.
Caveats
As noted above, this is not the preferred setup for Sangoma Talk. Calls made from Sangoma Talk will appear to come from the primary extension, but rules in place for things like Class of Service, Extension Routing must be updated to accommodate the new extension number. Things like Ring Groups and Queues need to be configured to either respect the FMFM settings or the new dummy extension must be added to them so the Sangoma Talk client will ring. Certain aspects of third party tools like XactView and iSymphony may not work at all since they make the assumption that the extension number dialing matches the Caller ID.
Talk Mobile Diagram
...