Hi,
I am testing a multi-tenant version of the software and have setup a conference.
I have setup a conference room as 390 which is saved as 2390 (due to the renant number) which is good. However when i dial either 390 or 2390 from a tenants registered phone i get a “this is not a valid extension” message.
How do i dial directly to either a Queue or a Conference room directly from a locally registered phone?
Feature codes are your friends :)
Yes, this is exactly correct - you have to create feature codes for about anything except of user extensions. This is done for the sake of flexibility over perceived ease of use - the approach we've taken that some may disagree with.
That said I wonder if the name "Feature Codes" confuses people as they think about these as only special codes to be entered on the phone and not "worker" codes that can be executed in a variety of ways and exist to allow invocation of any functionality (sorry if I talk too much :).
Would anyone vote for "Feature Extensions" or some other name?
I would definately change
I would definately change from "feature codes". am not sure what would be best... maybe "short codes" or "Dial Codes"?
Hi Alex, I'm not sure why
Hi Alex,
I'm not sure why you want to change the name, any ne will be fine to me. Is just something to remember.
But, in case you want to change it, I will suggest to use something similar to the TDM PBX. In my experience with Lucent Avaya, they use the name "Vector". that is the pointer that you put a call into, similar to the "Feature Extensions" here.
As I have seen that you are not happy with the name, I vote for "VECTOR".
Still looking for suggestions
Guys, I am too close to to Thirdlane PBX to assess how a new user reads "Feature Codes" or "Feature Extensions". "Vector" does not make me comfortable either but I truly can't think of a good name.
Please more suggestions!
"feature codes"
I would be careful here and try to stay within the boundaries of the accepted operational names from the TDM world.
If it helps to make things less confusing, even though they are basically the same from an Asterisk scripting point of view make two categories {pages}.
One could be "feature codes" as this falls into the thinking of an end user functions the same as dial codes, then make a second category {page} called call control.
As mentioned previously the VDN & Vectors used in Avaya are for the tech for building call control. The end user never sees or touches this. However, dial code, aka feature codes, are built and distributed expressly for the end user. Personally I am just fine with Feature Codes.
vertical service codes
vertical service codes tend to only referr to those *digit extensions. Feature extensions seems to cover not only vertical service codes but also an extension that does something besides calling a user directly.
Still looking for suggestions
the name feature codes is correct for default code, where I think the problem is is everything seems to get dumped there when creating things like conferences access code and many other things that really shouldn't be there..
maybe something to think about is either putting them in the sections that apply to them OR creating a new section for advanced codes or something of the sort..
G
To partially answer my own question I RTFMd again and spotted in the thirdlane-pbxUsersGuide.pdf that it says you have to create a feature code to access the conference rooms. I assume its the same for Queues as well...