Re: [asterisk-dev] Asterisk 18.16.0-rc1 Now Available

On 21.12.22 at 16:53 Michael Maier wrote: On 21.12.22 at 15:52 Fridrich Maximilian wrote: I got it working now with [...] That is excellent news! I meanwhile sent Max some more information about missing things (like missing parameter information in pjsip show endpoint|registration and not

Re: [asterisk-dev] Asterisk 18.16.0-rc1 Now Available

On 21.12.22 at 15:52 Fridrich Maximilian wrote: I got it working now with [...] That is excellent news! But the remaining useless headers in Invite should be removed before the final release. I think this should be part of the documentation. I'm not a maintainer but I think usually the

Re: [asterisk-dev] Asterisk 18.16.0-rc1 Now Available

> I got it working now with [...] That is excellent news! > I think this should be part of the documentation. I'm not a maintainer but I think usually the documentation is kept quite general without describing specific use cases. The docs for the security_mechanisms parameter say "This is a

Re: [asterisk-dev] Asterisk 18.16.0-rc1 Now Available

On 21.12.22 at 09:17 Michael Maier wrote: On 21.12.22 at 08:21 Fridrich Maximilian wrote: Security-Client: sdes-srtp;mediasec ^ The ",mediasec" is missing. Yes, the security_mechanisms option is a comma separated list of the literal security_mechanisms that

Re: [asterisk-dev] Asterisk 18.16.0-rc1 Now Available

On 21.12.22 at 08:21 Fridrich Maximilian wrote: Security-Client: sdes-srtp;mediasec ^ The ",mediasec" is missing. Yes, the security_mechanisms option is a comma separated list of the literal security_mechanisms that should be used. I.e. you have to specify

Re: [asterisk-dev] Asterisk 18.16.0-rc1 Now Available

> Security-Client: sdes-srtp;mediasec > ^ > The ",mediasec" is missing. Yes, the security_mechanisms option is a comma separated list of the literal security_mechanisms that should be used. I.e. you have to specify

Re: [asterisk-dev] Asterisk 18.16.0-rc1 Now Available

On 20.12.22 at 17:10 Michael Maier wrote: Hello Max, On 20.12.22 at 11:29 Fridrich Maximilian wrote: Please let me know, if you are still experiencing issues with the new patch. I think the different headers are not addressed? Just tested it - doesn't work. It is fine for me if you don't

Re: [asterisk-dev] Asterisk 18.16.0-rc1 Now Available

Hello Max, On 20.12.22 at 11:29 Fridrich Maximilian wrote: Mr. Maier, Michael :-) thank you very much for your feedback! We provided this specifically for Telekom's "CompanyFlex" trunks which still require mediasec headers according to their website [1]. Specifically, we have to adhere to

Re: [asterisk-dev] Asterisk 18.16.0-rc1 Now Available

Mr. Maier, thank you very much for your feedback! We provided this specifically for Telekom's "CompanyFlex" trunks which still require mediasec headers according to their website [1]. Specifically, we have to adhere to their technical specification 1TR119 [2]. > Does your patch work, too, if a

Re: [asterisk-dev] Asterisk 18.16.0-rc1 Now Available

On 17.12.22 at 18:21 Michael Maier wrote: On 15.12.22 at 14:39 Asterisk Development Team wrote: # [ASTERISK-30032 ] -     Support of mediasec SIP headers and SDP attributes (Reported by Maximilian Fridrich) Hi Maximilian, today I

Re: [asterisk-dev] Asterisk 18.16.0-rc1 Now Available

On 15.12.22 at 14:39 Asterisk Development Team wrote: # [ASTERISK-30032 ] - Support of mediasec SIP headers and SDP attributes (Reported by Maximilian Fridrich) Hi Maximilian, thanks for adding Mediasec support to