That's because you haven't used any multi-value headers there! Try a Via or a Contact header. That should cause those extra gears to kick in.
Best regards, Byron Campen Byron,
I tested with
To: <sip:12345@host>, <sip:6789@host2>
or
To: <sip:12345@host>
To: <sip:6789@host>
or
UnknownHeader: 123456789, abcdefg
No NFieldName, or NValue states have been used at all.
By the way, my resiprocate stack is compiled with RESIP_MSG_HEADER_SCANNER_DEBUG.
Regard,
Frank
On Fri, Apr 24, 2009 at 11:19 AM, Byron Campen <bcampen@xxxxxxxxxxxx> wrote: Ok, it looks like that FSM graph is missing some information; there are ways to transition from those single value states to the multi-value states. I am not convinced that these separate multi-value states are necessary. What good is it if the pre-parser rejects
To: sip:bob@foo, sip:joe@foo
When it cannot reject
To: sip:bob@foo To: sip:joe@foo
If you have code that deals with the latter (and we do, it lives in SipMessage), why should we deal with the former in the MsgHeaderScanner?
Best regards, Byron Campen
Hi Adam, How is State 7:ScanWhitespaceAfterNFieldName reached? Under what condition are NValue and NFieldName used? The graph is attached. Thanks Frank On Thu, Apr 23, 2009 at 11:22 AM, fuliang yuan <fuliangyuan@xxxxxxxxx> wrote: Hi Adam,
It works fine with GVedit.
Thanks a lot!
Frank On Thu, Apr 23, 2009 at 10:32 AM, Adam Roach <adam@xxxxxxxxxxx> wrote: fuliang yuan wrote: Hi,
I dumped MsgHeaderScanner FSM, but have no idea what tool should be used to convert it to diagraph.
Any help is appreciated.
http://www.graphviz.org/
/a
|