search

naidu / telephone

Automatically exported from code.google.com/p/telephone
Other
0 stars 0 forks source link

Distinctive ringing does not work. #361

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Set up a different ringing tone for your extension or ring group in asterisk
2. call it
3. listen

What is the expected output? What do you see instead?
A different ringing tone

What version of the product are you using? On what operating system?
All

Please provide any additional information below.
Basically this would require tone generating the ring alerts and or allowing 
selectively choosing sounds (which sounds annoying and less likely to be widely 
compatible)

Original issue reported on code.google.com by xsmurfs...@gmail.com on 8 Aug 2010 at 3:41

GoogleCodeExporter commented 9 years ago 
Sorry, I don't understand what you mean. Where do you set up a different 
ringing tone?

Original comment by eofs...@gmail.com on 16 Aug 2010 at 9:43

GoogleCodeExporter commented 9 years ago 
Ring tones are generated by the (PSTN) central not the phone (or the ATA or the 
Zaptel channel), however asterisk sends the distinctive ring request trough the 
"Alert-Info" header. On my ATA I can even sent the tones manually for each 
distinctive ring. (ex: Bellcore-r2 is defined as 60(.3/.2,1/.2,.3/4)). Some 
more information here 
http://www.voip-info.org/wiki/index.php?page=Asterisk+SIP+channels. If you have 
an ATA box, try sending Bellcore-r4 in the alert info, it should ring 
differently. Let me know if you have more questions, I'm not sure I'm making 
sense myself :p

Original comment by xsmurfs...@gmail.com on 16 Aug 2010 at 10:44

GoogleCodeExporter commented 9 years ago 
Actually yeah I probably wasn't clear... probably because I don't fully 
understand how Asterisk might handle distinctive ringing. Really as I 
understand it you put the ring name in the Alert-Info header. I looked a little 
but was unable to find a list of the said ring names. I know in my north 
american config ATA box (and some docs from Asterisk) that "Bellcore-r1" 
through "Bellcore-r6" is what is defined there. I've tried it and it works. 
It's nice to "mark" inbound routes for call screening.

Original comment by xsmurfs...@gmail.com on 17 Aug 2010 at 2:25