Jump to content

Vernon

Members
  • Content Count

    44
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Vernon

  • Rank
    Advanced Member

Recent Profile Visitors

2,346 profile views
  1. Hello, I was just wondering how the automatic blacklist operates on the latest version. I've had odd results in the testing environment. I have two test extensions i use to configure phones either through provisioning or manually to test features. Every now and then i may get the SIP password wrong and then i spend 20 minutes troubleshooting the phone trying to figure out why it won't provision, only to find out that it's been black listed, likely due to the wrong SIP password entry. The other test phone works fine since the blacklist seems to block individual ports and creates a listing for the extension and domain it was created so it's easy to find. I just want to understand the logic behind the extreme effectiveness of the blacklist. Just to provide an example i'm able to loop a phone into a provisioning cycle where i can force the PBX to regenerate the same config file 10,000 times and there's nothing in place that stops this. Is there a way to increase the amount of failed registrations attempts the PBX can accept before it ultimately blacklists the IP/device? Thank you
  2. Hello, There is a minor bug/oversight with how the call answer feature works on the app. Typically when a call comes in you'll see a notification pop out from windows, and you can see the pending call in your app. However once the notification goes away/times out, so does the ability to answer the call. So you have about 5 seconds to pick up the call. The app still rings the full duration but you just don't have the opportunity to pick up the call. I tested this by hovering over the notification from windows and the call inside the application stayed for as long as the notification was open. The easiest way to circumvent this bug is to disable the Windows notification alerts for the application, only drawback is you won't get a sliding notification of incoming calls. This was tested on the latest app 1.2.6 i think
  3. In this particular event i think it's better to restrict the device rather than the PBX since most don't support these types of actions by design. I did have a chance to try to test out the restrictive dial plan to not allow for extension/star code dialing but it doesn't have any effect because internal calls do not reach the dial plan for them to take effect. Since you're using Snom's they have an expression dial plan string page: http://wiki.snom.com/Features/Dial_Plan/Regular_Expressions The last one dictates on how to block dialing, since you only want outbound, you can substitute it with 1 instead of 9 as in the example. This way you can just send out all calls as 1xxx...etc. Since you're not stripping any digits, even if they were to dial an internal extension with a 1(xxx) it won't go anywhere since 1xxx is not a valid extension, same with starcodes. The example string from the help page: |^[^9]([0-9]{0,})$|sip:blocked\@\d
  4. Hello, Was testing some of the features for voicemails and while this is not critical or an issue per say, i felt like it should be brought up. So after listening to a voicemail you have various options, option 5 gives you the details of the calls. Before the new version it gave you the following information: Date of voicemail Time of voicemail The call From However with the new version the structure has changed: Date of voicemail Time of voicemail The call from The call To* Perhaps i haven't tested this in the correct environment it was designed for, but it seems redundant to let the user know that the voicemail left in their mailbox was left for their number. As an analogy imagine your personal cellphone voice tree announcing to you that "Voicemail 123 has been left for your number 456" Is there a way to modify this functionality or perhaps tweak it in some way.
  5. I'll attach an image to help better explain it. For the LDAP i tried with a Snom 745 and 725 ( 8.9.3.60 ). The domain address book LDAP works perfectly fine on these phones and picks up entries as it should, but when editing an address book from the user level and reprovisioning a phone no extra contacts appear. I've changed the setting to personal address book only and didn't see any new entries appear. I could try with a Yealink phone model and see if there's any difference
  6. Thanks for your reply, Would you be able to clarify on Point 2? What does it mean to end that option from being selected? Selected from where? I refreshed the page with both settings and i haven't seen any difference. 4. What i meant here is that adding entries to the address book only stays within the user level address book. If you were to provision a phone it would pick up contacts from the domain address book which doesn't contain any user level entries. Though i see under Extensions -> Address Book, there is a setting for the following options: Default, Domain+personal, Domain only, Personal only. I've provisioned a phone with all variations of this setting and didn't notice any changes on the phone. P.S What is the default Address Book setting and where is it set from?
  7. Hello, I've been testing some of the features of the User level in the PBX and noticed some bugs and have a couple of questions. Q: Question B: Bug? 1.Q: When adding an address book entry in the Web Attendant console, this entry doesn't seem to reflect in the domain/user address book. Is this entry stored only on the User Level's page? 2.Q: The third symbol of the address book doesn't indicate what it does. First is delete entry, second is to edit the entry, third, i'm assuming, is to block/allow the contact? 3.B: This might be related to the 2nd question. When adding a contact and setting the contact on the "Black List", after saving the entry and refreshing the page it will turn into a Regular contact. 4. Q: Will the address book functionality of the user interface be expanded to allow for more control over the system? For example it would be nice to let users manage their address book without having to give them full PBX access or maintaining ticket queues to add/edit entries. This was all tested on the latest Vodia IO, reading the past patch notes i wasn't able to see any notes addressing these issues/questions. Thank you
  8. Hello, I have a quick question. When creating domains and editing it the voicemail transcription option will be enabled by default. When navigating to the E-mail -> Notification and setting the default option to "Off", it will still create new domains with the setting enabled. Which setting takes priority? Right now it looks like you still have to edit individual domains to disable the transcription each time a domain is created
  9. You can try utilizing the CO lines for a specific trunk, then when it runs out of lines it should prioritize the busy routing you've created for that specific trunk. That way you can keep your attendant without having to use any other accounts.
  10. Hi, I'm trying to figure out how to best approach a scenario where a manager has to take over calls. Let's say Manager runs a call center and Rep A received Chatty Client B. CCB has frustrated RA to a point where heated words may be said. Manager wants to be able to grab the call from RA without having to use parks/holds. I know there's a feature for call barge in, but that would still leave RA on the line, is there a possibility of just completely taking the call over? To summarize the feature would be a forced transfer.
  11. I think he's referring to the example in the paging group under "Destination" From your Wiki: https://doc.vodia.com/paginggroups Under "Setting up the Paging Account" Destination (e.g. "40 41 5*") The example destination makes it look like it would page all extensions in the 5x range.
  12. Are there any plans to reintroduce the button templates for the SPA series phones? SPA504, 509, 525. Seems the only Cisco phones that have a template are the CP series and the SPA 112/190 (which have empty button profiles) This is on version 61.1 The provisioning still works just can't modify any of the buttons.
  13. For those looking for a possible work-around for the time being is to copy/paste the phone-MAC.xml file from the generated folder into the extensions custom phone xml. e.g snom_745_phone.xml...etc It seems like the first extension in the list gets the settings for both extensions, while the second identity phone-MAC.xml only generates for itself. It may not be pretty if it's for the whole system, but for individual extensions it should work well enough.
  14. Hello, I was just wondering if the Shared Line/ co line functionality will be making a return in the new version 62? I remember reading in one of the blog posts that the shared line will cease to exist in version 60+, but i can see from the new button list in version 61 that there is allocation for co lines. Provisioned a 320 with the buttons being co lines and accounts co1, co2, co3...etc Similar to how it's described in your wiki: https://doc.vodia.com/trunk_colines, but doesn't work like the older versions. Just to recap, in the past people would press a shared line and the button lit up on every phone to indicate the line is in use. On version 61.1 the button provisions it as a BLF that enables monitoring, but the line can't be selected so this does not have much usage. The value is provisioned as sip:co1@test@testdomain;user=phone>|*87. I'm guessing the value is provisioned in such a fashion to push for the usage of park orbits. Thank you
  15. Doesn't seem like that label template affects the 745. I've tried making it empty or even putting other unrelated information in there to see if it would affect it. Always seems to come up the same, it's account + name in the label. Is there another configuration where the 745 would be picking up the private line label? Giving the label an empty character/space simply forces that label to be empty.
×
×
  • Create New...