ahennis@voicespring.net
-
Posts
233 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by ahennis@voicespring.net
-
-
I did try that feature. It is very nice and I like it a lot.
As I said it would be nice to be able to have a button just toggle the flag on/off.
Here is a use case.
I have a customer with business hours from 8:00 AM to 5:00 PM. I setup an auto service flag for those hours. The customer wants a visual indication that night service is active so I program a button to monitor the auto night service flag. The customer also wants a way to manually turn on his night service. To make this work I create a manual service flag and configure another button on the phone to turn on/off this manual night service.
In this case it would be nice to just be able to flip the auto service flag on or off. I envision this feature as just turning the flag on or off until the next scheduled change of the service flag. Example, my Monday hours are 8:00 AM to 5:00 PM and my Tuesday hours are 8:00 AM ti 5:00 PM. I have to leave at 3:00 PM Monday so I press the button that sets the auto service flag. It stays set until I manually change it be pressing the button or until 8:00 AM Tuesday morning when it changes based on the schedule of the service flag.
I could instruct the customer to dial the service flag, give them the pin code and have them change the time for that day or they could just press the button.
-
In version 5.5.0 at the domain level when changing "Delete the call recording files along with the CDR" from Default to either Yes or No you can't set it back to Default.
-
-
I am a little confused on this feature. Can you elaborate please.
I thought that the feature was that when you dialed *98*1 the system would let you record that message, press # and use, review or delete the message. Dialing *98*1 should allow you to record the message just like it would if you hit the voicemail message on the phone.
-
As I read the release notes again I see that I misinterpreted what the feature was.
I thought the feature allowed you to turn the flag on or off like one would do with a manual service flag by just dialing the service flag.
I still think there should be a way to just dial the service code like one would change a manual service code. Requests have been made for this feature for years.
-
We just upgraded our test server to 5.5.0.
I setup an automatic service flag and a button on my Snon D715 to change the service flag. When I hit the button the flag does not change and I get the message "We're sorry but you are not allowed to place this call.
As future enhancements I think it would be a good idea to add the ability to turn the flag on/off from the web GUI and to have a field for permissions and what tone to play when the flag is manually changed.
Basically it should have the same fields as a manual service flag.
-
I think I discovered a bug in the Auto Attendant. I have tested this on both version 5.4.0 and 5.4.1a. We will be upgrading our test server to 5.5.0 this weekend so I will test on that version and report back.
When you create a new auto attendant the default for the following features in the IVR tab is set to off
Say "Please enter the extension number": Off
Say "For our dial by name directory, press [number]" (only if the dial by name number has been set): Off
Say "Or remain on the line for general assistance" (only if the redirect on timeout is active): OffI have the dial by name set and the redirect timeoue active.
When you call the auto attendant the system still says "Please enter the extension number" and "For our dial by name directory, press [number]" and "Or remain on the line for general assistance" (only if the redirect on timeout is active):
If you set these to on, save and then set them to off and save the system does not play those messages.
It seems like on creation of the new auto attendant that the default state of off is not set.
-
What PBX version are you running? Vodia adds the new phones with new PBX versions. Your version may be one before the new phones were available.
I wish there was some documentation on how to add new phones without having to upgrade the PBX version.
-
It would be a nice if the call recording pages and the call log/call history had the following enhancements at both the domain level and for the individual users.
1. Make the link for the page that you are currently viewing bold or stand out from the other links in some way. Right now there is no way to tell what page you are on.
2. Next, Previous, First and Last links that you can click on to get to the next, previous, first and last pages of the report.
3. Export button to download the call log as a CSV file.
-
It would be useful to be able to play a VM from the mailbox tab of the extension when you are logged in as an admin or domain admin.
-
-
I use and ACD as the final stage of a hunt group all the time. Works fine.
What is happening when you try to add the ACD to the hunt group? Are you getting an error?
-
The beep is provided by the phone. You will need to disable it on the phone.
-
Is there any documentation on the location feature?
-
Why would the global level need to have to override the domain level?
It would be better if the order would be a single phone, the domain and then the global level.
-
It would be useful to be able to specify how long to keep CDR and call recordings per domain rather than at the server level.
-
Seems like the only option right now is a conference room.
Other than having to transfer the caller to the conference and dial back into the conference what part of a conference room would not work? Just curious.
-
madyan, exactly what are you trying to accomplish? Would a conference room not work for this use case?
-
I think you are trying to use barge in for something it is not designed to do. A conference room seems more applicable to this use case.
-
The only extensions that can barge in are the extensions you specifically give permission to barge in by listing them in the "Barge into calls of the following extensions" under the Permission tab. By default no extensions are allowed to barge in or use teach mode or listen mode.
-
We are upgrading our servers from 5.2.5 to 5.4.0. On 5.4.0 it looks like the name of the firmware config XML file was changed from snom_3xx_fs.xml vs. snom_firmware.xml.
The upgrade is causing problems with any extension that has a custom snom_3xx_fs.xml because during the upgrade from 5.2.5 to 5.4.0 the snom_3xx_fs.xml was not changed to snom_firmware.xml for any domain or phone specific config file. The problem this is causing is that phones are rebooting and requesting the firmware file and the server does not recognize the legacy snom_3xx_fs.xml at the domain or phone level so it is handing out the server level snom_firmware.xml file causing the phones to load incorrect firmware images.
These are multi-tennent systems with 50 to 100 domains per server and perhaps 750 to 1000 phones on each server. Is there any quick way to find and replace all the snom_3xx_fs.xml files with snom_firmware.xml? It will be a lot of work to check each domain and each phone to determine if it has a custom snom_3xx_fs.xml that needs to be replaced with snom_firmware.xml. This will require us to manually check 1000s of phones.
Perhaps in the future the upgrades can take into account the types of changes that can affect 1000s of phones.
-
snomonepbx, my comment is directed at Vodia and not necessarily you since I do not think you work for Vodia.
-
Do you have an M700 in house to test on and can you verify that it is working? I see in the release notes for PBX 5.2.5 it says that support was added for M700.
https://vodia.com/doc/releasenotes525
What level of support for automatic provisioning of the snom M700 does the PBX support? Can I expect that I can deploy an M700 the same way I deploy a Snom 720?
-
Here is the document I am using to configure
https://vodia.com/documentation/snom_m700.pdf
Here are some logs from the M700 base
loc2 .Debug 1970-01-01T00:00:00Z 173-[ Loader status at boot: ff ff ff ff ff ]
NWK .Info 1970-01-01T00:00:01Z 173-[ ETH: Link down]
loc5 .Warn 1970-01-01T00:00:01Z 173-[ Link down on eth0]
loc3 .Debug 1970-01-01T00:00:01Z 173-[ SrtpInit]
NWK .Info 1970-01-01T00:00:04Z 173-[ ETH: Link up]
loc5 .Not 1970-01-01T00:00:04Z 173-[ Link up on eth0]
loc5 .Not 1970-01-01T00:00:04Z 173-[ Running 100Mb/s on eth0]
loc5 .Not 1970-01-01T00:00:04Z 173-[ DSP module not detected.]
NWK .Info 1970-01-01T00:00:07Z 173-[ ETH: Delta Link down/up 3s]
NWK .Info 1970-01-01T00:00:07Z 173-[ ETH: Running 100Mb/s]
NWK .Debug 1970-01-01T00:00:07Z 173-[ FNS_IF_EVENT_ADDRESS_READY]
NWK .Debug 1970-01-01T00:00:07Z 173-[ SIP_SERVER_OPTION#120 Not Found]
NWK .Info 1970-01-01T00:00:07Z 173-[ DHCP Enabled]
NWK .Info 1970-01-01T00:00:07Z 173-[ IP Address: 192.168.10.185]
NWK .Info 1970-01-01T00:00:07Z 173-[ Gateway Address: 192.168.10.1]
NWK .Info 1970-01-01T00:00:07Z 173-[ Subnet Mask: 255.255.255.0]
NWK .Debug 1970-01-01T00:00:07Z 173-[ TFTP boot server not set by DHCP. Using Static.]
NWK .Info 1970-01-01T00:00:07Z 173-[ DHCP Discover completed]
loc3 .Info 1970-01-01T00:00:08Z 173-[ Certificate issued for "MAC_ADDRESS_OF_M700" by "Snom Technology AG"]
loc3 .Info 1970-01-01T00:00:08Z 173-[ Firmware Version 03.55 Branch 0016]
loc3 .Info 1970-01-01T00:00:08Z 173-[ MAC=MAC_ADDRESS_OF_M700, SER= 00000, HW=255]
loc3 .Info 1970-01-01T00:00:08Z 173-[ Stun detection disabled]
loc5 .Not 1970-01-01T00:00:08Z 173-[ Running 100Mb/s on eth0]
loc3 .Debug 1970-01-01T00:00:08Z 173-[ LDAP: TCP Ready]
loc5 .Not 1970-01-01T00:00:09Z 173-[ SIPSIP: hUa#980f11 relation to UA#30 created]
loc3 .Info 1970-01-01T00:00:09Z 173-[ RemCfg: Time not set yet - deferring provisioning]
loc5 .Not 1970-01-01T00:00:10Z 173-[ [10] Trel accept called from task 7]
loc5 .Not 1970-01-01T00:00:10Z 173-[ [10] Trel TrelAccept success. Listening on port 10010]
loc0 .Info 1970-01-01T00:00:11Z 173-[ DECT master mode]
loc3 .Info 1970-01-01T00:00:19Z 173-[ RemCfg: Time not set yet - Provisioning using TLS might not work]
loc3 .Info 1970-01-01T00:00:19Z 173-[ RemCfg: Checking for settings]
loc3 .Info 1970-01-01T00:00:19Z 173-[ RemCfg: Attempting fetch of file: tftp://ADDRESS_OF_PBX/snomM700.htm]
loc6 .Crit 1970-01-01T00:00:28Z 173-[ Critical Slow DNS answer time: 9s]
loc3 .Info 1970-01-01T00:00:28Z 173-[ RemCfg: Error loading file]
loc3 .Info 1970-01-01T00:00:28Z 173-[ RemCfg: Attempting fetch of file: tftp://ADDRESS_OF_PBX/snomM700-MAC_ADDRESS_OF_M700.htm]
loc3 .Info 1970-01-01T00:00:28Z 173-[ RemCfg: Error loading file]
loc3 .Info 1970-01-01T00:00:28Z 173-[ RemCfg: Attempting fetch of file: tftp://ADDRESS_OF_PBX/snomM700-firmware.htm]
loc3 .Info 1970-01-01T00:00:28Z 173-[ RemCfg: Error loading file]
loc3 .Info 1970-01-01T00:00:28Z 173-[ RemCfg: Attempting fetch of file: http://ADDRESS_OF_PBX/snomM700.htm]
loc3 .Info 1970-01-01T00:00:28Z 173-[ RemCfg: Error loading file]
loc3 .Info 1970-01-01T00:00:28Z 173-[ RemCfg: Attempting fetch of file: http://ADDRESS_OF_PBX/snomM700-MAC_ADDRESS_OF_M700.htm]
loc3 .Info 1970-01-01T00:00:28Z 173-[ RemCfg: Error loading file]
loc3 .Info 1970-01-01T00:00:28Z 173-[ RemCfg: Attempting fetch of file: http://ADDRESS_OF_PBX/snomM700-firmware.htm]
loc3 .Info 1970-01-01T00:00:28Z 173-[ RemCfg: Error loading file]
loc3 .Info 1970-01-01T00:00:28Z 173-[ RemCfg: Attempting fetch of file: https://ADDRESS_OF_PBX/snomM700.htm]
loc3 .Info 1970-01-01T00:00:28Z 173-[ RemCfg: Error loading file]
loc3 .Info 1970-01-01T00:00:28Z 173-[ RemCfg: Attempting fetch of file: https://ADDRESS_OF_PBX/snomM700-MAC_ADDRESS_OF_M700.htm]
loc3 .Info 1970-01-01T00:00:28Z 173-[ RemCfg: Error loading file]
loc3 .Info 1970-01-01T00:00:28Z 173-[ RemCfg: Attempting fetch of file: https://ADDRESS_OF_PBX/snomM700-firmware.htm]
loc3 .Info 1970-01-01T00:00:28Z 173-[ RemCfg: Error loading file]
loc3 .Info 1970-01-01T00:00:28Z 173-[ RemCfg: No setting server offered via SIP PNP]
loc3 .Info 1970-01-01T00:00:28Z 173-[ RemCfg: No setting server offered in DHCP]
loc3 .Info 1970-01-01T00:00:28Z 173-[ RemCfg: Provisioning completed]
loc3 .Info 1970-01-01T00:00:28Z 173-[ UpdateAllTimestamps]
loc3 .Info 1970-01-01T00:00:28Z 173-[ RemCfg: Attempting fetch of file: ]
Auth .Info 1970-01-01T00:00:28Z 173-[ No flash certificates found]
loc6 .Info 1970-01-01T00:00:28Z 173-[ Multi cell Disabled]
loc2 .Debug 1970-01-01T00:00:28Z 173-[ PP FWU mail handler FWU_UPDATE_PP_INFOS]
loc2 .Debug 1970-01-01T00:00:28Z 173-[ PP FWU mail handler FWU_UPDATE_PP_INFOS]
loc7 .Info 1970-01-01T00:00:29Z 173-[ DECT Mode: US]
loc7 .Info 1970-01-01T00:00:29Z 173-[ System Mode: (a4/51)]
loc7 .Info 1970-01-01T00:00:29Z 173-[ Normal Reboot]
loc7 .Info 1970-01-01T00:00:29Z 173-[ DECT protocol delay timer started (single cell)]
loc6 .Crit 1970-01-01T00:00:37Z 173-[ Critical Slow DNS answer time: 9s]
loc3 .Info 1970-01-01T00:00:37Z 173-[ RemCfg: Error loading file]
loc3 .Info 1970-01-01T00:00:37Z 173-[ RemCfg: Provisioning PhoneBook completed]
loc2 .Debug 1970-01-01T00:00:38Z 173-[ PP FWU mail handler FWU_UPDATE_PP_INFOS]
loc7 .Info 1970-01-01T00:00:44Z 173-[ DECT protocol activated, delay passed (single cell)]
loc2 .Debug 1970-01-01T00:01:08Z 173-[ PP FWU mail handler FWU_UPDATE_PP_INFOS]
loc2 .Debug 1970-01-01T00:01:38Z 173-[ PP FWU mail handler FWU_UPDATE_PP_INFOS]
loc2 .Debug 1970-01-01T00:02:08Z 173-[ PP FWU mail handler FWU_UPDATE_PP_INFOS]
loc2 .Debug 1970-01-01T00:02:38Z 173-[ PP FWU mail handler FWU_UPDATE_PP_INFOS]
loc2 .Debug 1970-01-01T00:03:08Z 173-[ PP FWU mail handler FWU_UPDATE_PP_INFOS]
loc2 .Debug 1970-01-01T00:03:38Z 173-[ PP FWU mail handler FWU_UPDATE_PP_INFOS]
loc2 .Debug 1970-01-01T00:04:08Z 173-[ PP FWU mail handler FWU_UPDATE_PP_INFOS]
loc2 .Debug 1970-01-01T00:04:38Z 173-[ PP FWU mail handler FWU_UPDATE_PP_INFOS]
loc2 .Debug 1970-01-01T00:05:08Z 173-[ PP FWU mail handler FWU_UPDATE_PP_INFOS]
loc2 .Debug 1970-01-01T00:05:38Z 173-[ PP FWU mail handler FWU_UPDATE_PP_INFOS]
loc2 .Debug 1970-01-01T00:06:08Z 173-[ PP FWU mail handler FWU_UPDATE_PP_INFOS]
loc2 .Debug 1970-01-01T00:06:38Z 173-[ PP FWU mail handler FWU_UPDATE_PP_INFOS]
loc2 .Debug 1970-01-01T00:07:08Z 173-[ PP FWU mail handler FWU_UPDATE_PP_INFOS]
loc2 .Debug 1970-01-01T00:07:38Z 173-[ PP FWU mail handler FWU_UPDATE_PP_INFOS]
loc2 .Debug 1970-01-01T00:08:08Z 173-[ PP FWU mail handler FWU_UPDATE_PP_INFOS]
loc2 .Debug 1970-01-01T00:08:38Z 173-[ PP FWU mail handler FWU_UPDATE_PP_INFOS]
loc2 .Debug 1970-01-01T00:09:08Z 173-[ PP FWU mail handler FWU_UPDATE_PP_INFOS]
loc2 .Debug 1970-01-01T00:09:38Z 173-[ PP FWU mail handler FWU_UPDATE_PP_INFOS]
loc2 .Debug 1970-01-01T00:10:08Z 173-[ PP FWU mail handler FWU_UPDATE_PP_INFOS]
loc2 .Debug 1970-01-01T00:10:38Z 173-[ PP FWU mail handler FWU_UPDATE_PP_INFOS]
loc2 .Debug 1970-01-01T00:11:08Z 173-[ PP FWU mail handler FWU_UPDATE_PP_INFOS]
loc2 .Debug 1970-01-01T00:11:38Z 173-[ PP FWU mail handler FWU_UPDATE_PP_INFOS]
loc2 .Debug 1970-01-01T00:12:08Z 173-[ PP FWU mail handler FWU_UPDATE_PP_INFOS]
loc2 .Debug 1970-01-01T00:12:38Z 173-[ PP FWU mail handler FWU_UPDATE_PP_INFOS]
loc2 .Debug 1970-01-01T00:13:08Z 173-[ PP FWU mail handler FWU_UPDATE_PP_INFOS]
loc2 .Debug 1970-01-01T00:13:38Z 173-[ PP FWU mail handler FWU_UPDATE_PP_INFOS]
loc2 .Debug 1970-01-01T00:14:08Z 173-[ PP FWU mail handler FWU_UPDATE_PP_INFOS]
loc2 .Debug 1970-01-01T00:14:38Z 173-[ PP FWU mail handler FWU_UPDATE_PP_INFOS]
loc2 .Debug 1970-01-01T00:15:08Z 173-[ PP FWU mail handler FWU_UPDATE_PP_INFOS]
loc2 .Debug 1970-01-01T00:15:38Z 173-[ PP FWU mail handler FWU_UPDATE_PP_INFOS]
loc2 .Debug 1970-01-01T00:16:08Z 173-[ PP FWU mail handler FWU_UPDATE_PP_INFOS]
loc2 .Debug 1970-01-01T00:16:38Z 173-[ PP FWU mail handler FWU_UPDATE_PP_INFOS]
loc2 .Debug 1970-01-01T00:17:08Z 173-[ PP FWU mail handler FWU_UPDATE_PP_INFOS]
loc2 .Debug 1970-01-01T00:17:38Z 173-[ PP FWU mail handler FWU_UPDATE_PP_INFOS]
loc2 .Debug 1970-01-01T00:18:08Z 173-[ PP FWU mail handler FWU_UPDATE_PP_INFOS]
loc2 .Debug 1970-01-01T00:18:38Z 173-[ PP FWU mail handler FWU_UPDATE_PP_INFOS]
loc2 .Debug 1970-01-01T00:19:08Z 173-[ PP FWU mail handler FWU_UPDATE_PP_INFOS]
loc2 .Debug 1970-01-01T00:19:38Z 173-[ PP FWU mail handler FWU_UPDATE_PP_INFOS]
loc2 .Debug 1970-01-01T00:20:08Z 173-[ PP FWU mail handler FWU_UPDATE_PP_INFOS]
loc2 .Debug 1970-01-01T00:20:38Z 173-[ PP FWU mail handler FWU_UPDATE_PP_INFOS]
loc2 .Debug 1970-01-01T00:21:08Z 173-[ PP FWU mail handler FWU_UPDATE_PP_INFOS]
snom deskphone PNP support
in snom Phones
Posted
I know the D725 and D715 are supported in version 5.4.0. Never used a D765. The D3xx models are not available in the USA right now.