Hello again.

I managed this morning to make it work, but I am not sure why it didn't
before.
What I did is simply copy another xml scenario file that I know was
working, and replace its content with my MESSAGE scenario. It worked.

As I didn't change anything from my previous tests, I can only assume that
While editing the xml file with wordpad, it ads some kind of weird content
that makes it not really well formed for SIPp to parse it. But I really
have no idea as I was able to launch the scenario, but it just didn't send
anything... If you have an idea, that might help others in the same case!

but in the end the MESSAGE scenario is working fine. Thanks a lot for your
help


--------------------------------------------------
Mathieu DAVY

> Mathieu,
>
> The scenario works for me.  I have attached  simple UAS responder to go
> with it (t2.xml).
>
> Charles
>
>
>
> "Mathieu DAVY" <[EMAIL PROTECTED]> wrote on 03/29/2007 05:02:45 AM:
>
>> Hello Charles, here is the extremely simple scenario I am using:
>>
>>
>> <?xml version="1.0" encoding="ISO-8859-1" ?>
>> <!DOCTYPE scenario SYSTEM "sipp.dtd">
>>
>> <scenario name="message to inaccess">
>> <!-- Send an instant message to inaccess -->
>>  <send>
>>     <![CDATA[
>>       MESSAGE sip:[EMAIL PROTECTED] SIP/2.0
>>       Via: SIP/2.0/TCP [local_ip]:[local_port];branch=[branch]
>>       Max-Forwards: 70
>>       To: <sip:[EMAIL PROTECTED]>
>>       From: <sip:[EMAIL PROTECTED]>;tag=[call_number]
>>       Call-ID: [call_id]
>>       CSeq: 1 MESSAGE
>>       Route: <sip:domain.com:5060;lr>,<sip:[EMAIL PROTECTED]:5060>
>>       Contact: <sip:[local_ip]:[local_port]>
>>       Content-Type: text/plain
>>       Content-Length: 0
>>
>>     ]]>
>>   </send>
>>
>>   <recv response="200">
>>   </recv>
>> </scenario>
>>
>>
>> I really don't see what is wrong in it. Would I not get a reply it would
>> make sense, but this message is not even sent! When running it, I get
> the
>> normal table display telling me the MESSAGE has been sent, but checking
>> with ethereal shows me that nothing comes out...
>>
>> thanks
>> --------------------------------------------------
>> Mathieu DAVY
>>
>> > We have been able to send MESSAGE messages, as far as I recall, there
> is
>> nothing special required.
>> >
>> > Charles
>> >
>> > [EMAIL PROTECTED] wrote on 03/28/2007 11:52:43
>> AM:
>> >
>> >> Hello everyone.
>> >> Is there any special requirement to be able to send SIP packets with
>> the MESSAGE
>> >> method?
>> >> I can't have it work under windows. I used the last win-install
> package
>> > and no
>> >> cygwin.
>> >> Checked with ethereal, no packet is even transmitted on the network.
>> Registration, publish and subscribe messages are working.
>> >> many thanks for your help
>> >> Mathieu Davy
>> >
> -------------------------------------------------------------------------
>> >> Take Surveys. Earn Cash. Influence the Future of IT
>> >> Join SourceForge.net's Techsay panel and you'll get the chance to
> share
>> > your
>> >> opinions on IT & business topics through brief surveys-and earn cash
>> >
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>> >> _______________________________________________
>> >> Sipp-users mailing list
>> >> [email protected]
>> >> https://lists.sourceforge.net/lists/listinfo/sipp-users
>> >
>>
>



-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Sipp-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sipp-users

Reply via email to