Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Vernon

  • Rank
    Advanced Member

Recent Profile Visitors

2,455 profile views
  1. Hello, Thanks for your reply. I ended up playing around with it some more after my post and then read up on the new dial plan documentation. I did use the suggested 011* replacement pattern and setup the trunk with E.164 without leading + and it actually did resolve my issue with outbound calling. Testing it again I realized that I did not check for inbound calling. The inbound calls do show up and they do work, but PBX seems to add 011 to every incoming call in the CDR. So instead of seeing 416-xxx-xxxx, i now see 011416-xxx-xxxx. I mean it stil
  2. Hello, I'm trying to test with a trunk that can do "everything" that means local calling and international calling. I've so far been very successful in creating the trunks for local calling but i'm having some difficulties with the international part. I'm testing this on the latest version and i don't remember it functioning this way but maybe I'm wrong in this regard. So i create a generic trunk with no global number replacements and the system uses area code 1 for local calling and DID representation. Dial Plan 1: This is to catch all call
  3. The T43U has the EXP43 unit, which is used on the T43U, T46U and T48U. I followed the instructions and you are correct, i am able to manually change the model of the phone but the problem is that the next up Yealink model that has button configuration is the T46 which is a little different from the T42. This is the button configuration for a default T43U that's on the PBX right now. This is the button config for a T46. So in order for the T43u to be able to use the EXT button configurations they would always need to be c
  4. Hello, I've been testing the T43U unit and it does not have the possibility to edit the EXT/DSS key buttons on the button page even though the hardware can support it. I think the PBX may be tagging it as a T42 style unit after provisioning and prematurely removes the ability to edit those extra keys. While i don't actually have an EXP board plugged into the phone. I tested with some Snom phones and in the same scenario the pbx gave me the extra button options after provisioning.
  5. Not to try and resurrect an old thread but the posted picture of the beta application would be an excellent addition to the app.
  6. Hello, Yes I found that portion, but what it does not answer is if the auto-attendant has to be mapped *only* on the PBX or can the users utilize their own MS Teams Auto-Attendant. That's the part I wanted to confirm because looking at the MS Teams interface they do have an "Auto Attendant" page but i assume that since MS Teams does not have internal accounts like the PBX there wouldn't be a way to direct the calls to it.
  7. Hello, I recently watched your video on the Microsoft Teams integration and i just had a quick question about the inbound portion of the video. It's possible to assign the DID's to an extension and that'll ring on the MS Teams/ Desktop application, but my question is how does the PBX handle calls to an auto-attendant on MS Teams? The video and documentation wasn't very specific about these functionalities and i was just curious how far the integration goes. Thank you!
  8. Was testing the transcription on the latest build and it seems to break the transcription. From the logs I get the following error: [8] 13:04:00.086 Voicemail message is too long for transcription: 6s This error message appears even if the Maximum duration for transcription (s) under Notifications is set to a huge number, including leaving it blank. Downgrading to 66.0.4 doesn't produce this error message.
  9. The scenario I was looking at involves a user that works under appointments. For example in a bank (pre-COVID), you get your client to come in with you and you put yourself on DND so as to not be disturbed by calls or announcements. So in this particular case the user expects privacy but say management who has access to a paging group, decides to broadcast a message "Everyone, there's taco's and donuts in the staff room, feel free to take as many as you like". While it's not terribly inconvenient it could be seen as unprofessional in this type of environment. Looking at the Yeal
  10. Hello, I came across this little quirk, the PBX seems to bypass Yealink's DND functionality in order to page it. I've tried using the several custom settings the Yealinks have such as the Emergency DND Bypass but the PBX pushes through no matter what. Since the phones get provisioned and the DND status should sync up with the PBX, it should make sense that the PBX is able to ignore those phones/devices. It would be worthwhile to add the setting under the Extension permissions or as a setting on the paging group that will ignore devices/phones in DND.
  11. Just to add to this. Can confirm the functionality across different platforms. It does not seem to be relevant to the PBX version but more-so the app/web version and i assume the latest PBX versions run the latest web version of the app. I installed the v1.xx app and tested the parking orbit feature and it worked identical as in the pictures above, but the latest release from the MS store deviates from v1.xx with the issues present.
  12. 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 cre
  13. 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
  14. 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
  15. 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 t
  • Create New...