mattlandis

Is it reasonable that some places will not want the starting and ending BEEP when paging in a public place? Would it be possible to put a setting in snom ONE paging accounting to designate to turn this off? tx

Hello, Over the years I've been trying to get to the bottom of presence in pbxnsip/snom ONE. I'm curious where it stands right now? I've noted that these release notes say that snom ONE is now a "presence server" and not just "relaying" presence: http://www.pbxnsip.com/docs/release-notes/pbxnsip_version4_release_notes.pdf pg 26 What method is snom ONE using to set presence? The below? http://wiki.snom.com/Category:HowTo:Presence Also, how does basic call state (registered/idle,alerting,connected) relate to presence? Is designated presence (http://wiki.snom.com/Category:HowTo:Presence) just allow for more granular definition of "idle"? Is there a field in snom ONE under an extension that holds the presence state & note? I know that snom ONE isnt meant to/won't compete with Lync/OCS, but having basic presence would be good. I'm okay with a theoretical discussion here. No customer breathing down my back on this one. ;-)

Hello, First, I'd like to say that the available API/developer hooks (and us finally understanding how to use them!! ;-) really allows us to finally integrate snom ONE into other PC systems. This will make the value of snom ONE go upexponentially! We are writing a client to monitor active calls. Had some questions about XML returned to the "/ajax.htm?action=call_list&domain=localhost&token=whatever" request. #1-It appears there is not a way to tell if a call is internal or external except by looking if the "trunk" object is missing/present.(ie=<Trunk>Patton PSTN Trunk</Trunk>) Would it be more developer freindly to expose a object "CallType" and tell them explicitly if it is an external or internal call? #2-another thought: instead of requiring the developer to parse out extensions, etc wouldn't it be easy to add some fields: FromNumber, ToNumber, toFinalNumber... ? If there is anymore documentation on integrating to snom ONE I'd like to hear about it. so far we are just hacking around to find stuff. But this info presented in an organized way would surely benefit the snom ONE community.

In answer to your first paragraph: I am very aware of this, (that no one else will be able to page)that why i asked the question. I'm not looking for theoretics: How do we make it so the PA1 automatically hangs up any call longer than a minute? (we have a customer that is getting very frustrated at all the PA1 antics: randomly doesn't hang up, several units that would lock up after a day in service, new units that come with beta firmware...;-) (that tired smiley is mine, not customers.)

Read my article, especially point 3: http://windowspbx.blogspot.com/2011/02/gotchas-to-watch-for-when-migrating.html "Remember that these allowed non snom devices will have a limitation that they will not support a SIP REFER. In the real world this means that, for one, the Transfer button on software and hard phone will likely not work. This is not the end of the world though as with snom ONE you can put the call on hold and use the built in star code to transfer as a work around." I wish this would go away as well. Your welcome to suggest change here: http://snomone.ideascale.com/

i know that the max. call length can be set globally. Can i set 1 ext. to a very short call length? Use case: sometimes calls to the PA unit do not get hung up (for whatever reason) Can I set the calls to pa unit (snom pa1) to "hang up" after 2 minutes? (Either in the pa1 or in snom ONE) In the one case we caught it in the act, pressing the X key (via the web) hung it up. We could blame users, but I'm a little suspicios it is actually the snom Pa1. It doesn't happen often, but enough to

Cool! That does it perfectly. Once again, snom ONE doesn't dissapoint. [We are having a batch of snom PA1's that just hang out of the blue. This way we can monitor them proactively.] Matt

understood. thanks

-i just checked and spam did not catch this. -2ndly, i am getting other admin emails from this system. Can you verify it works for you? I have a subtle feeling this is not working correctly. tx

Where did that update come from? I dont see it here: http://wiki.snomone.com/index.php?title=Upgrades tx

what if i want to buy Hardware for free edition?

great about the excitement. even snom doesn't know pricing yet(i dont think) so probably you will need to wait a little. ;-)

thanks for clarification. we had an issue with cpu usage ramping up and killing snom ONE (which appears to have been Grandstream gateways...when we removed them it stopped ?) reason for watching memory closer than normal.

let me verify it didn't go to spam. i did test and the "new account" email came through and other admin emails are coming but I'll check. appreciate the verification

Hello, We have a problem with a certain phone dying (i won't mention any names) so I want to know when extension 101 has any change in registration. So i set the below setting to yes. "When a registration status of an extension changes:" If extension 101 has 3 registrations and I power off one of the phones, should the admin get an email?

sounds like a "freindly scanner" or similar attack? does v3.4 have the blacklisting feature? I forget, if not, get on one that does.

I'm curious how memory should work with snom ONE. Should snom ONE be using more memory with a heavy load during the day then release memory when there is no load over night? Or does memory use only go up?

Standard procedure when installing snom ONE/ v4.x: #1-install snom ONE #2-set the Administrator credentials (user/pw/pin) #3-now provision and/or restart the existing phone handsets They will now be provisioned with the new credentials and you will be able to login. This is possible to do entirely without being onsite.

actually, most are exposed. just not documented very well. http://forum.pbxnsip.com/index.php?/topic/3124-does-soap-expose-all-pbxnsip-objects/page__pid__19081#entry19081

Hello, When you switch from pbxnsip to snom ONE there will be some changes: -Blue will allow up to 40 non-snom devices to register. (snom ONE looks at the user-agent string in SIP and if it doesn't contain "snom" it will limit it to 5 in snom ONE Free, 10 in Yellow and 40 in Blue respectively) -Note that I used the word "allow" instead of "supported". This was intentional as you will need to do the interop testing yourself. Which usually is not a big hurdle for basic functionality. -Remember that these allowed non snom devices will have a limitation that they will not support a SIP REFER. In the real world this means that, for one, the Transfer button on software and hard phone will likely not work. This is not the end of the world though as with snom ONE you can put the call on hold and use the built in star code to transfer as a work around. -Also note that snom ONE Blue only allow 5 domains (tenants) is not meant (licensing/eula) for reselling hosted service to other customers. I'm not sure how this is enforced and I suppose it can get grey? if a company owns a building and rents to tenants. -snom ONE blue does not auto-provision brands other than snom handsets. Actually moving from pbxnsip to snom ONE is a bit of a consultative conversation to best answer your question but this is good items to start.

that sounds like a bug. Blf button should only call and show state, not pickup a call.

for good or bad. ;-)

Colin, Since your fighting an attack the article I wrote on SIP hacking might be of interest to you: http://windowspbx.blogspot.com/2010/10/someone-is-attempting-to-hack-into-your.html If anyone has anymore items to add to the list of Tips, I'd be glad to hear them. On a less serious note--the title "constant hacking" evokes edbassmaster character. "the hacker" ;-)

ha! not sure how that got resurrected!

;-) That will endear end users to administrator. There really ought to be a web search tool. But if big searches are being done on already taxed cpu it may reek havoc on real-time comms? I guess that is what lync does is off loads that stuff to another server. Not a bad idea but makes complexity into the picture. Matt