Re: [reSIProcate] Problem designing a B2BUA with DUM
This seems to me like a state that you should maintain in your
application. It might also be possible to provide some b2bua support
directly in dum. If folks are interested in this I would suggest that
we have a more detailed requirements discussion on the mailing list
followed by a conference call to discuss it further.
On 11/10/05, Micky Kaufmann <micky@xxxxxxxxxxx> wrote:
> Hi all,
>
> I have the following scenario:
>
>
> 'A' B2BUA 'B'
>
> INVITE without an Offer
> ------------------------>
> INVITE without an Offer
> ------------------------>
> .
> .
> .
> 180 With Offer
> <------------------------
>
> The problem I have is in the UAS part of the B2BUA - the state of the
> UAS in the end of the scenario above is 'UAS_EarlyProvideOffer' now when
> it sends a provisional the offer isn't sent with it.
> The B2B I want to design should let 'A' and 'B' make offer/answer
> negotiation without accepting an offer itself (only if 'A' or 'B'
> accepted an offer the negotiation should end)
> It seems like another state should be added between
> 'UAS_EarlyProvideOffer' and 'UAS_AcceptedWaitingAnswer' ...
>
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel
>