Page 26 - Telecom Reseller March-April 2015
P. 26






26 Telecom Reseller December/January 2015
Nortel
Q: What would make a phone stop getting supervisors have individual extensions (that’s zero). If you think about it, that makes sense. 
message lights? I have a whole group of call common, by the way), they can’t reside on key Normally you have multiple appearances of 
Notes
center supervisors that stopped getting message
zero, since that key has to be the ACD Incalls key. keys that are not anyone’s primary extension, 
lights, but everybody else is ine. I’ve made hat’s okay normally, since they only appear on like a department number, and department 
some changes on other phones in the call center one set. If there is a single appearance, the PBX numbers should not be on key zero. If the PBX 
but not theirs.
sees that set as primary.
were to light the message indicators for all of 
AYou see, the PBX has certain rules it has to them, everyone with the department extension 
: Hmmm.. hat’s not a lot to go on, but my use in determining who gets a message light would have a bright red message indicator RUFFIN
irst guess is that you’ve put their extensions when it receives a signal from the voicemail every time a message was let in the department 
on other phones. You see, ACD phones are sort
system. One rule is that it doesn’t light the light mailbox. Even worse, if they had a personal 
of an exception to the Nortel rule that a user’s for a multi-appearance extension when it’s
voicemail message and the department also had by Phil Rufin
extension is the number on key zero. If ACD
on keys that are not the primary DN key (key
a message, the light would go out ater someone 
listened to the department message and they 
wouldn’t know they had a message. Confused? Try to keep up.
So here’s the deal. It looks like you added the 
supervisors’ extensions to someone else. Since 
the extensions are not primary on any phone, YOUR TICKET TO BECOMING A CLOUD 
the PBXs decided (following its rule) not to 
light any message indicators. Don’t blame the COMMUNICATIONS SERVICE PROVIDER
PBX—it’s the rule.
You (the new hero of the story) can now add 
an XMWK key to each of the phones, using 
their extension numbers. hat gives them an Vodia's cloud-ready IPPBX software offers an unparalleled go-to-market hosted 
individual indicator key to show they have a IPPBX solution for managed service providers (MSP) of all sizes through a robust 
voicemail message. In addition, if they want the 
big, red light to shine, you can add LMPX to the platform that delivers the highest levels of service uptime and scalability. Vodia 
CLS. hat lights the indicator if you have a non- IPPBX software is purpose-built to help new service providers realize economies of 
primary extension message.
scale and drive down startup costs by being able to serve multiple client 
hen they can throw you a big party and 
show their appreciation with cake and cookies.
organizations on a single hosted PBX server in the cloud, and eliminating the need 
Q: for dedicated hardware for each individual customer. The subscription-based SaaS 
I have a dozen or so phones that all have the same department numbers on 
them. hat group doesn’t have individual
pricing model is further designed to help keep IT costs consistent or even lower 
extensions or anything programmed diferent than packaged software for the end-customer while providing a steady recurring 
on their phones. When they have turnover in 
that department, I have to send them setup revenue stream for the service provider, creating a win-win situation for all. With 
information for the new user, but I don’t know plug-and-play endpoint set up, multi-tenancy, advanced contact center 
which phone (TN) the user needs to use. How functionality, enterprise mobility and rich collaboration features, you now have all 
can I identify the TNs so I know which belongs 
to the former and new user?
the tools you need to start your own cloud communications business in no time and 
Aprovide a great user experience to your customers.
: It seems obvious to me that you can just 
document the TNs and associate them to 
user names in a spreadsheet (or a sticky note) 
and re-use (and re-document) the TN when 
there is turnover. If that doesn’t work for you, put  Zero startup costs
 Recurring revenue stream 
an extension or intercom button on each, with 
the user’s name assigned to the key. If they are all  Unlimited extensions and call paths  Full control of minutes
in numeric sequence, listing them should be easy.  Multi-tenancy
 Free server redundancy
Update that key’s assigned name every time you 
have turnover to keep the information current. You can make the key non-ringing to keep it  Full white labeling
 Plug-and-play setup
from afecting the users (in other words, keep it
BYOD
Call and data security 
a secret).
  
No available keys? Add a phantom module.  Full admin level control
 Pay-as-you-go
Tell the system there is an additional module, 
but don’t add it to the physical phone. You could 
even make the name the jack number instead
of the name if you like, and have them tell you 
which jack the phone is plugged into.
Call us today:
Q
: How do you get to the personal directory +1-617-399-8147
on 3903 sets? I see where to ind it on 
3904s but where is it on the 3903s?
A
: here is no personal directory on 3903 
sets. If you need to have speed calling you 
can assign a speed call list and SCC button to key 
23.
www.vodia.com +1-617-399-8147 sales@vodia.com
First create a new SCL (Speed Call List) in 
overlay 18, then use that number for the SCC (Speed Call Controller).
he user can’t assign names to the entries like VodiaNetworks VodiaPBX
in the personal directory, but it can be quicker to 
use. ■

















p1-28_TR_Dec_Jan_2015.indd 26
15/01/2015 21:30
   24   25   26   27   28