Re: [Seagull-users] Matching session id

[Olivier J. <oli...@hp...>]

Yariv,

the SIP environment has just been checked-in in SVN:
http://svn.sourceforge.net/viewvc/gull/seagull/trunk/src/exe-env/

No documentation for now, this will come soon.

Olivier.

Olivier Jacques wrote:
> Yariv,
>
> The reg expressions are defined in the dictionary. This is an XML file 
> that is passed as parameter when you start Seagull (-dico option).
> If you are interested in a SIP dictionary for Seagull, we will release 
> one in the following days, as well as an example UAC and UAS scenario.
>
> Olivier.
>
> Yariv Omer wrote:
>> Hi
>>
>> Thanks for the answer.
>>
>> I didn't understand where I need to define the reg expressions.
>>
>> For example if I am interested in the SIP protocol, where can I define
>> the matching rules of transactions and the ones for dialogs?
>>
>> I don't want to use the Sipp because I need several protocols
>> application.
>>
>> Regards, Yariv
>>
>>
>> -----Original Message-----
>> From: Olivier Jacques [mailto:oli...@hp...] Sent: 
>> Wednesday, October 25, 2006 4:11 PM
>> To: Yariv Omer
>> Cc: gul...@li...
>> Subject: Re: [Seagull-users] Matching session id
>>
>> Yariv Omer wrote:
>>  
>>> Hi
>>>
>>>  
>>>
>>> I didn't understand how seagull matches the incoming messages to the 
>>> correct scenario run?
>>>
>>> Basically there is a need to do a parsing on the message received, and
>>>     
>>
>>  
>>> match one (or several) fields (depending by the protocol) in order 
>>> to match the incoming message to the correct scenario 'instance' run.
>>>
>>>  
>>>
>>> Where do I define the matching rules, and how the parsing is done?
>>>
>>>  
>>>
>>> Regards, Yariv
>>>
>>>     
>> Hello Yariv,
>>
>> you actually understood the principle in general.
>> As indicated in the doc, "Session-Id" part 
>> (http://gull.sourceforge.net/doc/core.html#Session-Id), the protocol 
>> field that is used to match the message received to an existing scenario
>>
>> 'instance' run is indicated in the protocol dictionary.
>> This section: http://gull.sourceforge.net/doc/core.html#Dictionary 
>> provides the details of the parameters that are used in the 
>> dictionary. The attribute "session-id" will indicate which protocol 
>> field is used to
>>
>> identify the session. "out-of-session-id" will be used if the 
>> "session-id" cannot be found in the message received (seen as a "backup"
>>
>> session-id).
>> How the parsing is done depends on the protocol family (binary, text 
>> or other). Generally speaking, for the text family, the protocol is 
>> parsed using regular expressions (as you can tell from the 
>> dictionary). For binary, the parsing is done using internal Seagull 
>> routines, following dictionary description of the protocol.
>>
>> The whole mechanism being quite generic, this allows to add new 
>> protocols quickly in Seagull.
>>
>> I hope I was clear :)
>>
>> May I ask at which protocol you are looking at?
>>
>> Best regards,
>> Olivier.
>> HP OpenCall Software
>>
>>
>>   
>
>