How to set up Music on hold (MOH) (the easy way)
Felix:
I am trying to set up MOH on my OBi (in fact, MOH is the main feature that is missing in my non-PBX setup).
First, to clarify the scenario. I have a conversation (inbound or outbound call - shouldn't matter); somebody calls; I put the first call on hold and switch to the second call - the first caller gets music on-hold. This is the scenario that you are solving, right? When you say "Conference in the speed dial to the calling party" - it seems to be more involving than that and won't pass WAF test.
The first call can be over SP1 or SP2. I would much prefer to use internal server. Never heard of Homer before - it looks impressive (although documentation competes with OBi Admin guide in its in-comprehensiveness; clearly translation from German). Frankly, I can't figure out how would I set up OBi to pull music from Homer...
Any additional guidance would be awesome :D
ianobi:
@ QBZappy - I'm glad my very bizarre digit map ([^*+]@@[^+].<+:@>@@.|[^*]@@.'@'@@.) works for you. I designed it to get over the problem of sending "@" over the OBiTALK network.
@ azrobert - yes "sp2(music@iptel.org)" will work fine if the calls are being answered or originate from the OBi Phone Port, which is most cases. However, the trunk format in speed dials does not work from OBiAPP/OBiON.
If you are using OBiAPP with softphone and wish to access your music via the OBiTALK network, then ([^*+]@@[^+].<+:@>@@.|[^*]@@.'@'@@.) is useful. See my original post for other uses.
azrobert:
Quote from: ianobi on February 03, 2013, 02:55:05 am
If you are using OBiAPP with softphone and wish to access your music via the OBiTALK network, then ([^*+]@@[^+].<+:@>@@.|[^*]@@.'@'@@.) is useful. See my original post for other uses.
I think you guys intentionally try to make things more difficult than they have to be. LOL
Here is what I tried:
In OBitalk I set Speed Dial#3 to 3
In Obitalk Inbound call route I added:
{(290xxxxxx)>(<3:music@iptel.org>):sp2}
When I dialed "3" from Obion I was connected to Music.
I don't have any @'s in my DigitMaps.
I have SP2 registered to a provider and not setup as a dummy proxy 127.0.0.1
azrobert:
Quote from: Felix on February 02, 2013, 10:22:36 pm
First, to clarify the scenario. I have a conversation (inbound or outbound call - shouldn't matter); somebody calls; I put the first call on hold and switch to the second call - the first caller gets music on-hold.
I think QBZappy's MOH doesn't meet your requirements. This is how I got it to work.
You conference in Music. Both parties hear music. You can walk away while the other person listens to Music. When you return hit Flash to end music.
There is a Phone Port TransferWhenHolding. This doesn't meet your requirements either.
Hit Flash and then hang up. The other person is transfer to Music. Again, this is how I got TWH to work.
It seems to me that Obihai could add MOH. It would be very similar processing to Transfer When Holding. Maybe you should try a feature request, but I believe others have tried.
QBZappy:
OBi202 + Homer Conferencing might be a better fit, as the OBi202 has a native MOH setting.
Physical Interfaces->Calling Features->PHONEX Port->MOHServiceNumber (Could be a tel number or a sip uri). Note that using the Homer App requires a computer running. Using the music@iptel.org uri, no computer is required.
Re: Music On Hold doesn't work (using new MOHServiceNumber feature)
http://www.obitalk.com/forum/index.php?topic=4111.msg29915#msg29915
Quote from: mrjoe on November 12, 2012, 03:28:48 pm
The following is the reply I received from Obihai to my support enquiry below:
From: "Obihai Support Team" <support@obihai.com>
Date: 12 November 2012 08:57:34 PM GMT+02:00
To:
Subject: RE: OBi202 500xxxxxx, MOH
MOH server at the moment is for use with an OBiPLUS system, where the MOH
server is the OBiPLUS Master (an OBi202).
It might work if the MOH server is a standard SIP UA that answers <------ Homer Conferencing App
automatically and streams RTP to caller. If it works on outgoing call, it
should work on incoming call. No bugs in this regard that we know of.
Please check if your MOH server is actually sending out packets and to where
(IP address, port) in both cases. Make sure the audio codec used by your MOH
server is acceptable by your recipient in your case (the problem may be
because your incoming call uses a different codec compares to your outgoing
call).
Thank you.
-----Original Message-----
From:
Sent: Sunday, November 11, 2012 9:54 AM
To: support@obihai.com
Subject: OBi202 500xxxxxx, MOH
Navigation
[0] Message Index
[#] Next page
[*] Previous page