mattlandis

talk to your snom reseller to buy snom green. This allows unlimited non snom registrations. if you are not a partner and have no reseller please talk to use. sales at landiscomputer.com.

glad to hear your success!

does this example help at all? http://windowspbx.blogspot.com/2011/07/using-patton-smartnode-4960-with-snom.html Patton support is super. support@patton.com or call their phone. Their support is 2nd to none.

you want to go to the forum.snom.com for this question. Or someone could show you how to setup SLA on the snom ONE pbx here. ;-)

Hey, can we talk to them?

but that works GREAT. great guys. should be provisionable via pbx though. that was the #1 reason people snomone intercom wasn't real accessible. similar functionality for callmobile, callvm, etc makes remembering those arcane star keys a thing of past. (only people who remember star keys are those who programmed them or used every couple hours. ;-)

ahhhhh...so it can't be auto provisioned from snomONE/pbx yet? we tell our techs and clients to not touch the phone itself as best practice. ;-)

snom ONE, Release 2011-4.2.1.4025, 6/29/2011 This below function new enhanced intercom button looks cool, but how is it setup? There is no new button type under button profiles. Please give step by step. "Enhanced button functionality: By merging button functionality of the snom phone (intercom) with button functionality of snom ONE (speed dial or BLF), users can now intercom a pre-programmed number" http://wiki.snomone.com/index.php?title=Release_notes

@porter - do you need that much scalability? multiple core support would be a bonanza for hosters and bigger clients.

@Nathan - yes, there are a lot of good choices. The 2 things we like about patton is they are rock-solid (set and forget) and we have found their support to be unrivaled in the industry. (But not rock bottom price I'm sure.) But there are a lot of good units/vendors. Here is an article that while it doesn't speak on T1 specifically the overall comments about vendors seems to be true across board. http://windowspbx.blogspot.com/search?q=gateways

thanks for the response.

even smaller? I already thot snomONE was incredibly small! Way to go! (after a 3day exchange/uc & lync implementation ....it looks amazing.) But in all fairness lync feature set and scaling is very impressive.

#1-I have a good freind (a snom partneR) who is asking what features will be implemented in the next version of snom ONE. Is there a listing? #2-also asking what expected release time frame? #3-and...is Ideascale ideas being monitored at all? ;-)

hey, could snom consider adding something like $(mos_score) as an option into the tcp line "CDR:" method of sending out cdrs? thanks

and I see why old wiki long format did not work...it was changed (with no documentation?) ! ;-)

ahhhh...that was just posted...that's why i couldn't find it....

wikis, kiwis, kbs, geebees...what a nest to find things. ;-) but thanks for pointing the right place.

yup just make a dial rule that sends any 5xx over a trunk and that trunk is a tie line to the other pbx.

your problem is simple: 3cx was already using port 80 and snom ONE could not. snom ONE is bad at telling you stuff. but execllent at running months with out touching once setup.

what ports to forwarD? look under ports in snom one and check wiki. to search forms, wikis, etc i suggest using this search: http://windowspbx.blogspot.com/p/snom-one-search.html (will let you actually search for stuff ;-) matt

seeing nothing. My listener is recieving just like it recieves for the TCP by line connection. should we do different?

which of these letters is it? cdr_format=$i|$v|$m|$l|$f|$t|$F|$T|$x|$y|$R|$r|$S|$C|$A|$E|$W|$w|$b|$B|$e|$o|$c|$d|$s|$M|$(record_location) or is it not in this list?

We are using the "CDR Url" method of sending each CDR record to external MS SQL server via TCP. Is there a way to tell/identify multiple legs of a single call together? (or even better is there a detailed wiki/kb that explains CDR in detail?) tx

when i set "cdr url" to: cdr:http//:192.168.1.37:8888 or http//:192.168.1.37:8888 I get nothing from pbx. ?

thanks for that. should i have been able to find that in wiki somewhere? just making sure i'm not blind. ;-) would it be good to add the quality metrics in the standard tcp line cdr?