SIP Mediaserver Service - Getting Started

At Your Side:

1. Generate API Keys

   Generate the API keys required to authenticate API calls with the iotcomms.io SIP Mediaserver Service. This will ensure secure access and functionality for all service interactions.

2. Firewall Configuration

   Open your firewall to allow HTTPS callbacks from the SIP Mediaserver Service. Callback URLs are specified during service provisioning, so ensure these URLs are accessible to avoid communication issues.

3. SIP Telephony System Configuration

   Configure your SIP telephony system to route calls to the SIP domain associated with your iotcomms.io tenant. This domain is where all inbound SIP requests will be processed by the SIP Mediaserver Service.

Provisioning the SIP Mediaserver Service:

1. Provision the SIP Mediaserver Service

   • Use the iotcomms.io web interface or the provisioning API to set up the SIP Mediaserver Service.

   • Configure the SIP address for the service and specify the HTTPS URL and authentication details for the service callbacks. These callback URLs will handle events, such as incoming calls, and trigger responses based on your application needs.

Testing the SIP Mediaserver Service:

1. Place a Test Call

   • Initiate a call to send a SIP INVITE request to the configured service SIP address. This will trigger a /newCall callback to your specified URL.

2. Verify in Developer Portal

   • Use the "Logs" view in the developer portal to confirm that the INVITE was received and that the /newCall callback was sent to the correct destination URL. This log view is essential for verifying successful configuration and troubleshooting any initial setup issues.

This setup ensures that the SIP Mediaserver Service is configured, operational, and ready to manage calls.