I am experiencing issues with the createSIPRegistration API when attempting to register a SIP device using the following endpoint: createSIPRegistration API.

Issue Details:

1. Error when passing device.id in the request body:

   • Request fails with the following error:

   {
     "errorCode": "SPR-123",
     "message": "device is not allowed for Web.",
     "errors": [
       {
         "errorCode": "SPR-123",
         "message": "device is not allowed for Web.",
         "applicationType": "Web",
         "parameterName": "device"
       }
     ],
     "applicationType": "Web",
     "parameterName": "device"
   }

2. Error when not passing device.id and setting sipInfo.transport as TCP or TLS:

   • Response: 503 Service Unavailable.

3. Error when setting sipInfo.transport as UDP:

   • Request fails with the following error:

   {
     "errorCode": "SPR-112",
     "message": "Client edition is not compatible with current Brand",
     "errors": [
       {
         "errorCode": "SPR-112",
         "message": "Client edition is not compatible with current Brand"
       }
     ]
   }

4. Working case:

   • When using WSS as sipInfo.transport, the registration succeeds.

   • However, my third-party service (LiveKit) only supports TCP, TLS, and UDP.

Suspected Cause:

I believe these issues may be related to my device type, but I haven't found a way to modify or resolve the issue.

Questions & Assistance Needed:

1. How can I change my device type to ensure compatibility with Web-based SIP registration?

2. Is there a specific configuration required to use TCP, TLS, or UDP transport successfully?

3. Are there any restrictions on device compatibility that prevent using non-WSS transports?

Any guidance or suggested solutions would be greatly appreciated. Thank you for your support!