Forgot to include sipp-users...
Thanks,
Vui
Vui Vui <[EMAIL PROTECTED]> wrote:
Date: Fri, 25 Apr 2008 13:12:39 -0700 (PDT)
From: Vui Vui <[EMAIL PROTECTED]>
Subject: Re: [Sipp-users] Support for multiple call-ids within a single scenario
To: Charles P Wright <[EMAIL PROTECTED]>
Hi Charles,
II'm also trying to look for a solution for this multiple call-ids in the
same scenario issue. I'm kind of new to SIPp and I'm not quite clear about your
suggestion, please forgive me if I'm asking questions which other people might
have asked already.
I'm currently trying to test SIP TLS with SIPp and I've already got the
following scenarios to work:
sipp uac ----(tls)---- sipp uas
sipp register ---- (tls) ---- sip proxy
sipp uac ----(tls)---- sip proxy ----(udp) sipp uas
However, I'm having a problem with the scenario below:
sipp uac----(tls)----sip proxy----(tls)----sipp uas
The scenario failed at the point when the sip proxy tried to forward the
INVITE to sipp uas, it initiated the handshake process with sipp uas and
although I didn't see any error, the sip proxy just replied sipp uac with error
408 and did not forward the INVITE. Please see my wireshark capture, topology,
uac xml, uas xml and trace logs here
http://www.aic-cia.net/nhiepanh/sipp_tls.zip). Please also note that prior to
running the uas scenario on endpoint2, I ran the register (TLS) scenario to
register endpoint2 with my sip proxy and there was no problem there so all the
keys & certificates are ok.
I'm thinking since the TLS registration scenario works, if I can somehow
combine the register & invite in the same uas scenario, the registration will
establish the TLS connection between uas and the sip proxy. When the INVITE
comes, my sip proxy won't have to initiate the handshake with my uas and then I
might get this solution to work
My questions to you are:
1. Will the prefix///call-id solution work for my above scenario?
2. If not, what do you mean by extending SIPp?
Thanks,
Vui
Charles P Wright <[EMAIL PROTECTED]> wrote:
If you can generate the call-IDs yourself, then you can do something of
the format: prefix///call-id and prefix1///call-id and SIPp will treat
them as the same scenario. Otherwise, you would need to extend SIPp.
Charles
"Philip Campion"
Sent by: [EMAIL PROTECTED]
04/25/2008 08:47 AM
To
cc
Subject
[Sipp-users] Support for multiple call-ids within a single scenario
Hi,
My team is using a SIPp process to generate single call tests. At this
point we're less interested in the traffic capabilities of SIPp, but we do
need ways to generate more complex call models. While 3PCC is one way to
add complexity, we really need to support multiple call-id's within a
single scenario, to simulate events like call waiting. We were wondering
if anyone can suggest how this can be done.
Many thanks,
Philip
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Sipp-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sipp-users
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Sipp-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sipp-users
---------------------------------
Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now.
---------------------------------
Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now.-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Sipp-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sipp-users
