SRAPS (Secure Redirection and Provisioning Service) is a new Snom Service built to replace and enhance the legacy Redirection Service (RDS).

SRAPS will provide all the base functionalities of RDS ( XML-RPC API and Redirection management) plus more features as:

  • End-to-end security: SRAPS uses only TLS for the provisioning requests, with full TLS Client Authentication, ensuring end-to-end security.
  • Web interface
  • Auto-provisioning: Create your provisioning profiles easily via the SRAPS portal interface and deploy them to your Snom phones
  • Remote XML-RPC API available to all customers
  • Two tier hierarchy: Distributors, Resellers and Enterprise organizations may perform hierarchical Company management, including Sub-Domains, Users, and Configuration Management ( to be implemented )

If you are using the legacy Snom Redirection Service you are invited to signup to the new SRAPS, please after carefully reading this page.

Supported phone models

Desktop Phones

  • snomD120 (*)
  • snom300
  • snom320
  • snom360
  • snom370
  • snom820
  • snom821
  • snom870
  • snom710
  • snomD712
  • snom715
  • snom720
  • snom725
  • snomD745
  • snom760
  • snomD765
  • snomD785 (*)
  • snomD305
  • snomD315
  • snomD345
  • snomD375
  • snomD385 (*)

  • snomMP
  • snomC520 (*)

  • snomM300
  • snomM700
  • snomM200SC (*)
  • snomM400SC (*)
Industrial Applications

  • snomPA1

(*) The device already points to SRAPS ( ), this device isn't supported by the legacy RDS, in case you want to manage the redirection for that model you need an account on SRAPS where you can add the redirection trough the XML-RPC APIs. If you are using the Python CLI you should use the SRAPS version of the CLI in order to manage those devices.

Devices not marked with (*) are still pointing to the legacy RDS until the migration is completed (see above). In order to manage the redirection for those devices currently you need an RDS account. In case you are using the Python CLI you should use the legacy CLI.


Release 1:

  • Web portal for signup and account of the same company invitation
  • XML-RPC API for endpoint management (redirection)

Status: released in production

Release 2:

  • Endpoint management from the Web portal:
  • Add new endpoints
  • Create provisioning profiles (setting_server only)
  • Show list of endpoints (phone types, MACs, redirection URL)
  • Release / delete an endpoint from SRAPS

       Status: released in production

Migration Plan

As we know this service is crucial to your operation, the migration from one service to another has to be as smooth as possible. In the first phase both RDS and SRAPS will run in parallel, when everything is settled we will migrate all the data and the service will be replaced.

The following table describes the migration steps planned, please read it carefully and check with Customer Action column if you are aligned with every step and deadline:

IMPORTANT NOTE: The planned date for the migration is July 6th 2018

A minimum firmware version must be installed to ensure an error-free operation with SRAPS:

Snom Desk phones (except Snom 360)
MeetingPoint and PA1
Snom 360
DECT M300 and M700
v355B25 or >=410B03/B04

After the migration the old Redirection Service will shut down and not be in use any more. All data which remains on the server will be deleted in the next few months and no longer available.

Customer Action
From: March 01
To: -
Phase 1:
SRAPS Signup
Please go to and sign up for an user account on the new service. You will be asked to sign the terms and conditions, after which your account will be approved to use the new service.

NOTE 1: The first user of a company to sign up is automatically the company's admin user. He or she will be able to invite colleagues to join SRAPS per invitation email via the web portal.
NOTE 2: During the signup process you can select to subscribe the SRAPS newsletter: is strongly suggested to select such option, so you will be updated about maintenance and downtimes.

You may already manage the redirection of D120, D785, D385, M200SC, C520 with your XMLRPC interface, using as the server URL for your requests (the trailing slash ("/") is mandatory.)

Please make sure the HTTP header of your XML-RPC requests contain the Content-type: text/xml.
Since HTTPS provisioning requests to SRAPS must be secured by a proper client certificate, you can get now the redirection URL target using the new XML-RPC method redirect.getPhoneRedirection(mac). Every provisioning request without a proper TLS certificate will be rejected.
Signup on SRAPS:
From: March 19
To: April 20
Phase 2:
Migration Preparation
On SRAPS portal, we will provide a small input form, where we will ask you to provide your legacy RDS username and password. With these credentials, we will perform an authentication check against RDS, and after success we will store ONLY the RDS username into the SRAPS data base.
With this process we ensure that we migrate the MAC addresses on RDS to the correct user on SRAPS.

NOTE: This step is mandatory to allow the migration of your MACs from the legacy redirection service. If you don't link your legacy account we will not able to migrate your data.
Insert the legacy RDS credentials on the SRAPS portal, deadline: April 20
From: March 27

Phase 3: 
Legacy RDS Signup Freeze
Starting with this phase we will not accept new subscriptions for the legacy Redirection Service. Customers who already signed up can still work on the system with no issues: managing devices redirections will be working as usual
Make sure that all your phones using the redirection service fulfill the minimum fw requirements
From: July 6
To: July 6
Phase 4: 
Data Migration and services switch
We will migrate the database from legacy RDS to SRAPS, and after that we'll change the DNS entry of to our new SRAPS server. During this day, the service will be unreachable. Please inform your customers in advance.

Operations will start at 10:00AM (CET), starting at this time both SRAPS and the legacy RDS systems will not be accessible.

We expect a downtime until 16:00 (CET), a communication will follow when the system will be back online.

NOTE: this downtime will affect only new deployment and factory defaulted phones. Already installed / deployed devices will be still operational without any issue.

After these changes all phones with as their factory default setting server will be routed to SRAPS automatically. You may continue to use your XMLRPC interface with the same server URL for your requests, or you change it to the trailing slash ("/") is mandatory.


Q: What will change from the legacy RDS ?

A: All the RDS functionalities will be provided by SRAPS without any substantial difference. The major change is how to get the redirection target of a mac address: since HTTPS provisioning requests to SRAPS must be secured by a proper client certificate, you can get now the redirection URL target using the new XML-RPC method redirect.getPhoneRedirection(mac), the API call is documented on the wiki. Every provisioning request without a proper TLS certificate will be rejected.

Q: Is the Python CLI still available for SRAPS ?

A: Yes, on the wiki page we published a SRAPS version of the python CLI

Q: Are the Snom M3, Snom Vision and all the other old devices not mentioned on the table above manageable via SRAPS ?

A: No, those devices are not supported anymore and cannot be handled by SRAPS. Only devices listed on the table can be managed by SRAPS.

Q: What should I do after the migration to SRAPS ?

A: You should make sure to have updated all your systems using the XML-RPC API in order to use the new SRAPS credentials. Then all the functionalities of the legacy RDS will be available on SRAPS.

Q: Is the Legacy Redirection Server still working until the migration date ?
A: Yes: the RDS will be still working until the data migration process doesn't start

Q: I bought a Snom D785 and I want to add a redirection, what should I do before and after the migration ?

A: You can manage the redirection for the new devices (D785, D120, C520, M200SC) directly on SRAPS using the XML-RPC API or via the provided CLI. After the data migration you can still use SRAPS

Q: Will the IP address of change after the migration to SRAPS ?

A: Not the IP address of will remain the same after the migration


For any questions about SRAPS and the migration please contact us by sending an email to

Document Changes

  • June 26, 2018: new migration date defined
  • April 25, 2018: migration postponed to a date to be defined
  • April 06, 2018: postponed the migration date from April 10 to April 26
  • March 16, 2018: first publish of the document