Jump to content

mattlandis

Members
  • Posts

    1,254
  • Joined

  • Last visited

Posts posted by mattlandis

  1. Hello,

     

    I just got a actual snom ONE yellow box. I wanted to make sure I understand activation so I installed snom ONE and activated. It went extremely smooth. ;-) That was just for a test so I want to set my system back to free. So i removed activation key, clicked save and set back to free edition.

     

    Just want to make sure: Will this give any problem now when we want to activate this on a live system?

    Basically the question is: have i properly deactivated it on a test machine.

     

    Thanks,

    Matt

  2. do you have a lot of these? they are ancient! ;-)

     

    Nostalgia on my part. We had these phones at our office about 7? years ago.

    http://www.abptech.com/products/snom190/snom190.html

    http://www.snom.com/en/company/history/

     

    i would really suggest you think about upgrading if at all possible.

    snom ONE does not have a pnp template for them in the standard product.

    But you will be able to use them as a manually provisioned for sure. they will not count against non-snom devices.

     

    Matt

  3. our experience is: always provision phone using snom ONE/pbxnsip. too many things to go wrong it you don't ;-)

     

    I just talked to someone this week and telling them why to get snom phones. This was one of the reasons. tight integration to snom ONE.

     

    Matt

  4. For paging we deliverately choose not to offer wildcards just because this can easily result in explosive call volume. For example, where there is a domain with hundred extensions, a star would be a ticking time bomb. I believe for other fields the star is possible where there is no performance impact to be expected.

     

    I agree with that rationale.

     

    i suggest that fields that don't allow wildcards be noted in the UI. (since it is an exception) those little footnotes are fine. Even a popup help.

     

    Matt

  5. Getting a softphone is something snom should do. But it doesn't solve the complete issue here.

     

    if snom is going to limit devices that connect to snom ONE then they really need a full line of hardware and software which they can offer the user instead. What are some of the missing components? FXS, fax, video deskphones, multi-modal (IM, app sharing, voice) sip client, SIP cameras, etc. There are some other vendors that have nearly this whole list of devices/software. (c,g,y) Currently snom doesn't so to be compelling it needs openess.

     

    Also, i think snom shouldn't get to fixated on throwing some business to g/y. If snom ONE would cause 10 handset to goto g/y for every 100 gained for snom, wouldn't it still be worth it? Even if that ratio is much worse it is still additional sales for snom handsets. But even this may be an odd way to look at it. I mean, snom ONE is NOT generating sales for g/y. These companies would have bought some other pbx--snom just wouldn't know about it. Now snom knows about it and can email the admin from snom ONE stating "If you had a quality snom handset the issue you just experienced with the unsupported Grandstream would not have happened." ;-)

  6. Snomone Free allows, if I'm correct, for 10 extensions :

    8 of them have to be Snom phones, the other 2 may be other brands.

     

    Greetings,

    Marc

     

    Marc,

     

    That is correct. Note that this limitation applies to non-snom softphone, fxs, or sip phone/device. Free edition will allow 2, yellow=5 and blue=10 non-snom devices.

     

    So this is not the next question ;-) be aware that the 2 non-snom devices will not be able to use their "transfer" buttons (if they have them) but you will need to use the snom ONE star code to transfer. (example: put call on hold, then dial *77)

     

    I am very much hoping snom can find a way to remove these artificial limitations, but this is how it stands.

    Matt

  7. We introduced a new type "Park Orbit". It has pretty much the same functionality like the previous implicit orbit; however you can pick up the call from an extension by just dialling the park orbit number. This one does not "waste" an extension license. And when you send the call from a trunk to the orbit, the PBX will park the call there.

     

    Interesting.

  8. Hello,

     

    Thanks for that clarification.

     

    But don't be too hard on him quoting that 164 number because snom is mentioning 150 (ok, 14 different. ;-) and unlimited. I see the a disty says it this way: "snomONE PBX -Unlimited extensions - Recommend up to 150 extions/server"

     

    With that messaging people will need reassurance to go more. ;-)

     

    But once again I do appreciate that clarification.

     

    Matt

  9. Considering a Windows based PBX serving 240 users and 20 "other" type devices coming in on 48 SIP trunks from Global Crossing. I have read that the ideal number is under 164. ANyone using it for this many extensions? thoughts?

     

    Thanks!

     

    We have typically been 50 and under extensions.

     

    I understand one part of the problem is processing power. This system is B2BUA so all passes thru the server.

     

    I would like to hear experience too.

     

    Matt

×
×
  • Create New...