11 Mar
2022
11 Mar
'22
4:46 p.m.
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