On 15.12.22 at 14:39 Asterisk Development Team wrote:
# [ASTERISK-30032 <https://issues.asterisk.org/jira/browse/ASTERISK-30032>] -
Support of mediasec SIP headers and SDP attributes
(Reported by Maximilian Fridrich)
Hi Maximilian,
thanks for adding Mediasec support to asterisk! Unfortunately somewhat late - at
least regarding Deutsche Telekom consumer infrastructure. Telekom started quite
some time ago dropping the Mediasec requirement for their SIP servers. The new SIP
servers like
[city]-l01-mav-pc-rt-001.edns.t-ipnet.de
don't need any Mediasec headers any more. Those servers are meanwhile often the
primary ones provided by the SRV lookup (if they already exist for the location
you are requesting for).
But the old ones, which are still provided currently with lower priority, still
need it. Therefore it is necessary to enable Mediasec nevertheless to be able to
change to them if necessary. Does your patch work, too, if a server doesn't answer
the Mediasec request?
Another question:
Do you maybe plan to get asterisk ready to cope with 3 completely independent SIP
servers provided by the SRV lookup? Currently, asterisk can't handle it (it must
be ensured that all subsequent requests after the register must use the same
server previously registered to and not any other server of the list. Before
switching to another server, it's necessary to unregister the current active
server and afterwards register to the new one).
Thanks
Michael
--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-dev
