Hi Sanjay,
Thanks for the response, please see comments below :
1) Night Switch - Not currently supported. It is a feature we are targeting in a follow-up release.
Will this support scheduling and an indicator ?
2) Currently one can forward it to any internal extension. What you are asking for is to forward it even an outside number. Yes, customer X wants to overflow the Hunt Group to an after hours Mobile Number
5) It is supported with 8.6.4 release. For direct call transfer to voicemail, hit transfer, * followed by extension number and transfer key again (or hang up the phone). Good to know, I tried this and it works
8) It is supported. With 8.6.4 release, one can create multiple Outside DIal Codes on the System Dial Plan page. Then on the site page, one can associate those outside dial codes to different connection groups. In your case, you will have one connection group with SIP connections and another with ISDN.
Can the system support +E.164 dialing ? Lets say I want to send +61 2 83945522 out of the SIP trunk ?
9) You can configure shared lines, speed dial BLF (monitor keys). Silent ring key is something which is not currently not configurable. I am not sure what is overlay key call. If I understand multicall key, it is call waiting feature. Each line on the phone has max of 2 calls by default.
At present, the only way to silence the ringing is to DND the phone, but this will silence all keys, consider a CEO who has a private line, or multiple private lines and doesnt want to be disturbed on his private line.
10) There is a softkey for call forward. Is there any specific reason you are looking for feature access code? I believe feature code is more problem because of reason to remember them. Sofkey is just there.
Feature access codes can be much easier to remember to do rather then navigating through a multitude of menus, consider and old TDM user who is used to having press *26 to fwd and #26# to cancel forward, this is much quicker and should be a secondary option to the menu driven way. - Call fwd is only an example.
12) With 8.6.4, you can define custom rules for different routing needs. Having said that I agree that translation rules are currently not very flexible. We are planning to improve that in next release.
This is good, I hope to see that the translation rules will have an option to select which exiting trunk route to use.
14) Reset to Factory Defaults is a feature on roadmap. May not be available in next release.
What about Skipping the wizard all together ?
15) Line 1 is the primary DN. It will be labeled to the Extension number or name. What do u want to label it to?
Heres the scenario on this one, at present doesnt looke like you are able to put the DN number as the label of Line 1. Consider company A has multiple sub-companies/departments coming in on different DID's company A's receptionist wants to have visibility of ALL sub-company's DID presented on each line of her handset. At present, you will need to create another USER and associate with the extension's lines, however you cannot Re-Label the key to reflect any meaningful information. Perhaps support for a "floating"/ "phantom"/ "fictive" key should be implemented. This kind of key does not need to be tied to any extension, and will not take up any licenses.
16) On the System Dial Plan page, there is a tab to do abbreviated dialing. You can configure translation of a speed dial to an E.164 number
Good, I tested this and it works, but I dont see what the point is in having options to prefix and postfix digits in this form, what is the thinking here?
18) It is already supported. You can add a VG224 gateway.
Good.
Also, are these on the roadmap ? :
- DSS/BLF monitoring of different line statuses, ie Ringing, Off Hook, DND
- Ability to customise codec types if using SIP trunks and edit SIP parameters such as the SDP headers and packetisation rates..
