Jump to content

esoare

Moderators
  • Posts

    857
  • Joined

  • Days Won

    37

Posts posted by esoare

  1. I'll start off.

    I think the OTT App should:

    Allow for WhiteLabeling

    Allow dial out to customers with through the Cell Phone service using the USER's company DID for outgoing CLID, or the MAIN Business Number/Branch Business Number for the company.

    Allow for BLF of User's

    Allow for BLF of Device's

    Allow for Transfering to other User's, using Names/Extensions/Faces

    Have the User Portal Native

    Allow for Seeing Faxes / Transmitting Faxes (Need to get fax transmission on the User Portal eh? I know I can API that, but I want to GUI that)

    Allow access to the Cell Phone Contacts

    Allow access to the SmartPBX Directory - or - Other Company Directories

     

  2. On 3/15/2018 at 4:04 PM, Plau said:

    If you want Reseller settings applied to Accounts under Reseller2, then make changes to Reseller settings for Reseller2. Accounts will always inherit from the closest Reseller parent account. So, if you had something like

    Master -> Reseller1 -> Reseller2 -> Account1 -> Account2

                                        -> Reseller3 -> Account 3

                  -> Reseller4 -> Account4

                                        -> Account5

    All the Resellers inherit settings from Global/Cluster. Accounts 1 and 2 inherits settings from Reseller2. Account 3 inherits settings from Reseller3. Account 4 and 5 will inherit from Reseller3.

    No one inherits from Reseller1 because there are no accounts that is a child of Reseller1 and not a child of another Reseller account. This is also true if you set the Master account as a Reseller.

    I think a long time ago inheritance might have worked differently as our production cluster is setup with a MasterReseller account under the Master (superDuperAdmin) account. For organizational purposes, I can see the value of having a MasterReseller account, but as you can see, settings don't trickle down. It is confusing if you haven't been told about it. I did a talk about Inheritance in Provisioner at KazooCon 2 years ago, but never got around to writing a full documentation on how it works.

    3

    @Plau "Account 4 and 5 will inherit from Reseller3."

    Was this a typo and should say 'from Reseller 4'?

    esoare

  3. Just now, FASTDEVICE said:

    My development team completed an Excel addin for Tuly. Hopefully Tuly's clients are finding it very useful.  And our existing Chrome extension is going through a rewrite as a monster app.   

    All our addins (Excel, Outlook,) and browser extensions will soon be available on the Monster App Store. 

    @FASTDEVICE great to hear about the rewrite for the Monster App Store! 

  4. @Olaolu Abiodun That is what I thought happened. :)

    I also use it for inventory. I create Separate "servers" in RPS for each Customer/Site, so that I know where the phones are.... 

    The biggest issue (in my opinion, is that we don't know anymore what devices are at a site. If I delete a MAC from the Advanced Provisioner, that MAC addresses isn't recorded anywhere. It would be great to be sent an email, that says, "Hey this MAC address was removed from Advanced Provisioner/Smart PBX/Advanced Call Flow -> Devices, and you need to record that and place it in your RPS. 

    The Preference is the following. 

    Have a place to enter our RPS credentials. 

    Then Each Account/Sub-Account is created as a "Server" in RPS. And the MAC addresses are placed in RPS using that "Server". 

    This would be the IDEAL solution!

    Anyone else think so? Either UP Vote, or Heart this comment. 

  5. Anir,

    Do you have Advanced Provisioner working with your own cluster?

    Did you remove the offending phone from the network?

    Try to start the phone on a hub with a pc for troubleshooting / uploading to a "good" firmware (basic, but thought I would mention it) before connecting it to a live network again. You could also Factory Reset the phone. :)

    esoare

    p.s. I have run across this issue on the "hosted" platform before. In a pinch, try these options.

    1) If you have a cell phone, do tethering to a computer/laptop, and you can access the provisioner app again. 

  6. This might be a Auto Provisioner thing, to add the new range. The new range is 80-5E-C0 per the Yealink forum annoucement. 

     

    @Plau can you see about adding the new MAC range to the Yealink's? It looks like you will be getting a few support tickets if not :)


    http://forum.yealink.com/forum/archive/index.php?announcement-16.html

    Yealink has used MAC address segment which begins with the OUI 001565 for all the phone models, as the available number of the MAC address within this segment is running out, Yealink has initiated a new MAC address segment starts with 805EC0XXXXXX since September in 2017, while W52 BASE and T49 will keep using 001565 MAC address segment.

    Yealink has done the survey before the change and there is no need to worry as it won’t cause any problem.

    In some rare cases that few customers’ network/Auto provision servers/PBX might have configured the OUI 001565 as the identifier for Yealink models, please also add the new OUI 805EC0 as the identifier for Yealink, if you have such kind of settings.

    Please contact Yealink technical support if any question.

    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    Not sure about trusting the link below for MAC addresses, since it's not the official forum.

    http://www.adminsub.net/mac-address-finder/yealink

     

  7. To be more specific:

    2-14-18 the advanced provisioner was updated. My phones went to the "default" selected by 2600hz. I noticed that on the morning of 2-15-18, had to go in and modify all the devices indavidualy to get the new 88.20 firmware. 

    1 customer noticed they had issues on their T42S phones, because the firmware of 88.10 was grabbed by the phone... 

     

     

    If anyone else has T4xS phones, you may want to check the devices, so that they are not on the old firmware after the advanced provisioner update. 

    Esoare

  8. The BLF issue of being Green even though a user/device is on a call is still happening in Hosted. Evidently its on long calls... Have a ticket in to get that fixed up. 

    Will update when that is fixed. 

    2-14-18 the advanced provisioner was updated. My phones went to the "default" selected by 2600hz. I noticed that on the morning of 2-15-18, had to go in and modify all the devices indavidualy to get the new 88.20 firmware. 

    1 customer noticed they had issues on their T42Gs phones, because the firmware of 88.10 was grabbed by the phone... 

     

     

    If anyone else has T4xS phones, you may want to check the devices, so that they are not on the old firmware after the advanced provisioner update. 

    Esoare

×
×
  • Create New...