[Spce-user] rtpengine usage in serial forking

[John Nash]

Yes I can see that even if call-id is same but to tag is different
rtpengine allocating new port But my issue is end UA receives two different
ports in two session progress message (One for each forked destination). My
complete flow is...
UA Sends Invite to openser
Openser does rtpengine_offer and forwards to Media Server (IVR) (Port 1111
as example sent to Media Server)
Media Server sends Session Progress to openser and openser does
rtpengine_answer
Openser sends Session Progress back to UA (Port 2222)
At openser media servers sends failure message (After IVR is played) and
openser sends Invite again to Other destination a gateway (Port 1111sent
again to gateway too!!)
When gateway sends session progress and openser does rtpengine_answer again
it allocates a different port !! 3333 and finally UA receives another port
in second session progess.

I understand that To tag is different in second session progress from
gateway but something seems to be wrong.

Expected behavior is UA should always receive single port (In both session
progress) and two Invites (Each to different destinations should have
different port) isnt it?




















On Wed, Jan 21, 2015 at 7:31 PM, Richard Fuchs <rfuchs at sipwise.com> wrote:

> On 01/21/15 06:42, John Nash wrote:
> > Dear Guys,
> >
> > I need to use rtpengine where I am forking invite between a media server
> > (For some announcement and dest gateway).
> >
> > I looked at via-branch flag and looks like that should be used there but
> > I am not sure about complete flow.
> >
> > Should I call rtpproxy_offer with via tag for each branch (Branch
> > route)?...what about when I receive two session progress?...and how can
> > I delete one specific branch session?
>
> The via-branch is currently not used by rtpengine, instead the from- and
> to-tag is used to distinguish between multiple dialogues within the same
> call. This is normally enough to establish media even if multiple media
> responses are received. Session deletion also works as long as the
> to-tag is included.
>
> cheers
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20150121/0ac49e5b/attachment-0001.html>