Hello
I have two sipp scrips representing alice and bob. When I start the alice
script, it registers to the SIP server, sends a SIP:MESSAGE to bob trough
the same sip server and then, when 200 OK is received, it unregisters from
the server. Bob will also register to the same SIP server, then it
Alice's message will have a different Call-ID than Bob's existing call.
Therefore the message will not be identified as part of the conversation.
You can use three or fou r SIPp instances for this to work.
1. Bob's Registration
2. Bob's Message Receive
3. Alice (or Alice's Registration and Send)
Hi,
I am running a sipp script in which sipp is receiving REGISTER, sending 200
OK, and receiving INVITE. When I am trying
to receive INVITE then sipp reports it as an unexpected message.
Can you please help on this.
The folowing Error occurs:
2007-04-26 18:05:15: Aborting call on
Ashok,
The REGISTER and INVITE will have different Call-IDs. To make this work
you need to use optional messages, so that either a register or an invite
can start a new scenario.
Charles
[EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
04/26/2007 08:31 AM
To
sipp-users@lists.sourceforge.net
I have loaded the latest sipp version and found an
extra comma in the 2nd via header when use [Last_Via]
handle the short form message. pl check the 180
Ringing message below.
Thanks,
Joseph
2007-04-17 15:11 oboulkroune
* call.cpp, call.hpp: Fix: updated support of short
header forms - provided
curl-loader version 0.30 released.
curl-loader now officially supports 10K and more simultaneously
loading HTTP clients
in hyper mode (commandline option -m0).
For more info about this open-source project, please, look at:
http://curl-loader.sourceforge.net/
--
Sincerely,
Robert
Joseph,
Can you try the attached patch?
Charles
[EMAIL PROTECTED] wrote on 04/26/2007 03:57:07 PM:
I have loaded the latest sipp version and found an
extra comma in the 2nd via header when use [Last_Via]
handle the short form message. pl check the 180
Ringing message below.
Thanks,
