Jump to content

esoare

Moderators
  • Posts

    857
  • Joined

  • Days Won

    37

Posts posted by esoare

  1. 14 minutes ago, Darren Schreiber said:

    Well the beta strategy I listed above would likely give enough time to find any huge bugs. To roll-back I suspect we could just remove the bad firmware which would change the default/Current one.

    However frankly the problems have been amplified not by a need to roll back (the manufacturers have been pretty good with fixing actual bugs quickly) but more with an inability to quickly release & move forward without being disruptive. So I feel a bit of this nervousness is from being burned in the past in ways that may not happen in the future.

     

    I would agree with your statement of nervouseness being do to past burns and scarring. 

    I guess something that wasn't mentioned, and I just thought of since you posted your reply Darren, is the following:

    There would be an announcement of the new firmware available in advanced provissioner.

    Reseller's would have an opportunity to select a few customers with various needs to upgrade their phones. 

    If there are reports with said customer's we open service tickets that could be tracked to the new firmware.

    The Current wouldn't be forced without those being closed. (I'm not making a rule here, just a suggestion.) Obviously a "bad firmware" wouldn't be forced as current. 

    If no reports, then the Firmware Current change is announced. 

    And we move on with life. 

  2. 3 minutes ago, Plau said:

    So, I wasn't very clear in my explanation earlier. My bad.

    There are multiple "logo" settings in the config file. The one you see as "Logo" in Advanced Provisioner sets the image for the idle screen. That one specifically isn't supported by the models I listed in my previous post. This is the setting I'm talking about that is set through Advanced Provisioner: http://support.yealink.com/faq/faqInfo?id=219

    The Wallpaper setting, which is what esoare has posted about, is not something that can be set through Advanced Provisioner at this time. I'm assuming that Jack set the Wallpaper for the T29G through the phone's web UI.

    So a better name would be "IDLE LOGO" OR a better description to show it's kinda the screen saver? 

    I guess IF you get the Wallpaper setting done, it would be called Wall Paper. :) ? If the LOGO isn't supported, should that not even be an option on the models that don't support it? 

    esoare

     

  3. I found this on Yealink's website. Doesn't have the latest phones, but it's worth noting. 

    Quote

    http://support.yealink.com/faq/faqInfo?id=182

    Description

     

    Introduction of different specifications of logo.

     

    Cause

     

    Sometimes, when we want to compare the logo specifications, we need to open many guides for it.

    So this document can let our customer be more clear about specification of logo in all types.

     

    Resolution

     

    Please refer to the following doc:

    Phone Type

    Logo Display

    Logo File Format

    Resolution

    Single File Size

    Total Files Size

    SIP-T28P

    236*82 pixel

    .dob

    <=236*82 2 gray scale

    /

    <=100KB

    SIP-T26P

    132*64 pixel

    .dob

    <=132*64 2 gray scale

    /

    <=100KB

    SIP-T22P

    132*64 pixel

    .dob

    <=132*64 2 gray scale

    /

    <=100KB

    SIP-T20P

    Text log

    /

    /

    /

    /

    SIP-T48G

    Wall Paper

    .jpg/.png/.bmp

    <=800*480

    <=5MB

    <=20MB

    SIP-T46G

    Wall Paper

    .jpg/.png/.bmp

    <=480*272

    <=5MB

    <=20MB

    SIP-T42G

    192*64 pixel

    *.dob

    <=192*64 2 gray scale

    /

    /

    SIP-T41P

    192*64 pixel

    *.dob

    <=192*64 2 gray scale

    /

    /

    SIP-T29

    Wall Paper

    .jpg/.png/.bmp

    <=480*272

    <=5MB

    <=20MB

    SIP-T27

    240*120 pixel

    *.dob

    <=240*120 2 gray scale

    /

    /

    SIP-T23

    132*64 pixel

    *.dob

    <=132*64 2 gray scale

    /

    /

    SIP-T21P E2

    132*64 pixel

    *.dob

    <=132*64 2 gray scale

    /

    /

    CP860

    192*64 pixel

    *.dob

    <=192*64 2 gray scale

    /

    /

    SIP-T21P

    132*64 pixel

    *.dob

    <=132*64 2 gray scale

    /

    /

    SIP-T19P

    132*64 pixel

    *.dob

    <=132*64 2 gray scale

    /

    /

    SIP-T49G wall paper *.jpg/*.png/*.bmp 1280*800 <=5MB /

     

    More Information

     

    Null

     

    Product Type
    CP860 , SIP VP-T49G , SIP-T48G , SIP-T46G , SIP-T42G , SIP-T41P , SIP-T29G , SIP-T27P , SIP-T23G , SIP-T23P , VP530 , SIP-T38G , SIP-T32G , SIP-T28P , SIP-T26P , SIP-T22P , SIP-T21P , SIP-T20P , SIP-T19P
    Version
    V72, V73 and V80
     
     

    Yealink logo file types.JPG

  4. On 7/30/2017 at 9:43 PM, esoare said:

    Plau, 

    I see that the upgrade happened. 

     

    An FYI, the main account is appearing on two buttons.built a new Yealink T42G and T42Gs, and this happens. 

    It happened on the sandbox, but I failed to report it.

    Hope this is a quick bug fix. 

    Thanks, 

    Esoare

     

    FYI. If you are deploying and have the issue with the two buttons showing up for the first account. 

    You can set the Combo Key 2, to N/A in Advanced Provisioner, (or something else, if you use that) until the bug gets fixed. 

    esoare

  5. So I wan to find out who owns a specific analog line (could be a DID also) The customer that I am porting has it on their website. The customer's Comcast bill doesn't show it. The customer did a CSR on their main number, but this fax line didn't show on that either. 

    Is there a resource, that I can place a number in and get who provides the service for the number? 

    Anyone want to share? :)

  6. Question on this. With the e911 CLID, would we want that DID (which should probably be different than a: the main account number, b: the location number) to ring ALL the phones at that location? 

    Kinda, like a default e911 group for that DID number, would always ring all phones.

    An alternative, but more complex. would be to do what Cisco does. Have 1 or 2 DID's set for a location, with the addresses programmed. When a device dials 911, it picks the first DID for outgoing CLID, and dials 911. If the call gets disconnected, the 911 operator can call back the DID, and it will RING that specific Device. If a second person call 911, the same is accomplished...

     

    My reasoning suggesting the default e911 DID ring Group, is that customers usually have a Menu Call flow for their main number, and it would be difficult for a dispatcher to reach whoever called 911, if the 1st call to 911 was disconnected.

  7. 1 hour ago, JR^ said:

    Thanks for the input, will definitely keep it in mind if/when we build something for CDRs :) 

    We're trying to come up with tools we can do with the existing APIs we have. Some features are hard to build without new back-end work (such as searching...)!

     

    Forget searching! (Sorry to throw you under the bus Tuly! ;D) Glad your looking at getting something going. 

    PLEASE really consider doing the Automated reports! The less a customer/re-seller has to do with these, the better.

  8. I would also like to add. That to me. CDR Reports is different than Billing. 

    CDR Reports should give customer reports that they are interested in. 

    Incoming/Outgoing on Account, DID's, Groups, Users, Devices, with a range of Dates, and allow for automatic reports to show up in their email box, so that the customer can see how they are doing. 

    8) An interesting CDR Report, would be for Month over Month, Week over Week comparison's. ?Maybe multiple?

    i/e: In July compared to June, we received 200 more calls incoming on a Specific DID. Wow! That must mean that our marketing with that DID, really worked! I wonder how it compares over the past 6 months? 

  9. I am really liking the new Forum!! 

    Most Awesome is the "Unread Content" that allows us to peruse what we missed in a short amount of time!! 

    I like that the heavy hitters (Developers that have clusters are posting here) since that allows us small fry's the ability to see what is being discussed. 

    Keep up the great work! 

    Another + to the design, layout + the Point system! ;)

    esoare

  10. On 7/31/2017 at 11:14 AM, JR^ said:

    I see a lot of interest about CDR Analytics! Out of curiosity, what are the CDR Analytics "stats" that you'd like an app to expose?

    1) Incoming / Outgoing Call Hours/Minutes for a whole account. - Allow for monthly, bi-weekly, weekly, daily (break out all 7 days with numbers) Custom Dates

    2) Incoming Call Hours/Minutes for a specific Phone number - Allow for monthly, bi-weekly, weekly, daily (break out all 7 days with numbers) Custom Dates

    3) Incoming/Outgoing Hours/Minutes for a multiple Users/Devices, like a Sales Group, or Service Group - Allow for monthly, bi-weekly, weekly, daily (break out all 7 days with numbers) Custom Dates

    4) Allow for all of the above, to be generated on a certain date (customer chooses) as a PDF and emailed to a user/admin

    5) CDR search page, where you can search filter by "originating number" "destination number" "caller ID name" "incoming" "outgoing" "date" "missed calls" "per extension or across the account"

    6) Make something pretty :) 

    7) Not needed right up, but it would be nice for historical stuff, maybe a year/two/three? BUT, save the CDR data over onto amazon/drive, so the Hosted DB doesn't get to big. 

     

    On 7/31/2017 at 0:23 PM, Tuly said:

    I made a call to a number that ends with 5555 last week, search for it,

    Tuly. 

    You can do that now in the User Portal...just type in 4 digits and you will see it..

     

    esoare

  11. 3 hours ago, Plau said:

    It didn't happen last week because I ended up finding a couple more issues and didn't have time to make a full announcement for the upgrade. We will be posting an announcement either today or tomorrow about the upgrade scheduled for this Friday along with release notes of changes and fixes to Provisioner, so look out for that update.

    p.s. I will keep an eye out for this. :)

  12. 3 hours ago, Plau said:

    You can provision it as a T42G, then later go into the Callflows App -> Devices and change the device type from T42G to T42S. Afaik, that's the only place to change a device type after it's been added.

    Plau,

    I wouldn't recommend that. I did the following, and the Phone was removed from Advanced Provisioner. 

    Built a Smart PBX using T42G template.
    After provisioning (which didn't look quite right)
    I changed the device type in Callflows/Devices to T42S.
    That removed the phone from advanced provisioner. 
    But the phone was in SmartPBX
    I Tried re-saving the Smart PBX device after making minor changes, but that did not work. 
    So, I would not recommend changing the Device type in CallFlows. :) 

    I'll hope for success this Friday. 

×
×
  • Create New...