From http://sipp.sourceforge.net/doc/reference.html
A call_id identifies a call and is generated by SIPp for each new call. *In
client mode, it is mandatory to use the value generated by SIPp in the
"Call-ID" header.* Otherwise, SIPp will not recognise the answer to the
message sent as being part of an existing call.
Note: [call_id] can be pre-pended with an arbitrary string using '///'.
Example: Call-ID: ABCDEFGHIJ///[call_id] - it will still be recognized by
SIPp as part of the same call.
On 6/25/07, Edward Russell <[EMAIL PROTECTED]> wrote:
I have a scenario in which I want to send a message with one call id and
later receive a message with a different call id. This is for SMS
MESSAGEs. The first sent SIP MESSAGE contains an SMS-Submit in the content
and then I receive a 202 response. Then I need to receive a SIP MESSAGE
(containing an SMS-Submit-Report) in the same scenario. But the received
message (from a SIP Protocol point of view) is a new request (almost like a
new INVITE) and therefore has a new call id.
SIPP drops the received message because its not part of the original
call. Has anyone monkeyed with the code to do this?
Scenario attached.
Thanks,
Ed
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Sipp-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sipp-users
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Sipp-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sipp-users
