ProvisionVoiceAccountRequest response has old Vivox data inside
needs info
Glaznah Gassner
We are developing a voice support for SpeedLight (web SL viewer). The ProvisionVoiceAccountRequest cap request gives unexpected response.
The LLSD data being sent:
<llsd>
<map>
<key>jsep</key>
<map>
<key>type</key>
<string>offer</string>
<key>sdp</key>
<string>-a-lot-of-sdp-data-here-</string>
</map>
<key>parcel_local_id</key>
<integer>2</integer>
<key>channel_type</key>
<string>local</string>
<key>voice_server_type</key>
<string>webrtc</string>
</map>
</llsd>
According to https://wiki.secondlife.com/wiki/WebRTC_Voice the response contains jsep. Instead of expected
<key>jsep</key>
response we get old Vivox data:{"password":"...","username":"...","voice_account_server_name":"https://www.bhd.vivox.com/api2/","voice_sip_uri_hostname":"bhd.vivox.com"}
(dumped it as JSON)
Tried it both in webRTC1 and webRTC2. What may be a reason of missing webrtc response?
Log In
Signal Linden
needs info
Roxie Linden
That's odd, that should be correct. What's the exact URL you're sending the request too (including hostname, port, etc.?)
Have you attempted to implement the cross-region voice yet? If that's the case, you'll get vivox results back from the neighboring Vivox regions, which technically isn't optimal, but on the main grid we likely not end up in that situation given rollout plans.