< Previous by Date Date Index Next by Date >
< Previous in Thread Thread Index Next in Thread >

Re: [reSIProcate] Is Contact header in 180 Ringing Mandatory ?


It looks like this is a dum bug.

>From 3261:
   Zero, one or multiple provisional responses may arrive before one or
   more final responses are received.  Provisional responses for an
   INVITE request can create "early dialogs".  If a provisional response
   has a tag in the To field, and if the dialog ID of the response does
   not match an existing dialog, one is constructed using the procedures
   defined in Section 12.1.2.

It looks to me like dum is assuming that a 1xx always creates an early
dialog. We will need to do something if a 1xx is received without a
Contact. Presumably, we should make a callback on the AppDialogSet for
this case and NOT create a dialog. The same goes if a 1xx is received
with no to tag.

On 11/11/05, Asheesh Joshi <asjoshi@xxxxxxxxxx> wrote:
> Hi,
>  I am having a problem with my B2BUA using resip. When a client responds
> with 180 Ringing ( without contact)  to my INVITE, the resip stack throws an
> error saying "Cannot create dialog, no contact in 180".
> Is contact mandatory in 180 ? I don't see this in RFC 3261 !
>
> -best regards
> Asheesh.
>
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel
>