Maybe I need some more coffee :) In the INVITE the Alert-info message is applicable to the ED party and in the RINGING message it is of interest to the ING party. Correct ? I think what I meant to say is that my application will need to handle the Alert-info when it receives an INVITE and then determine what 'tone' to play.
Regards John -----Original Message----- From: Ben Gatewood [mailto:[EMAIL PROTECTED] Sent: Thursday, November 18, 2004 1:53 PM To: Wainwright, John; Troy Cauble; [EMAIL PROTECTED] Subject: RE: [Sip-implementors] Distinctive Call ringing. I may have missed something here (it's late and I've had too much coffee) but what is the point in putting an Alert-info header into a 180 RINGING? Surely the information conveyed by this header is only relevant when delivered to the *called* party? Regards, Ben -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Wainwright, John Sent: 18 November 2004 18:45 To: 'Troy Cauble'; [EMAIL PROTECTED] Subject: RE: [Sip-implementors] Distinctive Call ringing. This could be the case - I will investigate further. I think I am only really interested in the Alert-info as part of the 180 Ringing message - I don't think my application will generate it in an INVITE method. Aren't there security concerns with supplying a URL from a Calling party to be played by a Called party ? I always thought DCR was more useful when linked to a caller ID such that a different 'tone' was played depending on the calling party ? Thanks John -----Original Message----- From: Troy Cauble [mailto:[EMAIL PROTECTED] Sent: Thursday, November 18, 2004 1:25 PM To: [EMAIL PROTECTED]; Wainwright, John Subject: Re: [Sip-implementors] Distinctive Call ringing. "Wainwright, John" <[EMAIL PROTECTED]> wrote: > Does anyone have any experience with Distinctive Call Ringing using > SIP ? > > As far as I can make out this is achieved using the ALERT-Info header > which seems to take a URL as a parameter to indicate what ringing > 'tone' to play. I thought I came across a Cisco implementation that > used an integer field instead of the URL. > > Any insights ? > > Thanks > John Alert-Info: and the use of an URL are standard. I've seen more than one system use this form Alert-Info: <http://127.0.0.1/Bellcore-dr3> to indicate a DR, but I don't think it's a standard. (Google will turn up some examples.) Just guessing, but maybe the implementation you remember took a integer field at configuration time, then generated something like the above from it. -troy _______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors ************************************************************************ ************** Disclaimer: This electronic message may contain privileged or confidential information. If you are not the intended recipient, be advised that any disclosure, copying, distribution or use of this information is strictly prohibited. If you are not the intended recipient, please notify the sender and delete this message. Views expressed in this message are those of the individual sender, and are not necessarily the views of the Streamdoor Limited, unless otherwise stated. Although Streamdoor Limited has taken reasonable precautions to ensure no viruses are present in this email, the company cannot accept responsibility for any loss or damage arising from the use of this email or attachement Employees of Streamdoor Limited and its affiliates are expressly required not to make defamatory statements and not to infringe or authorise any infringements of copyrights or any other legal right by email communications. Any such communication is contrary to company policy and outside the scope of the employment of the individual concerned. For further assistance on email policy, or if you have received this email in error, please contact Streamdoor Group IT&C Helpdesk by email at it&[EMAIL PROTECTED] or write to Streamdoor Ltd , Head of IT&C Department , 114 Power Road , Chiswick, London , W4 5PY. www.streamdoor.com ************************************************************************ ************** **************************************************************************** ********** Disclaimer: This electronic message may contain privileged or confidential information. If you are not the intended recipient, be advised that any disclosure, copying, distribution or use of this information is strictly prohibited. If you are not the intended recipient, please notify the sender and delete this message. Views expressed in this message are those of the individual sender, and are not necessarily the views of the Streamdoor Limited, unless otherwise stated. Although Streamdoor Limited has taken reasonable precautions to ensure no viruses are present in this email, the company cannot accept responsibility for any loss or damage arising from the use of this email or attachement Employees of Streamdoor Limited and its affiliates are expressly required not to make defamatory statements and not to infringe or authorise any infringements of copyrights or any other legal right by email communications. Any such communication is contrary to company policy and outside the scope of the employment of the individual concerned. For further assistance on email policy, or if you have received this email in error, please contact Streamdoor Group IT&C Helpdesk by email at it&[EMAIL PROTECTED] or write to Streamdoor Ltd , Head of IT&C Department , 114 Power Road , Chiswick, London , W4 5PY. www.streamdoor.com **************************************************************************** ********** _______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
