Douglas Garstang
2006-Aug-07 15:16 UTC
[asterisk-users] Music On Hold Class Not Makin' Sense
I've discovered that music on hold, in general, doesn't behave in a way that makes sense. Here's my sip.conf: sip.conf: [general] musicclass=natv_default [3254101] musicclass=classic [3254103] musicclass=natv_silence Here's what happens with these settings: 3254101 calls 3254103: 3254101 puts 3254103 on hold -> Plays default 3254103 puts 3254101 on hold -> Plays classic 3254103 calls 3254101: 3254103 puts 3254101 on hold -> Plays default 3254101 puts 3254103 on hold -> Plays silence In summary, when a caller puts a callee on hold, the music on hold class played is always the system-wide setting set in sip.conf. When the callee puts the caller on hold, the music on hold class played is what's defined in sip.conf for the caller. This really makes no sense whatsoever. Common sense would dictate that when the callee puts the caller on hold, that the music on hold class heard should be what's defined in sip.conf for the CALLEE. That is, this person(the callee) wants everyone who calls and gets put on hold to hear what they have defined. Take for example, a small business that wants to have custom advertising or such played when someone calls THEIR number. How about if they wanted different custom advertising on different extensions? The SetMusicOnHold() app won't help here either. You can only set ONE class of moh for a call between two phones. If the two extensions want different moh classes when they put someone ELSE on hold, then this just isn't possible. Has anyone else encountered this before? How did you work around this? Doug.
Olle E Johansson
2006-Aug-08 01:24 UTC
[asterisk-users] Music On Hold Class Not Makin' Sense
The music on hold system was changed by Russell in trunk a few days ago, since what you describe is a bug reported long time ago by Terry Wilson. In trunk/1.4, when you put someone on hold, the music played is whatever is configured for the device that puts someone else on hold. If you want to play commercial announcements for your customers, you do it. We had a discussion on AstriDevCon in Pisa about this and defined the architecture that Russell now has implemented. This required some changes to the internal structure of the coming Asterisk 1.4 that can't be backported to 1.2, so 1.2 will remain as it is. regards /Olle