Sorry typo in example code. Should be
SIPMessage invite;
/// Pupulate INVITE headers here
SIPHeader fork( "PARALLEL-FORK" );
fork.SetHeaderBody( "<sip:11...@gw...:5060>,
<sip:22...@gw...:5060>, <sip:33...@gw...:5060>" );
invite.SetInternalHeader( "PARALLEL-FORK", fork );
fsm.FindTransactionAndAddEvent( invite );
jo...@op... wrote:
> Hello Everyone,
>
> I am happy to announce that parallel forking is now supported by
> OpenSIPStack and OpenSBC. For OpenSBC Users, Parallel Forking will
> be enabled by setting the fork parameter in B2BUA Route Entry like so
>
> [sip:1111*;fork=true] sip:gw1.domain.net:5060,
> sip:gw2.domain.net:5060, sip:gw3.domain.net:5060
>
> Instead of the usual serial fail-over, OpenSBC will send out
> simultaneous INVITEs to all three routes. The first to send a 183
> with media or a 200 final response among the three routes will be used
> by OpenSBC to process the call. The remaining two forked calls will
> be CANCELed.
>
>
> For OpenSIPStack users, parallel forking is accomplished by setting
> the "PARALLEL-FORK" internal header of the INVITE you want to send
>
>
> SIPMessage invite;
> /// Pupulate INVITE headers here
> SIPHeader fork( "PARALLEL-FORK" );
> fork.SetHeaderBody( "<sip:11...@gw...:5060>,
> <sip:22...@gw...:5060>, <sip:33...@gw...:5060>" );
> fsm.FindTransactionAndAddEvent( invite );
>
>
> Thats it. The transaction layer will take care of forking your
> request and canceling abandoned forks.
>
> Joegen
>
>
|
