[asterisk-dev] ACK - wrong URI?

Santiago Gimeno santiago.gimeno at gmail.com
Mon Mar 16 11:19:35 CDT 2009


Hi,

In section 13.2.2.4

"The UAC core MUST generate an ACK request for each 2xx received from
   the transaction layer.  The header fields of the ACK are constructed
   in the same way as for any request sent within a dialog (see Section
   12) with the exception of the CSeq and the header fields related to
   authentication. "

Best regards,

Santi

On Mon, Mar 16, 2009 at 5:10 PM, Chris Maciejewski <chris at wima.co.uk> wrote:
>
> Hi Olle,
>
> Thanks for your reply.
>
> This is exactly what common sense tells me too:
> > The Contact: we get in the 200 OK is exactly the address we need to
> > send the ACK to.
>
> But could you please point me in the right part of RFC 3261 which
> describes this?
>
> I have spent best part of my day today reading RFC 3261 all over
> again, and failed to find the right paragraph.
>
> Thanks
>
> Chris
>
> 2009/3/16 Olle E. Johansson <oej at edvina.net>:
> >
> > 16 mar 2009 kl. 12.30 skrev Chris Maciejewski:
> >
> >> Hi,
> >>
> >> It seems to me Asterisk (1.6.1) is wrongly using "Contact" header from
> >> "200 OK" instead of original INVITE's URI when sending ACK to "200 OK"
> > Why is this wrong?
> >
> > The Contact: we get in the 200 OK is exactly the address we need to
> > send the ACK to.
> >
> > /O
> >
> >>
> >> My scenario:
> >>
> >> 1. Asterisk sends INVITE to 442088462718 at example.com:
> >>
> >> INVITE sip:442088462718 at example.com SIP/2.0
> >> From: "John Smith" <sip:NA@{some_ip_2}>;tag=as7ff91d10
> >> To: <sip:442088462718 at example.com>
> >> Contact: <sip:NA@{some_ip_2}>
> >> {body/some headers omitted}
> >>
> >> 2. 442088462718 at example.com replies with 100, 180 and finally:
> >>
> >> SIP/2.0 200 OK
> >> From: "John Smith" <sip:NA@{some_ip_2}>;tag=as7ff91d10
> >> To: <sip:442088462718 at example.com>;tag=2UBy3tD90HyrH
> >> Contact: <sip:{__CONTACT_IP__}>
> >> {body/some headers omitted}
> >>
> >> 3. Asterisk sends ACK with {CONTACT_IP} from "200 OK", rather than
> >> sip:442088462718 at example.com as in originaly INVITE:
> >>
> >> ACK sip:{__CONTACT_IP__}:5060 SIP/2.0
> >> Max-Forwards: 69
> >> From: "John Smith" <sip:NA@{some_ip_2}>;tag=as7ff91d10
> >> To: <sip:442088462718 at example.com>;tag=2UBy3tD90HyrH
> >> Contact: <sip:NA@{some_ip_2}>
> >> {some headers omitted}
> >>
> >> Is it a bug in Asterisk, or is it RFC 3261 complaint to use "Contact"
> >> from "200 OK" as ACK's URI?
> >>
> >> Best regards
> >>
> >> Chris
> >>
> >> _______________________________________________
> >> --Bandwidth and Colocation Provided by http://www.api-digital.com--
> >>
> >> asterisk-dev mailing list
> >> To UNSUBSCRIBE or update options visit:
> >>   http://lists.digium.com/mailman/listinfo/asterisk-dev
> >
> > ---
> > * Olle E Johansson - oej at edvina.net
> > * Cell phone +46 70 593 68 51, Office +46 8 96 40 20, Sweden
> >
> >
> >
> >
> > _______________________________________________
> > --Bandwidth and Colocation Provided by http://www.api-digital.com--
> >
> > asterisk-dev mailing list
> > To UNSUBSCRIBE or update options visit:
> >   http://lists.digium.com/mailman/listinfo/asterisk-dev
> >
>
> _______________________________________________
> --Bandwidth and Colocation Provided by http://www.api-digital.com--
>
> asterisk-dev mailing list
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-dev



More information about the asterisk-dev mailing list