Meet Me Conference Observation 10.1 1

[gntsfan8690]

Discovered this little nugget today, not sure anyone else has. Customer is on 10.1 Select Edition. It appears when you are the first party to enter a meet me conference, you will hear MOH/on-hold tone until a 2nd party arrives. I spent hours on this thinking I was doing something wrong, until someone suggested we both try dialing in. As soon as I dialed in after him, the on-hold tone went away. So, unless there's a place to disable this, it looks like when people want conference bridges, we need to make sure we load some MOH files to their system, as well as record something that warns the participants they will remain on hold until additional parties arrive. I'm not sure this is a 10.1 GA bug, but I didn't see anything about this in the SP1 tech bulletin.

 

[Westi]

This started in R7 I think of you use conference bridge numbers that match extension numbers.

If it doesn't match extensions then I have not discovered that to work like this but also have to say that I don't have select on a server edition to test it just the regular ones.


Joe W.

FHandw, ACSS (SME)


"This is the end of the world, make sure to buy your T-shirt before it is too late"
Original expression of my daughter

 

[budbyrd]

We use a seperate MOH source on our bridges with the please wait message.

SC-- 5000
feat-- Conf meet me
tel-- h(2)N

Dermis and feline can be divorced by manifold methods.*
*(Disclaimer for all advise given)--'Version Dependent'

 

[gntsfan8690]

I created a specific meet me short code yesterday that had no relationship with a user's extension, routed a DID to it, and when the first party called in, he got the busy tone until I dialed in right after.

 

[Pepp77]

Yep, does look like a 10.1 thing (not select), and only appears to happen on external calls to the conf meet me and not internal calls to it.

| ACSS SME |

 

[gntsfan8690]

Yep, pretty dumb if you ask me. Something else to look out for upgrading a customer from 10.0 and below.