I am experiencing issues with the createSIPRegistration
API when attempting to register a SIP device using the following endpoint: createSIPRegistration API.
Issue Details:
-
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" }
-
-
Error when not passing
device.id
and settingsipInfo.transport
as TCP or TLS:-
Response:
503 Service Unavailable
.
-
-
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" } ] }
-
-
Working case:
-
When using
WSS
assipInfo.transport
, the registration succeeds. -
However, my third-party service (LiveKit) only supports
TCP
,TLS
, andUDP
.
-
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:
-
How can I change my device type to ensure compatibility with Web-based SIP registration?
-
Is there a specific configuration required to use
TCP
,TLS
, orUDP
transport successfully? -
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!