Thanks all.
-- Eduardo
-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-
http://emmartins.blogspot.com
http://www.redhat.com/solutions/telco
On Fri, Sep 3, 2010 at 12:15 AM, Iñaki Baz Castillo wrote:
> 2010/9/2 Paul Kyzivat :
>> (a) is the correct answer.
>>
>> You *may* need to send requ
2010/9/2 Paul Kyzivat :
> (a) is the correct answer.
>
> You *may* need to send requests in an early dialog.
> For instance, a reliable provisional response requires a prack to be
> sent in the dialog. Also in some cases an UPDATE may need to be sent to
> carry an additional offer.
And there could
Eduardo Martins wrote:
> Hello, trying to clarify thoughts with early dialog forking, generally
> is there such concept?
>
> For instance when receiving two 180s with different tags, should:
>
> a) 2 early dialogs be "constructed" (why? is there any need to a
> REQUEST to be sent before receivi
Hi Eduardo,
Generally dialog is an end to end relation, not a SIP Proxy one. Proxy layer
is built above transaction layer and there is no dialog forking there is
only a request forking.
When SIP Proxy receives a response, possibly related to forked requests, it
finds the appropriate response conte
Hello, trying to clarify thoughts with early dialog forking, generally
is there such concept?
For instance when receiving two 180s with different tags, should:
a) 2 early dialogs be "constructed" (why? is there any need to a
REQUEST to be sent before receiving 2xx response which needs the
tags?)
