Dave, For the send path you should start looking at message.cpp which parses the scenario and creates the SendingMessage structure that is then used by call::CreateSendingMessage to actually assemble the message from its constituent components.
For the receive path, you probably need to start in sipp.cpp and take a look at the process_message function. You'll need to dive into several of the functions that it eventually calls. Also, you should start from the Subversion trunk rather than a released version. Charles "David Adams" <[EMAIL PROTECTED]> wrote on 03/13/2008 04:03:32 PM: > Awesome! I'll start tinkering. > > Thank you. > > Dave. > > This email message and any attachments may be confidential and/or > privileged to Nortel. If the reader of this message is not the intended > recipient, you are hereby notified that any use, disclosure, > distribution or copying of this communication is strictly prohibited. > If you have received this communication in error, please notify us > immediately by replying to this message or by calling the sender and > then destroying all copies of the message and any attachments. > > -----Original Message----- > From: Charles P Wright [mailto:[EMAIL PROTECTED] > Sent: Thursday, March 13, 2008 3:44 PM > To: Adams, David (CAR:3P33) > Cc: [email protected]; > [EMAIL PROTECTED] > Subject: Re: [Sipp-users] Binary Encoded Data as part of scenario file > or inf file? > > You'll need to modify the SIPp source code to use length specified > rather than null terminated strings and associated functions.. > > Charles > > [EMAIL PROTECTED] wrote on 03/13/2008 03:37:54 > PM: > > > Hi, > > I have an interesting scenario that I'm trying to simulate and I > > thought SIPP could do it. However, now I'm not so sure after looking > > at the source code. > > Does anyone know if it's possible to include binary data as part of > > SIP message payload either directly in the sceanario file or possibly > > through an info file? > > In my experiments I've found that whenever I try to specify binary > > data, the SIPP message parsers choke on binary characters that > > translate to a null character (\0). Is there anyway, short modifying > > the SIPP source code, for specifying binary data in the message > > payload? > > Thanks, > > Dave Adams. > > > > > ------------------------------------------------------------------------ > - > > This SF.net email is sponsored by: Microsoft Defy all challenges. > > Microsoft(R) Visual Studio 2008. > > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > > _______________________________________________ > > Sipp-users mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/sipp-users > ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Sipp-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sipp-users
