Distinctive ringing is a feature service offered by service provider, and it is controlled from server by inserting Alert-Info to INVITE.
The reason to include Alert-Info in 180 is to make ring-back tone cadence consists with remote ring cadence. 180 should have same Alert-Info it received in INVITE. Gali -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Thursday, November 18, 2004 3:50 PM To: Wainwright, John Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; 'Troy Cauble' Subject: RE: [Sip-implementors] Distinctive Call ringing. John, I am with Ben, it is morning in my hemisphere and I to am lacking coffee - but what good is including an Alert-info header in the 180 Ringing ?, unless I have missed something I know of it only as a way to inform the end device to play a distinctive ring - sending it back in the reverse direction is accomplishing what ?. The 'mapping' of this I have seen is play distinctive rings for each line of a multiline phone - to give audible representation of which line (dn) is being alerted, although whatever is sending the INVITE to the end device can do whatever logic to insert | change this field (I have heard of the concept of alerting with a different tone based on the incoming call being a fax - but the logic to do this is boggling). I believe the number setting you may have seen could have been for Cisco phones distinctive ring - I understand / recall that they have a numeric number which correlates to different tones on the phone - it only supports 4 or something, I believe I remember having to re-use tones on a 7960 6 line phone. The URL form of doing it is much more flexible - you can point it at standard known Bellcore tones - some of which will be included in phone firmware which lest you use the 127.0.0.1 loopback IP address as given in troys example below, so no security risk there. But if the device is trusting - no problem in pointing it somewhere else and getting Muppets theme or something as ring tone as well. Regards, Wayne Davies "Wainwright, John" <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 19/11/2004 05:45 AM To: "'Troy Cauble'" <[EMAIL PROTECTED]>, [EMAIL PROTECTED] cc: 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 ************************************************************************ ****** - NOTICE FROM DIMENSION DATA AUSTRALIA This message is confidential, and may contain proprietary or legally privileged information. If you have received this email in error, please notify the sender and delete it immediately. Internet communications are not secure. You should scan this message and any attachments for viruses. Under no circumstances do we accept liability for any loss or damage which may result from your receipt of this message or any attachments. ************************************************************************ ****** _______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
