Re: [reSIProcate-users] a question about Accept-Contact

[Scott Godin <sgodin@xxxxxxxxxxxxxxx>]

There was a bug in the stack NameAddr parser if a * contact contained parameters.  I'll commit a fix.

Thanks,

Scott

On Fri, Dec 25, 2009 at 10:13 PM, 吴振宇 <ssosun@xxxxxxxxx> wrote:

I use the sipp tool to send a invite message to the stack wich has a
Accept-Contact header.
the header is:
Accept-Contact:*;+g.poc.talkburst;require;explicit

i have get the rfc3841 abnf as follow:
Accept-Contact  =  ("Accept-Contact" / "a") HCOLON ac-value
                     *(COMMA ac-value)
  Reject-Contact  =  ("Reject-Contact" / "j") HCOLON rc-value
                     *(COMMA rc-value)
  ac-value        =  "*" *(SEMI ac-params)
  rc-value        =  "*" *(SEMI rc-params)
  ac-params       =  feature-param / req-param
                        / explicit-param / generic-param
                      ;;feature param from RFC 3840
                      ;;generic-param from RFC 3261
  rc-params       =  feature-param / generic-param
  req-param       =  "require"
  explicit-param  =  "explicit"

i think the header i use is true,but the stack give the follow information:

DEBUG | 20091222-151245.213 | sipserver | RESIP | 1095485760 |
../stacks/resiprocate/rutil/BaseException.cxx:17 | BaseException at
../stacks/resiprocate/rutil/ParseBuffer.cxx:951
../stacks/resiprocate/rutil/ParseBuffer.cxx:951, Parse failed
unexpected eof in context: Accept-Contact

is it a bug or what other?
_______________________________________________
resiprocate-users mailing list
resiprocate-users@xxxxxxxxxxxxxxx
List Archive: http://list.resiprocate.org/archive/resiprocate-users/