Hi,
has anybody managed to connect to Zoom with Kamailio, ideally using rtpengine?
I'm getting error 500 when I call them …
Hello,
I haven't heard there is any public SIP interconnect offered by Zoom, but I can't say I am familiar with the matter.
Cheers, Daniel
On 02.03.22 13:06, Matthias Urlichs wrote:
Hi,
has anybody managed to connect to Zoom with Kamailio, ideally using rtpengine?
I'm getting error 500 when I call them …
-- -- regards, -- -- Matthias Urlichs
Kamailio - Users Mailing List - Non Commercial Discussions
- sr-users@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
Hello,
I haven't heard there is any public SIP interconnect offered by Zoom,
Not "public", but they're offering traditional phone interconnect services. If you ask nicely you can get them to set up a BYOC link (Bring Your Own Carrier) which is basically encrypted SIP and RTP. Reportedly, the ability for customers to set up such interconnects via the admin webpage is in the works.
I've since figured out that the solution to my problem is to radically limit the crypto algorithms (offered to them *and* accepted from them) via SDP. Apparently there's a somewhat-hairy bug in their gateway's negotiation setup.
No usable reaction from Zoom support yet, let alone a fix that'd allow me to remove that hack; as usual for companies of that size and/or rate of growth, their front line support leaves much to be desired.
On 3/11/22 08:32, Matthias Urlichs wrote:
I've since figured out that the solution to my problem is to radically limit the crypto algorithms (offered to them *and* accepted from them) via SDP. Apparently there's a somewhat-hairy bug in their gateway's negotiation setup.
Sounds similar to five 9, cube, and some others...
Horrible rtpengine statements, such as: SDES-no-AES_CM_128_HMAC_SHA1_32 SDES-no-AES_192_CM_HMAC_SHA1_80 SDES-no-AES_192_CM_HMAC_SHA1_32 SDES-no-AES_192_CM_HMAC_SHA1_80 SDES-no-AES_256_CM_HMAC_SHA1_80 SDES-no-AES_256_CM_HMAC_SHA1_32 SDES-no-F8_128_HMAC_SHA1_80 SDES-no-F8_128_HMAC_SHA1_32 SDES-no-NULL_HMAC_SHA1_80 SDES-no-NULL_HMAC_SHA1_32
Fred Posner | palner.com Matrix: @fred:matrix.lod.com o: +1 (212) 937-7844
On 11.03.22 14:46, Fred Posner wrote:
Sounds similar to five 9, cube, and some others...
Yep. Exactly.
Worse, this also applies to incoming crypto. You offer to use X or Y, I accept X, you send an error 500 to the caller (*not* to me)? Nice. Very nice indeed.
Plus, if they ever stop advertising the not-exactly-high-grade algorithms that I've limited things to, our link will die – and whoever maintains the thing when I'm retired will have no idea what they should do about it.
-
Daniel-Constantin Mierla -
Fred Posner -
Matthias Urlichs