13 Oct
2020
13 Oct
'20
10:07 p.m.
Hmm, it's a tricky one, not sure actually.
https://tools.ietf.org/html/rfc3261#page-167
The answer might be in:
Even if the "display-name" is empty, the "name-addr" form MUST be
used
if the "addr-spec" contains a comma, semicolon, or question mark.
On Tue, Oct 13, 2020 at 3:39 PM Sergiu Pojoga <pojogas(a)gmail.com> wrote:
Aren't the Contact params supposed to be delimited
by semicolon?
On Tue, Oct 13, 2020 at 1:06 PM David VILLAUME <david.villaume(a)sewan.fr>
wrote:
Hello,
I see parsing errors on 302 contact header that seems compliant to RFC :
Contact:<sip:172.16.0.21:5060>;q=0.5,<sip:172.16.0.22:5060>;q=0.25
<core> [core/parser/parse_addr_spec.c:479]: parse_to_param(): invalid
character ',' in status 27: [;q=0.5]
Is there an error in my contact or is it truly a parsing error ?
Regards,
David
_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users(a)lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users