Actually I cannot even find this old version sipp.cumulus.2005-10-18.tar.gz.

On Wed, Jun 25, 2008 at 4:55 PM, Lucian Romi <[EMAIL PROTECTED]> wrote:

> Ooops! It's actually from an very old version. Is it also significant to
> merge?
>
>
> On Wed, Jun 25, 2008 at 4:46 PM, Charles P Wright <[EMAIL PROTECTED]>
> wrote:
>
>> You have to patch the current source code, but it would involve
>> significant reimplementation of the original patch.
>>
>> Charles
>>
>> "Lucian Romi" <[EMAIL PROTECTED]> wrote on 06/25/2008 07:12:53 PM:
>>
>> > Hi,
>> >
>> > I google and figure out that somebody actually implemented something
>> > call pre-scenario post-scenario to deal with this problem.
>> > Please follow this link
>> > http://osdir.com/ml/telephony.sipp.user/2006-09/msg00070.html
>> >
>> > Even I got the latest code from svn, the pre pos scenario is not
>> > there. Is there any other way to implement this with latest build or
>> > I have to patch the source code?
>> >
>>
>> > On Mon, Jun 23, 2008 at 11:36 AM, Lucian Romi <[EMAIL PROTECTED]>
>> wrote:
>> > Thanks Itzik and Charles.
>> >
>> > Looks like I have to use two different scenarios.
>> > Question are can I run these two scenarios into one sipp process?
>> > If not, can my REGISTER sender and INVITE server use the same source
>> > port to send messages?
>> > I need to do this because I'm inside the NAT.
>> > Thanks!
>> > On Sun, Jun 22, 2008 at 9:17 PM, Itzik Harel <[EMAIL PROTECTED]>
>> wrote:
>> > Charles
>> >
>> > If this is the case for Lucian, than you are correct about the need to
>> > use two separate scripts.
>> > I probably did not understood Lucian request properly.
>> >
>> > Regards, Itzik Harel.
>> >
>> > -----Original Message-----
>> > From: Charles P Wright [mailto:[EMAIL PROTECTED]
>> > Sent: Sunday, June 22, 2008 9:52 PM
>> > To: Itzik Harel
>> > Cc: Lucian Romi; sipp-users@lists.sourceforge.net;
>> > [EMAIL PROTECTED]
>> > Subject: Re: [Sipp-users] How to do REGISTER and UAS(INVITE server)
>> > together.
>> >
>> > Itzik,
>> >
>> > Your scenario has a single UAS that will handle either the REGISTER or
>> > INVITE.  I believe what Lucian wants to do is have a single scenario
>> > that sends the REGISTER every hour and listens for INVITES.  The first
>> > is possible (you did it), the second is not (it must be broken into two
>> > separate scenarios).
>> >
>> > Charles
>> >
>> > [EMAIL PROTECTED] wrote on 06/21/2008 11:42:34
>> > PM:
>> >
>> > > I did something once that does not require 2 scenarios.
>> > > Using labels, you can create different flow for Register and Invite
>> > > within the same scenario.
>> > > This will also support different call-id's for these methods.
>> > >
>> > > The script I have attached shows Register + handling Invite as a
>> > > redirect server, but I think you can integrate the Register and labels
>> >
>> > > portion into a basic UAS scenario.
>> > >
>> > > Good luck, Itzik.
>> > >
>> > > -----Original Message-----
>> > > From: [EMAIL PROTECTED]
>> > > [mailto:[EMAIL PROTECTED] On Behalf Of
>> Charles
>> >
>> > > P Wright
>> > > Sent: Sunday, June 22, 2008 12:18 AM
>> > > To: Lucian Romi
>> > > Cc: [EMAIL PROTECTED];
>> > > sipp-users@lists.sourceforge.net
>> > > Subject: Re: [Sipp-users] How to do REGISTER and UAS(INVITE server)
>> > > together.
>> > >
>> > > You need to use separate scenarios.
>> > >
>> > > Charles
>> > >
>> > >
>> > >
>> > >
>> > > "Lucian Romi" <[EMAIL PROTECTED]>
>> > > Sent by: [EMAIL PROTECTED]
>> > > 06/20/2008 07:06 PM
>> > >
>> > > To
>> > > sipp-users@lists.sourceforge.net
>> > > cc
>> > >
>> > > Subject
>> > > [Sipp-users] How to do REGISTER and UAS(INVITE server) together.
>> > >
>> > >
>> > >
>> > >
>> > >
>> > >
>> > > Hi,
>> > >
>> > > I tried to create one scenario like this. There are REGISTER and
>> > > INVITE server.
>> > > To make the server able to locate this UAS without expire, every 3600
>> > > second will send 1 REGISTER.
>> > > INVITE traffic is continusly sending from UAC, say 1 per second.
>> > >
>> > > Because REGISTER and INVITE server have different frequency and
>> > > Call-ID, anybody tell me how to do this scenario like this. Thanks!
>> > > ----------------------------------------------------------------------
>> > > --
>> > > -
>> > > Check out the new SourceForge.net Marketplace.
>> > > It's the best place to buy or sell services for just about anything
>> > > Open Source.
>> > > http://sourceforge.net/services/buy/index.php
>> > > _______________________________________________
>> > > Sipp-users mailing list
>> > > Sipp-users@lists.sourceforge.net
>> > > https://lists.sourceforge.net/lists/listinfo/sipp-users
>> > >
>> > >
>> > >
>> > > ----------------------------------------------------------------------
>> > > --
>> > > -
>> > > Check out the new SourceForge.net Marketplace.
>> > > It's the best place to buy or sell services for just about anything
>> > > Open Source.
>> > > http://sourceforge.net/services/buy/index.php
>> > > _______________________________________________
>> > > Sipp-users mailing list
>> > > Sipp-users@lists.sourceforge.net
>> > > https://lists.sourceforge.net/lists/listinfo/sipp-users
>> > > [attachment "redirect_sim.xml" deleted by Charles P Wright/Watson/IBM]
>> > >
>> > ------------------------------------------------------------------------
>> > -
>> > > Check out the new SourceForge.net Marketplace.
>> > > It's the best place to buy or sell services for just about anything
>> > > Open Source.
>> > > http://sourceforge.net/services/buy/index.php
>> > > _______________________________________________
>> > > Sipp-users mailing list
>> > > Sipp-users@lists.sourceforge.net
>> > > https://lists.sourceforge.net/lists/listinfo/sipp-users
>>
>>
>
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Sipp-users mailing list
Sipp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sipp-users

Reply via email to