Hi!
On Apr 7, 2009, at 9:03 PM, Steven C. Blair wrote:
So I created this scenario but it still does not work.
Any thoughts
on what might be missing?
180? 183? BYE? looks odd in a SUBSCRIBE/NOTIFY scenario.
If the SUBSCRIBE was successful you'll receive a NOTIFY at some point.
You should absorb
that in order to prevent sipp from complaining about out of sequence
messages.
How about you take your favourite client, sniff some traffic (i.e.
ngrep -W byline ...) and
create the sipp XML file based on the traffic you actually see?
Hendrik