spidersden
-
Posts
22 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by spidersden
-
-
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
-
there is someone that make a sip based attendantconsole that is compatible with snomone/pbxnsip. i can't think iof the name right now...perhap snom can help?
(the option i'm thinking of DOES cost)
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.
-
We are working on a windows based attended console at the moment as a substitute for WAC.
"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.
-
I upgraded SnomONE to Beta Corona Austrinids (version 4.5.0.1030 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
-
Just to finalize this thread; we upgraded to 2011-4.3.0.5020 (Linux) and it has cleared up the LDAP issue.
Thank you,
~Scott
-
These guys are a partner of ours.
http://www.vertical.com.co/vertical/EN/callScout.html
They have some pretty neat cdr tools.
We received pricing from Vertical. CallScout is cost prohibitive. Any other suggestions?
Thanks,
~Scott
-
These guys are a partner of ours.
http://www.vertical.com.co/vertical/EN/callScout.html
They have some pretty neat cdr tools.
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
-
Hi,
Is there a general document describing CDR(or ACD) mechanism and meanings of each field in CDR for all different issues and call scenarios in detail.
For example in outgoing call this field x this field y,
in incoming call this field x this field y, etc.
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
-
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
-
I appreciate the quick response.
The INVITEs sent on the trunk has an issue in the 'bad' case. Both the "From" & "To" have the same value. Looks like the provider does not look at the "P-Asserted-Identity" header. So, can you please change the "Trunk->Edit->Remote Party/Privacy Indication:" to "Remote-Party-ID" and re-do the test. We move around the header contents a bit and that probably would take care of the caller-id.
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
-
Do you have the SIP log from the PBX for these 2 cases?
Yes. I have sent them via PM to you.
-
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.
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-4.2.1.4025 (Linux)
-
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
-
-
We are able to reproduce the issue here. There was an error in how we were searching for internal extensions (it was dipping into the wrong table and that was causing to pickup Hannah [last name])
The fix will be available in the next version.
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
-
Ok. You can PM the configuration & we can see if that we can reproduce it here using that data.
PM sent. Couldn't attach the tar file though, 500k attachment size limit.
-
In any case, we have made some changes to the code for the next version so that you do not have to add address book entries for the existing accounts. If you would like to test it, please let us know.
I don't think I can offer to test a new version of the PBX software since we just went into production with this system early last week.
Is there maybe a way for me to clear and repopulate the ldap directory?
~Scott
-
Anything from the address book should be supported. We will perform some tests on this and update it tomorrow.
Is there anything I can do to aid in testing? I can probably make a full backup of the PBX (minus audio recordings) and upload it to the Snom Support Portal if that would be helpful. Obviously I won't be willing to provide that here in the public forums.
Thanks,
~Scott
-
Currently, among the internal accounts/numbers, only extensions are supported. Rest of the account types will be there in the next version.
Ok... Automatic addition of hunt groups and ACD queues is unsupported. I can accept that.
But why am I not seeing success when manually adding the hunt groups and ACD queues to the domain address book?
Or do you mean that having address book entries for hunt groups and ACD queues is entirely unsupported; no matter how those entries are added?
Thanks,
~Scott
-
Maybe lets do a step back and discuss what kind of problem you have. Maybe we have to change the LDAP on the server side to get this done.
Sure thing.
The core problem is that when I would dial the number of a hunt group or an agent group, caller id on the dialing phone would not show the name of the group, it was instead showing the name of a seemingly random extension account. It would consistently show the same wrong name for any particular group, but I could not find any reason for it to be showing those names.
When calling the "Network Services" number (404), it would show "Hannah" on the display every time. Her extension is 246...
Another hunt group at extension 401 would consistently show "Wendell" on the display of the calling phone. He is actually extension 203.
After doing research on the Snom forums, I had seen instances of similar sounding problems being resolved by manually placing entries into the Domain Address Book.
When I add the entries to the domain address book, it fixes _some_ of the CID issues, but only because the LDAP server starts handing out 2 entries for each account. If the correct entry happens to appear alphabetically later than the incorrect entry, the phone will show the correct name (after flashing the incorrect name), otherwise it will still show the wrong name on the calling phone.
What blows my mind is that the server is giving me any information at all for Hannah (telephone number 264), when a PCAP trace shows that the ldap filter is a very straightforward "telephoneNumber=404".
Thanks,
~Scott
-
Please keep in mind that the LDAP server on the PBX has a very limited functionality. The PnP mechanism provisons something into the LDAP settings of the phone that should work. If you start editing t, changes are pretty hght you are hitting something that is simply not implemented on the PBX.
I only started making changes after discovering a problem. I'm pretty sure that they're back to defaults now with the exception of the ldap_display_name field because I do not want 2 entries per user to show up in the company directory. We were seeing one entry for the user's local extension, and one for their cell phone number. Due to us having 75 employees, we prefer to use the *00 feature code in SnomONE instead of doubling the number of address book entries shown on each phone.
For clarification though, here are the current settings as they exist on a phone:
ldap_server!: [correct ip address of the server]
ldap_port!: 389
ldap_base!: ou=people
ldap_username!: [domain]\[extension]
ldap_password!:
ldap_max_hits!: 80
ldap_lookup_ringing!: off
ldap_sort_results!: on
ldap_search_filter&: (cn=%)
ldap_number_filter&: (telephoneNumber=%)
ldap_name_attributes!: cn
ldap_number_attributes!: telephoneNumber
ldap_display_name!: %cn
ldap_predict_text!: off
perform_initial_query_in_ldap_state!: on
auto_dial_ldap!: on
Thank you,
~Scott
-
Hello,
I have noticed that when dialing some of my Agent Group extensions internally, I'm seeing an incorrect name displayed on my Snom 870.
I am running SnomONE Blue on Linux:
Version: 2011-4.2.1.4025 (Linux)
Created on: Jun 27 2011 12:40:10
License Status: snom ONE blue
My phone is running firmware version 8.4.31
Older versions of the phone firmware & PBX had an issue where calls to extensions would scroll through every name in the PBX directory when making an internal call. I am not being affected by this problem.
When directly dialing an agent group or hunt group from my phone, I was seeing the name of a seemingly random user being displayed as the destination caller id on the phone instead of the name of the hunt group or agent group I was dialing. The phones are auto-provisioned by the PBX and I haven't messed with the Name or Number filters on the phone too much. I have removed "%mobile" from the "LDAP display name" field.
I attempted to correct this problem by manually creating entries for each hunt group and agent queue in the domain address book [settings | Address Book | Load CSV File] . I had previously been letting the PBX handle all of that on it's own (without me adding entries).
After adding the phone book entries manually, I'm seeing 2 names flash on the caller ID when I dial, usually the incorrect name first, followed by the correct name, but other times it is displaying the correct name first before settling on the incorrect name (depends on the alphabetical order of the 2 names returned by the LDAP query)
Pulling a full PCAP trace from the phone after making a quick test call is showing the phone sending this query to the PBX
(404 is the actual hunt group extension in this case)
Filter: (telephoneNumber=404)
Attributes:
AttributeDescriptionList: cn
AttributeDescriptionList: telephoneNumber
The response I'm getting is showing both info for the hunt group, and for a seemingly random user.
One that's correct:
CN=Network Services
telephoneNumber=404
And one that's not even close:
CN=Hannah [lastname removed]
telephoneNumber=404
Hannah's extension is actually 264. She is also not a member of the Network Services hunt group.
I can provide the .pcap file if needed, but will have to remove her last name from the file which will show TCP checksum errors when opening the file in wireshark.
This is also happening for some other hunt groups and some agent queues, so it doesn't appear to be related to the "404" extension but the directory does seem to be working properly when calling any of the "Extension" accounts.
Can someone shed some light on this situation for me? Do I need to manually configure the domain address book to include all users of types Extension, Hunt Group, and Agent Group? Or have I found a bug?
Thank you for your time and attention.
Sincerely,
~Scott
How to access WAC in Beta Corona Austrinids
in PAC and WAC
Posted
Has there been any additional forward movement on the new attendant console?