Jump to content

mattlandis

Members
  • Posts

    1,254
  • Joined

  • Last visited

Posts posted by mattlandis

  1. @Lucadef

     

    To answer the question of cost of Lync: as of Dec 2012, a Lync Server License costs $3700 plus CALS. See details:

    http://windowspbx.blogspot.com/2012/11/microsoft-lync-2013-availability-and.html

     

    Also, remember that this cost doesn't not include implementation, which can easily be as much as licensing for a small setup.

     

    The question immediately comes up, what about Lync Standard Edition (that used to be $699). The short answer is it now costs $3700, below are details:

    http://windowspbx.blogspot.com/2012/12/can-i-still-buy-install-lync-server.html

     

     

    @snomONE (admin)

    Since I've been busy with Lync implementations I've been a little sidetracked from snom ONE. I need to say (as someone else did on this thread) that technically snom ONE is an excellent product (so kudos there), but company stability of pbxnsip/snom ONE/vodia is extremely dissappointing, very confidence undermining and I'm sorry to see it.

  2. The link talks about the static mechanism of stopping the process, changing the xml and then starting it.

     

    The easy thing to do is to use the mechanism to change any global variable as explained here - http://wiki.snomone.com/index.php?title=Global_Configuration_File:

     

    So, you would login to the PBX as system admin and then type http://<pbx-ip>/reg_status.htm?save=save&out_of_dialog_options=true

     

    not sure if it is a bug, but when i ran the above, it indeed did at the "out_of_dialog_options" in the pbx.xml, but as false. i just changed it to true and it seems to stick now.

     

    weird.

     

    Thanks guys.

  3. This pertains to snom ONE 4.5.x

     

    #1- i think the MOS score Graphs on System, Trunks and Extensions is very good. Thanks!

     

    #Q2-Is there a way on a MOS graph to drill into the bad calls? If i see a chart with bad calls, first thing tech wants to do is see the details/who/what/when of bad calls...

    #Q3- Is there a way for the admin to get emailed the call details of a bad MOS call?

    #Q4- OR: if there are over XX calls with bad quality/ MOS score under XX, the admin get an email?

     

    #Q5- I see the "Call Log" now has a MOS score. Great! is there a way to drill into the MOS score details from call log?

    #Q6-what are other resellers doing to monitor call quality on remote snom ONE pbx's?

  4. hey matt! love your contributions and videos by the way..and you were spot on about calling this a uc client instead of an attendant console...boy a real attendant console would be FAR more extensive! queue management, orbits, agent routing..haha.

     

    again, agreed it is a step in the right direction. only thing is i don't see where they mention on the priority of this project...it is somewhat important to me because this can actually make/break it for my clients...the selling point on this feature alone makes my clients want to jump in. i did remember reading somewhere on a vote for the development of this but i believe it was old news from pbxnsip. we need to try to weed out the mixed information on the two...it is blended everywhere and sometimes there is no mention if the solution was for pbxnsip or snom one...anyways..

     

    i still haven't seen any visual voicemail on the client. maybe it wasn't in your video or i just overlooked it? (currently i (with my team) am working on an XML visual voicemail for the snom 3xx and 8xx series phones. the 7xx will be implemented at a later date. i will release it on site when it is fully functioning. i will be meshing this into the default autoprovision using the 8.4.35 fw.)

     

    Glad you like our work. ;-)

     

    priority: with snom you just wait. patiently.

     

    visual voicemail: this is something snom should do.

     

    If our clients need a strong PC client, visual voicemail and those types of things and more we are pointing them at Microsoft Lync.

  5. Ahhh ok. Our snom phones have no hard button for it. I think i'll use the star code. Thanks!

     

    Hal

     

    yes, snom 8xx, 3xx (Except snom 300) have a hard button.

     

    snom 7xx you can use a context/(one of four below screen) buttons.

  6. Hello

     

    Snom One was certified for OCS, but what about Lync. I havent found any information on whether Sonm One is or will be certified.

    Neither have I found any instructions on how to set it up. What I'm interestred in is to use Snom One as a trunk to gateway to the PSTN.

     

    Regards Kjeld

     

    Kjeld,

     

    snom ONE is not Lync certified.

    I did start a step by step to integrate lync / snom ONE that may help get you started:

    http://windowspbx.blogspot.com/2011/09/using-snom-one-as-sip-trunk-gateway-for.html

  7. off subject--but related:

     

    this thread is excellent example of why partners and snom themselves needs to promote staying on the latest version of communication software.

     

    snom's current unclear "upgrade path" around licensing is not helping this issue. The only consistent message i'm hearing is "buy the next version when it comes"---this is not a way to incentive people to stay on latest version...actually it is a way to keep them on ancient versions ;-)

     

    My suggestion is market this: "your comunication platform is never outdated" and sell something like a "stayupdated for another year/3yr" license at 20% of original license.

  8. Not only is the softphone market difficult from a technical point of view, it is also cut throat. There is so much free competition out there in the SIP space and also in the VoIP space in general that is it difficult to make money. Counterpath is a public company, you can see how much they are turning over.

     

    In the SIP space, I think it is fair to say that Counterpath has one of the the best soft phones if not the best. Customization would help from a marketing perspective as it would look to the native customer that snom has its own soft phone; however a deep integration that takes advantage of the buttons or even things like visual voicemail, extension status indication and so on are not possible. Thats why we are working on the attendant console. If customers are interested in large device interoperability (iPhone, Android, PC, Linux, Mac, you name it), then Counterpath Bria is the better choice.

     

    i'm glad to see snom invest in snom client/attendant. good move, snom ONE needs it. keep in this direction.

  9. just a couple things. i am gonna go heavy but at the same time i may be ignorant on some of the mechanics of snom one/attendant console integration. testing on 4 blues installed at diff locations ~40 phones at each... client requests:

     

    1 - multiple domain level presence (i know, might be taxing)

    2 - xml global phonebook (domain level privs)

    3 - hardphone dial (i don't care if this even passes the calls via web url)

    4 - incoming call notification (my clients are always looking at their screen and a popup with caller ID and a picture of a face is easier to identify than a phone number..pick up handset to answer)

     

    and to stretch this out even more, one touch recording on calls to the local machine using sip headers and using the ethernet switch on the phone as a tap. a little birdie told me that you can set the ethernet ports to work in a non-switched state. of course i understand this will tangle the QoS. i know this may be a bit but the first 3 are trivially necessary.

     

    it would be even better if you can integrate the recording cdr in the agents section to include all recorded calls from the local machine and can pull all the recordings to a local or remote area for archiving. if not, then i can write my own.

     

    and WAY WAY out there is maybe a small "virtual" lcd screen with DSS keys around it to be able to write custom XML pages to create things like visual voicemail and what not. that would really be cool.

     

    just some ideas that i have had while banging my head into a wall to get snom one to be as seamless as possible to my clients. so far, i have had to hand write most of the functionality needed and using third party apps like VOP.

     

    also, you should put version #s on the download page, 'cause i don't know if i am downloading a new version or one that i did a couple weeks ago...also, maybe we can stem away from the m9 functionality in the attendant console (autoprovis/tftp) and make it act more like a 370 or 821?

     

    just my 2 cents.

     

    some things to note:

    -the client already has visual voicemail.

     

    opinions:

    -i would say the format of the client is rough, but good direction. (i would say don't replicate any phone layout on pc)

    -incoming call pop is essential

    -phone control would be nice

     

    other notes

    http://windowspbx.blogspot.com/2012/06/snom-releases-windows-uc-client-that.html

  10. I got it to work! It would not work until I installed the m9 soft phone which downloaded and installed the visual C++ information.

     

    I like the look and feel!

     

    One thing I noticed was that when I dial a number from the console the computer dialed the number and not my desk phone, is this standard behavior? Is there a way for us to set which way we want to dial, soft phone vs desk phone.

     

    A couple things I was wondering:

     

    Will we be able to drag and drop calls or transfer in a later release.

    Will we be able to see incoming calls and pick them up?

    What does the phone keypad do?

     

    Thanks guys and keep up the good work.

     

    --Steve

     

    good.

     

    hmm, i expect i had m9softphone installed...

  11. Whow that would mean that maybe even when fax transmissions are going on, failover over would not miss a beat! However, from what I heared the faoliver is in the 1000 ms area, where regular calls may stay alive but fax would end.

     

    one fax fail on failover is acceptable.

     

    :-P

     

    seriously, snom ONE should work great on virualization failover.

     

    I see Mitel is really hitting the vmware thing. its how they select partners!

  12. Out of interest I thought I'd try-out the Attendant Console, but it also fails to run on my XPPro 32 bit machine.

     

    I get the dreaded 'AttendantConsole.exe has encountered a problem and needs to close...'. I'm also running v4 .net client, which I guess got loaded when I tested out the m9 softphone.

     

    p.s.

    I often read Matt's windowspbx blog and it's really interesting, thanks Matt.

     

    the client also crashed during use on my win7 64bit. i notice today snom noted the client is beta.

     

    Also, glad you like the blog. hope it continues to be helpful.

     

    matt

×
×
  • Create New...