After successfull JWT authorization for Client ID 5kbWr8Q48FFbdt4wl2f6q4 (Avaya Cloud Office - Sandbox - RingCentral Softphone Demo CSharp), the first Rest API call "SipProvision" fails w/ error message "SPR-112 Client Edition is not compatible with current Brand". The app setting is configured as "public" and NOT limited to brand "Avaya Cloud Office". As authorization method is JWT, I have no idea how to configure brandid 6010 inside C# program code. 
Please note: Auth via "Password" is no longer supported. Furthermore we're going to build a server-side app (Windows Service in C#), that's why rc.Authorize is called w/ JWT.
Client ID for this app in Avaya Cloud Office sandbox is: 5kbWr8Q48FFbdt4wl2f6q4
The app is configured as public w/o any limitation/restriction on specific brand.
Hi @Phong Vu and @Tyler Liu ,
yesterday, Karsten was so kind to help me to get "SIP over TCP and RTP" up and running on my ACO instance and for my user extension & SIP device by implementing "List extensions, Get Extension ID, Get Device SIP Info" - it works!
Sorry for the confusion, it was my oversight, because the limitation of API call "Device SIP Registration" on WebPhone, Mobile, Softphone" is described and visible on top of the page.
So may I assume, that "List extensions, Get Extension ID, Get Device SIP Info" can be used and is supported like all other APIs functions on "developers.ringcentral.com/api-reference"?
Appreciate your support (and final answer:)
Brgds & Thx, Ralf
"Get Device SIP Info" is available in RingCentral's public documentation/API reference, so yes you can use it and it is supported.
Hello @Phong Vu and @Tyler Liu: I looked at the project a bit further. I have got the RingCentral.net Softphone project to work. I have used Get Device Sip Info api call to get the SIP information from an "existing phone" and use these details in the c# project instead of using Create SIP Registration. This would allow a external app to registered as a SIP endpoint programmaticly using SIP TCP.
This Get Device SIP Info API call is used widely for 3rd party devices that are not on the offical hardware phone list of RingCentral. Could you confirm if the API call Get Device Sip Info is fully supported for Ralf?
Interesting. Thanks for sharing this Karsten! Let's have a deep look at this and come up with a solution if possible. @Ralf Reifenberg please stay tuned.
if you are talking about "SIP over TCP + RTP", as we confirmed with project manager, it is not a feature that should be open to public. Only some RingCentral apps could use this feature. Third party apps should use SIP over WSS instead. For now it is by design. In the past it used to work but now it doesn't work any more. And since by design it is for internal usage only, we may not provide any fix in the near future.
Can you try to create a JWT token bound to this app (NOT all app under my organization)? And use that JWT token instead. Also, you can narrow down the investigation area by changing the app from public to private.
For brand configuration, you don't have to set anything from the SDK, it's just the app settings.
Hi Phong Vu,
appreciate your efforts! Unfortunatelty the behaviour hasn't changed, same result in Visual Studio project RingCentral Softphone Demo and on RingCentral web sites using "Try Out". I'm not able to execute "Device SIP Register" for any other protocol than WSS. For this test, I tool the "ACO Sandbox Germany" RingCentral App "API Ringout", which was already created in June 2021 and which has User/Pwd auth configured:
It works for WSS, but our Windows server application/service requires JWT, so this doesn't help.
I'm getting SPR-112 for TCP protocol, same for UDP and TLS.
I got a confirmation from the platform team that TCP transport is only supported for RC apps. Thus, 3rd party can only use WSS transport method.
We will add a note to the API reference later to make it clear.
Let me setup my environment and investigate this. I have not used this before so it may take some time.
Hi Phong Vu,
I've tried all combinations in sandbox environment of ACO account "Avaya Germany Sandbox" (main number +14244275013 ):
App JWT JWT Auth - Error Msg
-----------------------------------------------------------------------------
private private OAU-153 - invalid client
private public OAU-153 - invalid client
public private SPR-112 - client edition not compatible w/ current brand
public public SPR-112 - client edition not compatible w/ current brand
Avaya private SPR-112 - client edition not compatible w/ current brand
Avaya public SPR-112 - client edition not compatible w/ current brand
Note: "Avaya" = public app limited to brand Avaya Cloud Office and all other Service & Brand partners.
I've checked w/ SIP test client "PhonerLite" (similar to ZoiPer), that my extension works. And I've found an old app in "Avaya Germany Sandbox" created in June 2021, which is configured to allow "User+Pwd" authentication. Unfortunately I do NOT have a JWT dated June 2021 (because I joined "ACO Sandbox Germany" recently) ... RingCentral Softphone Demo also returns SPR-112 error when using "User+Pwd" in combination w/ newly created JWT token of type "all applications".
Hmm ... no idea what to try next ...
Hi Phong,
as RingCentral.Softphone.Net is original RC code
- which did work in the past
- which is designed for (and worked for) "creation of SIP device using SIP over TCP + RTP" (see program.cs lines 30 - 48)
- which worked for "user/pwd", until this auth method became deprecated and blocked (and maybe in same timeframe, PCKE became introduced)
could you please double-check, whether TCP transport is really only supported for RC apps?
This morning, I've had support from Karsten Domaratius and he was able to reproduce SPR-112. Karsten is just investigating, whether SPR-112 will appear for a RingCentral app/user too.
@Tyler Liu Can you have a look at this? Thanks
Ok, maybe the issue is here:
- in sandbox environment of "ACO Sandbox Germany"
- the first API call "Device SIP Register" "https://platform.devtest.ringcentral.com/restapi/v1.0/client-info/sip-provision" does NEITHER work for "TLS" nor "TCP protocol for extension 101 in case of JWT
- the "Device SIP Register" only works for extn 101 and an App w/ OAuth2 and WSS protocol
- but that doesn't help at all, both OAuth2 and WSS are wrong for the Windows service we have to implement based on JWT
If I try an App w/ JWT and select "TLS" protocol. then I receive "SPR-117 Server does not support protocol"
How to get out of this chicken-egg problem for extn 101 on "ACO Sandbox Germany"?
- "User/Pwd" auth is no longer possible - OK
- 3-leg OAuth2 is wrong for Windows service w/o UI
- JWT doesn't work for TLS and ext 101 in "ACO Sandbox Germany" .. I still haven't understood why ...
Before I look into the problem, I want you to double check if the problem is with the JWT or not. I enable password flow for your app. So can you try authenticate your app with 101 username and password and register the SIP device.
Let me know the result.
A new Community is coming to RingCentral!
Posts are currently read-only as we transition into our new platform.We thank you for your patience
during this downtime.
Try Workflow Builder
Did you know you can easily automate tasks like responding to SMS, team messages, and more? Plus it's included with RingCentral Video and RingEX plans!Try RingCentral Workflow Builder
