Jump to content

Michael D

Customers
  • Posts

    288
  • Joined

Posts posted by Michael D

  1. I wouldn't create sub accounts for the different companies , it will create the need for 10 digit dialing and incur pstn costs for each call.
    Also, creating a sip user per company will incur device costs (unless that is in your favor)
    We use Karl A's method mentioned "prepend"
    for example, one of my partners has an old vonage number he ported over. He can see "VON" on the phone screen letting him know it is vonage, not his normal calls to his DID.

    MD
  2. First off, Excellent job getting the Branding App Launched!


    I'm trying to determine why I cannot create Branding of my Reseller Sub accounts


    See diagram :





    I get this when I try to set up branding under the sub account:




    This is possible in the Kazoo UI.

    Am I doing this incorrectly?


    Thank you


    MD
  3. Folks,
    I have been testing BLFs with the MonsterUI/Advanced Provisioner.

    The results seem to be the same on both Yealink T22 and Polycom IP 550s

    Basically, you add the numeric Extension number to the address field of the feature key/line key
    Like this:


    Seems to work consistently when the account was created in Monster

    If the account was added in Kazoo UI, but the source phone existed in the Kazoo UI/Call flow previously, does not work as expected. For example, we recreated our users/devices in the monster ui with advanced provisioner. If any of these previously existing phones are added as a BLF SOURCE, it does not work
    If we create a new user/device in Monster/AdvProvisioner it does work as the Source for a BLF
    The destination phone can be a preexisting kazoo Ui phone

    What is the best practice for implementing BLFs?

    Should the BLF address field be the numeric extension?
    Should the BLF address field be the alpha numeric sip username (user_xyzx?)
    If the user has multiple devices, will blf reflect all device status?

    Thanks

×
×
  • Create New...