Thanks for this clarification. I'll make my question more concrete.
In a SIP-ISUP interworking case, suppose I want to send a re-INVITE because I received an ISUP SUSPEND message from the TDM network. Since a SUSPEND message does NOT include a Q850 cause code, I simply don't have a "cause", but still I would like to provide a Reason for the re-INVITE. Many thanks Jan Van Geel IT and Network Specialist Belgacom SDE/SDV/PSE/FVC Tel: +32 2 202 1035 Tel: +32 2 207 9032 Email : [email protected] www.cyberwezz.tk -----Original Message----- From: Ritul Sonania [mailto:[email protected]] Sent: 20 May 2011 14:40 To: VAN GEEL Jan (SDV/PSE) Cc: [email protected] Subject: RE: Reason header syntax > -----Original Message----- > From: VAN GEEL Jan (SDV/PSE) [mailto:[email protected]] > Sent: Friday, May 20, 2011 5:59 PM > To: Ritul Sonania > Cc: [email protected] > Subject: RE: Reason header syntax > > In that case can someone explain me what "cause" I need to put when > using a Reason header in an initial Request e.g. an initial INVITE ? > > As far as I understood from RFC3326 is one of the goals of the Reason > header to include a Reason why a particular Request is being sent. > Hi, That's true but that request which you are generating now, should be because of a result of some other response which your proxy got. >From the RFC - " Third party call controllers sometimes generate a SIP request upon reception of a SIP response from another dialog. Gateways generate SIP requests after receiving messages from a different protocol than SIP. In both cases the client may be interested in knowing what triggered the SIP request." Different causes you can see here - http://wiki.freeswitch.org/wiki/Hangup_causes For an example, your proxy forks an invite to other terminal because the previous request was terminated/rejected as the calling number was not available. Then your proxy should raise the INVITE with Reason code copied from the response it get from previous attempt. Hope you got it, looks confusing :) Regards, Ritul Sonania > Many thanks > > Jan Van Geel > IT and Network Specialist > Belgacom SDE/SDV/PSE/FVC > Tel: +32 2 202 1035 > Tel: +32 2 207 9032 > Email : [email protected] > www.cyberwezz.tk > > > -----Original Message----- > From: Ritul Sonania [mailto:[email protected]] > Sent: 20 May 2011 14:15 > To: VAN GEEL Jan (SDV/PSE) > Cc: [email protected] > Subject: RE: Reason header syntax > > > > > -----Original Message----- > > From: [email protected] [mailto:sip- > > [email protected]] On Behalf Of VAN GEEL Jan > > (SDV/PSE) > > Sent: Friday, May 20, 2011 2:27 PM > > To: [email protected] > > Subject: [Sip-implementors] Reason header syntax > > > > Dear all, > > > > > > I have a question about the SIP reason header syntax. Apologies if > this > > has been asked before or in case this isn't the right forum. > > > > In RFC 3326 the Reason header is defined as follows: > > > > --------------------------------- > > Reason = "Reason" HCOLON reason-value *(COMMA reason- > value) > > reason-value = protocol *(SEMI reason-params) > > protocol = "SIP" / "Q.850" / token > > reason-params = protocol-cause / reason-text > > / reason-extension > > protocol-cause = "cause" EQUAL cause > > cause = 1*DIGIT > > reason-text = "text" EQUAL quoted-string > > reason-extension = generic-param > > ---------------------------------- > > > > The question is whether the following syntax is correct given the > fact > > that there is a sentence " SIP: The cause parameter contains a SIP > > status code.": > > > > Reason: SIP ;text="Network Initiated Resume" > > > > Or does the sentence means that a reason-param "protocol-cause" is > > actually mandatory ? > > Hi, > > I believe protocol-cause must exist, since the code carries both for > SIP status codes, and Q.850 codes. As in the code will represent the > correct status code/cause value. > > Best Regards, > Ritul Sonania > > > > > Many thanks > > > > Jan Van Geel > > > > **** DISCLAIMER **** > > http://www.belgacom.be/maildisclaimer > > > > _______________________________________________ > > Sip-implementors mailing list > > [email protected] > > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors > This message and the information contained herein is proprietary and > confidential and subject to the Amdocs policy statement, > you may review at http://www.amdocs.com/email_disclaimer.asp > > > **** DISCLAIMER **** > http://www.belgacom.be/maildisclaimer This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at http://www.amdocs.com/email_disclaimer.asp **** DISCLAIMER **** http://www.belgacom.be/maildisclaimer _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
