![]() |
|
|
#21 | |||
|
Junior Member
Join Date: Apr 2008
Location: Cleveland
Posts: 11
|
Quote:
That would suck. |
|||
|
|
|
|
|
#22 | |||
|
Junior Member
Join Date: Apr 2008
Location: Cleveland
Posts: 11
|
Quote:
|
|||
|
|
|
|
|
#23 | ||
|
Member
Join Date: Sep 2006
Location: Little Rock, AR
Posts: 52
|
I don't know the cost of the NET 7000 unit itself. Those were installed by onholdworx and are included as part of our monthly fee. I hate to put pricing on here because that can probably vary depending on number of sites and length of term. But I will say that it was only slightly more than what we were paying (a major wel-known vendor) for a service that gave us quarterly updates, and it was half the cost of another service we had that allowed unlimited updates.
|
||
|
|
|
|
|
#24 | ||
|
Junior Member
Join Date: Jul 2008
Location: Oregon
Posts: 5
|
ITS Telecom
I use 2 of these MusicTel-Net + units at my two PRI sites. They are remotely managed via a small piece of software. You can adjust the volume level output as well as running multiple mp3's. They work great and I have had zero problems with them. Very reliable. Of course, it would be ideal if I only had to run 1 of these, but 2 isn't bad. For us, we have all 13 of our sites accessing the PRI trunks at the two sites, so it works. If each site had it's own trunks, that would be a different story. |
||
|
|
|
|
|
#25 | ||
|
Junior Member
Join Date: Dec 2006
Location: Denver
Posts: 21
|
My company is currently looking at new VoIP solutions including ShoreTel. If all ShoreTel users were as "helpful" as jlorenz, I think I would definitely look elsewhere. One of the things I really didn't like about ShoreTel last time we looked at them was their handling of MoH. It appears that this has not been fixed in the past two major releases. Multicast MoH from a primary source is easily doable. I don't understand why ShoreTel makes things so complicated.
In our case, a single MoH source at our headquarters would suffice for our entire network, but ShoreTel's architecture doesn't allow that. This can be frustrating, and I don't see why some people try to trivialize this point by acting as if it isn't a real issue. |
||
|
|
|
|
|
#27 | ||
|
Junior Member
Join Date: Dec 2006
Location: Denver
Posts: 21
|
That's the problem. Our primary site does have a couple PRIs, but many other sites also have their own incoming CO trunks. That means that each of those sites would have to have their own MoH source. I'd much rather have a single multicast MoH source at the headquarters that the remote switches listen to. That's super easy to do. I don't know why ShoreTel doesn't implement it.
|
||
|
|
|
![]() |
| Thread Tools | |
| Display Modes | |
|
|