Jump to content

mattlandis

Members
  • Posts

    1,254
  • Joined

  • Last visited

Everything posted by mattlandis

  1. The snom ONE team has certainly been listening to feedback! thanks. I appreciate the organized, thoughtful roll out. testing as we speak...
  2. thanks for that explanation. I see now why you gave the RFC.
  3. http://wiki.snomone.com/index.php?title=Upgrades
  4. ahhh... so any call over a SIP trunk will return a 1.0? Also, what about Patton PSTN gateways? patton must, because on our own install we have NO 1.0 scores and we use a patton ourself. hmm Matt
  5. We are trying to understand call failed senarios: #1-We are noticing that if someone dials an external number on a snom phone then hangs up before it is completed, we get a "Default Configuration: Call attempt failed on trunk Patton PSTN Trunk@pbx.xxremovedxx.local with code 486". It seems like this is a different case then if they dialed, waited and call failed (on pstngateway side) and there should be a way to tell the difference? is there a way to tell the difference? [almost like there should be a way to tell a user initiated call abort versus when the pstngateway failed] #2-Another senario is failover. If a call fails over to another trunk we are getting the same message above. Is there a way to get a failover notice versus a completely failed attempt? Or something like failed "but I have a failover option to try", because if there is no fail over option the error is much more critical. Are these dumb requests? ;-)
  6. thanks for that feedback. we have a suspect port/pstnline on one gateway that is failing which is failing over to a sip trunk. I think this appears to be the source of all the 1.0 scores and we are checking it...
  7. I'm trying to understand the MOS scoring in the CDR. ;-) Question #1: I'm looking at this line: QualityEst:MOSLQ=4.1 MOSCQ=1.0 does "MOSLQ" = trunk calls on the graph? does "MOSCQ" = extension calls on the graph? We are trying to track down ext to ext calls that are MOS = 1.0. Question #2: If non snom devices are involved in a call, will this cause MOSCQ to be 1.0? We have a lot of Extension MOS=1.0 I'm trying to track down. thanks.
  8. I am curious once again, is there a way to pull pbx extension presence at all? My previous questions that didn't get answered yet: 3-can pbxnsip CSTA return the presence info of pbxnsip extensions? (or something else?) 4-can pbxnsip CSTA be used send instant message? (or something else?) 5-is CSTA the tool to use to make a client that initiates calls, shows presence etc? Thanks guys.
  9. but you failed to answer my question #1. ;-)
  10. lerman, snom ONE Free limits you to adding 10 extension objects in snom ONE free. You can add as many snom handsets to those 10 extensions as you want. (if I'm understanding correct.) Another option is if you already have Exchange UM licenses/CALs. You could possibly use them as mailboxes...(i havent dont an exchange integration myself so dont know the issues) But I have to agree with previous post, likely snom ONE blue is best, simplist and leaste costly option.
  11. #1- bump: is that the next release? or v5.x? #2- would it be a good idea to have an admin email sent if a call has a low MOS score? (with call leg details?) I can't get over how good those graphs are at giving a nice overview of what a system is doing.
  12. okay, I did some testing. (i was wanting to know how languagues work myself ;-) It seems like in a multi-languague senario you need to: #1-download and install all languages you need. #2-if you have only a 2 launguage senario #3-in the autoattendent define the 2nd language needed #4-in the same autoattendent under "Direct Destinations" select "Announce 2nd Language" from the drop down list. presto. if you use the preset "direct destinations" announcements the autoattendent will be translated entirely automatically. It works VERY slick. Works VERY slick.
  13. i think the way snom ONE works is that caller selects languague in the first auto attendent and that persists throughout that call. (i haven't tested, just think i remember someone else asking)
  14. okay, Kurt from our office, came up with an even better solution: IVR with small asp.net app.
  15. Hey Kurt, The only solution i can think off: #1- make a hunt group 771 that the people will call for service #2- make a manual service flag for each seperate destination the service_desk will need to be forwarded too. 9000 = tech1 ext# 9001 = tech1 mobile# 9002 = tech2 ext# 9003 = tech2 mobile # 9004 = tech2 home# etc. etc. #3- now in hunt group 771 configure the service flags and night service thus: Service Flag Account: 9000 9001 9002 <etc etc> Night Service Number: <9000_destination_#> <9001_destination_#> <9002_destination_#> final notes: -Now the destination for 771 can be changed by dialing the 9xxx account you want it to goto -remember that the first flag to be set will be the one the call will goto -so for tech to change destination he will "turn off" current destination and "turn on" the desired destination. Make sense? I know. i GET A "KLUDGE" PhD for this one. But I don't see how else. attention snom: flags are soo cool. But they really need some tweaks to make our lives easier. some things that would be nice: -setting one flag can set or unset other flags -also, if an extension's redirection could use a manual flag there would be no need to use a hunt group above.
  16. hotdesking wont work since calls need to be forwarded to external numbers. (cell phone & home phone)
  17. but now if some one dials just 7335300 it wont catch it. and i just tested.. neither will that rule catch if someone dial 17177335300.
  18. I'm not sure I'm getting my head around regular expressions. We would like to send a group of numbers (lets say about 15 of them) to a certain trunk. But since someone could type them in 3 different ways: 17177335300 or 7177335300 or 7335300 we would need 3 lines in dialplan looking something like: 7335300|7338001|7336700 7177335300|7177338001|7177336700 17177335300|17177338001|17177336700 We thought if we could just match the last 7 of what they dial. (instead of all the examples which match the beginning) How would we do this?
  19. you mean 4.2? wow, the goodness keeps coming.
  20. I'm just impressed by them again. The Calls & MOS score charts just nicely give at a glance insight into what the system is doing. I'm curious, how hard would it be to be able to drill into all calls in the last 24hr/s that don't come up to a certain MOS score? (Just to get a sense of what is causing bad call quality) Matt
  21. I'm curious if there is star code/option to get voicemail of somone else' voicemail that instead of just asking for a pin it asks for extension and pin? (astersik usually assign *97 (get ur own vm) and *98 (get someone elses)) Not overly critical, just curious...just wondering if there is a hidden provision to do this tx
  22. I'm curious if it automatically autoprovisions like all the rest? (just plug it in and it picks up an extension...) I note on snom ONE it does not have an entry like all the other models. I agree that we really want to get away from snom m3. but for those who have existing m3's (...might be a little offputting to say to them "dump m3" ?) and still waiting on m9 in USA. ;-)
×
×
  • Create New...