Jump to content


  • Posts

  • Joined

  • Last visited

spidersden's Achievements


Newbie (1/14)



  1. Has there been any additional forward movement on the new attendant console?
  2. Thanks Steve & Matt. I appreciate your responses and advice. Are there any other suggestions on monitoring on-call extensions? Any SOAP calls I could pop from a web server? A newer beta of the PAC? I've scheduled a maintenance window to downgrade SnomONE this evening unless a suitable solution can be found to hold us over until a working PAC is available. Thank you, ~Scott
  3. This'n? Voice Operator Panel It definitely costs. If there's a beta version of the PAC (assuming it's different from the snom phone application), I'd be willing to give it a try. Just need _something_ that shows idle/busy for the operators. Thank you.
  4. "We're working on something better" is great; glad to hear that. What's the release date? What exactly are my operators supposed to do for presence monitoring in the mean time? This? The snom phone application We have desk phones. We don't need to dial numbers from our computer. Our operators need to be able to see if User X is on another call before transferring someone to them. Our attendants used the WAC simply to see if we had users on another call or not. Not a lot of other features worked in it. I saw the other forum postings; it's unsupported, we're working on something better, and I accepted that. But replacing partially functioning code with a promise that you're working on something else is not a good way to keep a customer happy. And doing so without warning is an even worse idea. We've got more than 70 Snom 870 phones deployed in our facility with a blue license for SnomONE. The Snom Vision, marketed as an operator panel, flat doesn't work for a company our size. So we've made due with the WAC, while waiting for the Vision to be improved to the point that it would actually be useful. Now we're left with Visions that don't do much good, and no WAC. So what are my options here? I'd love to see a PM on how to re-enable the WAC. Hopefully I can customize some htm files and bring it back to life for our deployment. If it's not that simple, what can we use for centralized busy/idle status monitoring on 70+ phones? Thank you.
  5. I upgraded SnomONE to Beta Corona Austrinids (version on CentOS 64) last night and now see that on the login screen for the PBX, the "Console" login-type is gone. Due to extreme limitations with the snom Vision operator panels, our operators rely very heavily on the WAC. How can I get them logged in to this? I couldn't find any mention of this functionality being removed in the release notes. It's great that you show all the new features and bug fixes, but if you're removing major functionality from the PBX, that probably should be mentioned as well. Thank you
  6. Just to finalize this thread; we upgraded to 2011- (Linux) and it has cleared up the LDAP issue. Thank you, ~Scott
  7. We received pricing from Vertical. CallScout is cost prohibitive. Any other suggestions? Thanks, ~Scott
  8. Thanks for the info. I've requested a price quote from them. Aside from that, I've been playing with the simple tcp cdr output to try and make it work with CDR-Stats. I'm not finding a variable for "disposition" which is asterisk speak for whether a call failed, was busy, was answered, or was not answered. I'm also noticing 2 lines of CDR output for a single phone call, one with a direction of "I" and one "O". Is this normal? It's almost like one line of CDR info is being generated for the connection from the provider to the PBX, and then another for the PBX to the internal extension, but I'm not 100% sure that that's what is happening. Thanks, ~Scott
  9. The most detailed information I've been able to find is inside the Snom ONE manual, available here. I hope this is helpful for you. ~Scott
  10. Can someone recommend a nice CDR reporting tool that works with SnomONE? While researching, I stumbled across this product: http://www.cdr-stats.org It's designed and marketed as an Asterisk solution, but I'm wondering if I can make it work, or if I can find a similar product that SnomONE would be able to interface with. I like that cdr-stats is web based as we operate in a mixed platform environment, some Linux workstations, some Apple, and some Windows. Thanks, ~Scott
  11. I appreciate the quick response. As you recommended in PM (quoted above), I set "Remote Party/Privacy Indication" to Remote-Party-ID and re-tested. That appears to have corrected our problem. I've included your suggestion here in hopes of helping other forum members in the future. Thank you for your help and a great product. ~Scott
  12. Yes. I have sent them via PM to you.
  13. For what it's worth, if I copy the URL from the Address Book call link, and change the IP address to the FQDN of the PBX, the caller ID does display properly at the remote party. In other words, manually changing this url: http://ip.of.the.pbx/remote_call.htm?user=241%40our.domain&dest=1423xxxxxxx to this url: http://pbx.our.domain/remote_call.htm?user=241%40our.domain&dest=1423xxxxxxx results in proper caller id display for the remote party. Any suggestions on how to work around this? Product: SnomONE Blue 2011- (Linux)
  14. Hello, I have had an issue reported to me by one of our users today. The problem is that if an entry is added to your personal address book via the PBX web interface, and then you dial that address book entry from the web interface, the caller ID of the remote party shows their own phone number (instead of ours). In other words, dialing an address book entry with a phone number of 1-234-567-8901 from 1-423-xxx-xxxx shows 1-234-567-8901 on the remote party's caller id instead of our 1-423-xxx-xxxx number. This only happens if the little green phone icon is clicked from the call column of the usr_adrbook.htm page. Using the the phone icon on the "Call Logs" or "Missed Calls" pages works properly. If we use the address book via the phone UI, then caller id is properly displayed on the receiving party's phone. An interesting, but probably bad, side affect of this is that if we use the web address book dial link to call a cell phone, then we get dropped directly into that persons voicemail, because the remote carrier thinks that the user is calling themselves. This would be the same for any carrier or pbx configured to put a user in their mailbox if they call their own number. To reproduce the problem: Log into the SnomONE web interface as an extension account Click the "Lists" tab Click the "Address Book" link Add an entry Use the green phone icon to initiate a call to the remote party. The remote party will see their own phone number on their caller id The only thing I'm noticing as a major difference with web dialing between the Call Log page (usr_callog.htm) and the Address Book page (usr_adrbook.htm), is that the call link is formulated a little differently. Link from Call Log looks like: http://pbx.our.domain/remote_call.htm?dest=1423xxxxxxx Using this first link properly displays CID on the remote phone. Link from Address Book looks like: http://ip.of.the.pbx/remote_call.htm?user=241%40our.domain&dest=1423xxxxxxx Using this link does not properly display CID on the remote phone. Notice that the properly working link is using the FQDN for the pbx whereas the non-working uses the IP address. Thank you, ~Scott
  15. Glad to see that you were able to track down the root cause of the problem. Is there an expected release date for the next version? Is there any sort of published "Roadmap" (showing projected feature additions and bug fixes along with expected release dates) for the SnomONE product or any of the Snom phone firmwares (particularly the 870 and the Vision operator panel)? Thank you, ~Scott
  • Create New...