Hi,
I am testing the following scenario using Sipp:
sipp UAC--- SIP SBC SIP UAS
SIP SBC does interworking between SIP-SIP.
1. UAC will send Invite
2. SIP SBC will forward this Invite to UAS
3. UAS will send 183 with SDP.
4. SIP SBC will send PRACK to 183.
5. UAS will send
Hi Charles,
I for one am certainly interested in these changes. There are a lot
of
them that are generally useful (e.g., your performance improvements),
and
also applicable to any interested in user-model based-benchmarking.
Glad to hear you're sharing that point of view.
The biggest
You cannot send with retrans unless you next wait on receive. So you need
to move the retrans to the 200OK for INVITE.
Peter
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Girish
Gangaiah
Sent: 24 April 2007 18:19
To: sipp-users@lists.sourceforge.net
Hi David,
Verbeiren, David [EMAIL PROTECTED] wrote on 04/24/2007
04:35:10 PM:
The biggest logistical problem I see with this patchset is that there
has
probably been quite a bit of divergence of your tree and the SIPp tree
in
the meantime. For example, your network changes are going to
