Re: [Sip-implementors] RFC ABNF grammar check for Truncated unrecognized header

On 2/8/19 2:43 AM, Rakesh wrote: Sorry typo. "ff" I mean. Since we are talking about HEX, ff & FF are the same. More below. BR/// Rakesh Kumar Mohanty On Fri, Feb 8, 2019 at 1:12 PM Rakesh > wrote: Hi Paul, Thank you very much. Another think I am th

Re: [Sip-implementors] RFC ABNF grammar check for Truncated unrecognized header

Sorry typo. "ff" I mean. BR/// Rakesh Kumar Mohanty On Fri, Feb 8, 2019 at 1:12 PM Rakesh wrote: > Hi Paul, > Thank you very much. > Another think I am thinking is FF is also not valid as per RFC 3261 it is > UTF-8 Character set. > Am I correct in understanding ? > > BR/// > > Rakesh Kumar Mo

Re: [Sip-implementors] RFC ABNF grammar check for Truncated unrecognized header

Hi Paul, Thank you very much. Another think I am thinking is FF is also not valid as per RFC 3261 it is UTF-8 Character set. Am I correct in understanding ? BR/// Rakesh Kumar Mohanty On Thu, Feb 7, 2019 at 11:07 PM Paul Kyzivat wrote: > Rakesh privately asked me why this doesn't conform to t

Re: [Sip-implementors] RFC ABNF grammar check for Truncated unrecognized header

Rakesh privately asked me why this doesn't conform to the ABNF of a sip message. I'm replying to the list for the benefit of others. Here is some of the relevant ABNF: SIP-message= Request / Response Request= Request-Line *( message-header ) CRL

Re: [Sip-implementors] RFC ABNF grammar check for Truncated unrecognized header

Rakesh writes: > Can I just know on INVITE request if I get the below characters then is it > OK as per ABNF grammar? Please note I am not asking about the header > rather I need to know the correctness of the character that has appeared on > INVITE request. Looking at the hex dump that you pro

Re: [Sip-implementors] RFC ABNF grammar check for Truncated unrecognized header

Rakesh, I still don't understand your question. What you show below appears to be garbage that happens to include a few fragments that resemble sip URIs. Did you receive this on a port where you expect to receive sip messages? If so, this clearly doesn't conform to the ABNF syntax of a sip me

Re: [Sip-implementors] RFC ABNF grammar check for Truncated unrecognized header

Hi, Further to add to the last this is what I am looking for the bold part *ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff * 0010 * ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff* 0020 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ÿÿÿ

[Sip-implementors] RFC ABNF grammar check for Truncated unrecognized header

Hi Expert, Can I just know on INVITE request if I get the below characters then is it OK as per ABNF grammar? Please note I am not asking about the header rather I need to know the correctness of the character that has appeared on INVITE request. [truncated]\377\377\377\377\377\377\377\377\377\