[SIPForum-discussion] Regarding Trigger Point
rupandeep singh
er_rupandeep at yahoo.com
Mon May 19 06:24:29 UTC 2008
Hi neeraj,
So is this SPT trigger implementation dependent or there is any standard which defines which Headers or which lines to use for SPT.
Thanks and regards
Rupandeep
neeraj kumar <nekumar at gmail.com> wrote: It'll be good to keep the S-CSCF implementation simpler and more generic. Application Server is the node which anyway has to analyse the SIP message in detail for service execution.
So, design simpler SPTs and let the call go to AS, in case there isn't any requirement of service execution, it'll forward it (the call) back to S-CSCF.
S-CSCF functionality should be more focussed towards call handling rather than service identification/execution.
On 15/05/2008, Rajdeep Ahluwalia <rajdeepwalia at gmail.com> wrote: For multiple m lines in a INVITE msg probably the S-CSCF implementation will try to match each m line
And the regular expression can be (say u want to ignore the media format) :
All strings starting with "audio 3458 RTP/AVP" so no matter what comes after this the line will match the criteria.
U can refer the net for the exact syntax of REG EXP
Best regards,
Rajdeep
On 5/15/08, rupandeep singh <er_rupandeep at yahoo.com> wrote: Thanks Rajdeep for this information but one more thing i want to ask....
The m-line can have any number of codecs in it and each codec has a a line , so for each line we have to perform a search, than how can we create a SPT for m line or a line as there number are variable and also each time codecs used can be different.
And can you please elaborate what do u mean by regular expressions and string ie. the entire value of the line .
Regards
Rupandeep
Rajdeep Ahluwalia <rajdeepwalia at gmail.com> wrote: Also to add here you can use regular expressions for the content part.
the regular expression shall be matched with the string received in
the INVITE message
Best regards,
Rajdeep
On 5/15/08, Rajdeep Ahluwalia wrote:
> Hi Rupandeep,
>
> I believe the S-CSCF will try to match the whole content as from the
> TS 29.228 Annex F
>
> So, you should use second trigger point definition.
>
> Best regards,
> Rajdeep
>
> On 5/15/08, rupandeep singh wrote:
>> Hi,
>> Can anyone please tell me that when we create a trigger point in which we
>> define "line" and "content" for the SDP after that When a invite request
>> comes, does the the entire line content in SDP body of Invite request is
>> matched or matching is performed in parts ie.
>>
>> m=audio 3458 RTP/AVP 0 96 97 98 ( m line in SDP body of invite request)
>>
>>
>> Trigger point definition:
>> line: m
>> content : audio 3458 RTP/AVP
>>
>>
>> the above m-line in the SDP body of invite request would match or not or
>> would i have to define the entire m-line in the trigger point ie.
>>
>> Trigger point definition:
>> line:m
>> content :audio 3458 RTP/AVP 0 96 97 98
>>
>> Regards Rupandeep
>>
>>
>>
>
_______________________________________________
This is the SIP Forum discussion mailing list
TO UNSUBSCRIBE, or edit your delivery options, please visit http://sipforum.org/mailman/listinfo/discussion
Post to the list at discussion at sipforum.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sipforum.org/pipermail/discussion/attachments/20080518/fec6acb4/attachment-0002.html>
More information about the discussion
mailing list