Hi guys,
I'm testing your W52P with latest firmware and I've found an issue on SIP INFO implementation.
According to RFC 2327 (SDP) :
Text records such as the session name and information are bytes
strings which may contain any byte with the exceptions of 0x00 (Nul),
0x0a (ASCII newline) and 0x0d (ASCII carriage return). The sequence
CRLF (0x0d0a) is used to end a record, although parsers should be
tolerant and also accept records terminated with a single newline
character.
If I send a SIP INFO with a DTMF tone from W52P I have:
Signal=4\r\n
Duration=100
While should be
Signal=4\r\n
Duration=100\r\n
My PBX (based on Freeswitch) answer with Bad Request!
Is it possible to have a firmware that fix it?
Thank you
I'm testing your W52P with latest firmware and I've found an issue on SIP INFO implementation.
According to RFC 2327 (SDP) :
Text records such as the session name and information are bytes
strings which may contain any byte with the exceptions of 0x00 (Nul),
0x0a (ASCII newline) and 0x0d (ASCII carriage return). The sequence
CRLF (0x0d0a) is used to end a record, although parsers should be
tolerant and also accept records terminated with a single newline
character.
If I send a SIP INFO with a DTMF tone from W52P I have:
Signal=4\r\n
Duration=100
While should be
Signal=4\r\n
Duration=100\r\n
My PBX (based on Freeswitch) answer with Bad Request!
Is it possible to have a firmware that fix it?
Thank you