Vodia Telephone System

Can you attach one of these wav files here that is not being accepted, so that I can test it here? Because I tried with a few and were accepted without problem. Just to be clear, you are uploading a wav file as a voicemail greeting, right?

Are you making sure the file being uploaded is a WAV file, 8 kHz Mono, 16 bit? Others won't be accepted.

I just tested it and it does show up as missed calls, under Calls->Missed Calls on the user portal. Can you tell me which version you are running? And I wonder we have some settings set up differently.

Also, in the next release version, you will be able to see the name of the domain you are in on the left side below the Admin button. Thank you.

About the CSV, you have to add a top line that explains each field of the bulk account creation. For example: type;alias;ani;password;web_pass;first_name;display_name;mb_pin;email_address;mac extensions;650;9786501234;1234;1234;Fred;Feuerstein;1234;ff@abc.com;000BBBCCCDDDD As you can see above, each field corresponds to its value like type=extensions, alias=650 and so on. Of course, it is not necessary to give all information of the account during bulk creation, you can always add them later. But at least two fields, type and alias, are necessary to let the system know what type of account like extensions and what its number is. For example: type;alias; extensions;651; extensions;652; That will create the two extensions for example. Also if you want to skip a header field for specific extension that is present at the top, just add a semicolon ; without any value. So if you download a list of users, the list is fine but you will have to add the header line on top for the fields in that list to be imported. I hope it helps.

We will look into both the import CSV (as to why it doesn't work for you) and making it clear in which domain you are. Inactive has already been explained and has nothing to do with the behavior.

Since it works perfectly for me on snom720, I don't know what settings are different for us that it behaves differently for you. The only difference could be the phone firmware? I am using snom720-8.7.3.19-SIP-r.bin.

I am sure I completely understand the problem. Is it not working? The LED does not light up and the redirection does not activate/deactivate? Anyway we have fixed the led as well as the redirection on/off toggle in our latest update: http://snomone.com/downloads/snomONE/version-5.1.1.xml Maybe you would like to give that a try and let us know. Thanks.

I am sorry, I don't quite understand what you mean? Activesync is the only way you can do it through the exchange server. And apart from that you can manually add or delete entries. All of these entries, including activesync contacts will show up on your phone through LDAP. But I think you were trying to ask something else?

It generally means redirection to another url. But the problem is, that is only allowed during auto discovery where we handle it accordingly. In this case, auto discovery is complete and syncing has started. In this state, this response from the server does not make any sense. Also, as far as I can remember, the document doesn't even mention this kind of response from the server in the syncing process. It is only described for auto discovery process where we handle it. Could it be the server is generally set for redirection for all its folders? Could you test it on another account or even another server if possible.

In theory, there is no limit. However I haven't tested extremely huge lists of contacts. Is it giving you a problem? It does seem however, that some contacts may be giving problems. Unfortunately, I haven't seen any such problem on my side yet in order to deal with it.

It will show the two numbers and the mobile number in the LDAP. Unfortunately the home number is not included. Actually, if I recall correctly those were the only numbers I got from the Exchange Server response.

I don't quite understand. It can't be from the calling side, since anyone would be allowed to call on a public website. So I don't understand where to match a user agent. If you mean to check if it is indeed from the browser then that would be useless since all javascript info is available to everyone anyway. We do check the trunk's id which is unique but again it is available. Maybe you meant something entirely different that I misunderstood. Thanks.

That seems very strange, since it seems synching has already started. For confirmation: You entered the email address in Username, e.g. abc@company.com Followed by the correct password. Leaving the Exchange Address empty. Then pressing Save. Then pressing Sync. Other than that it would difficult to pinpoint the problem unless something is set differently on the Exchange server side. In order to really pinpoint the problem, maybe you could provide us with a fake (test) email account with some fake contacts in it on the exchange server that we could try to test here. Thanks.

Well we have a version 5.0.10o, which is not final yet but since you are testing, maybe you could try that.

Which version are you running? I ask because that issue for updating the call has been fixed for some time now and it should do it without any refresh. Also the call should be there even if you were not on the page when the call was made and came to the page later, the call should be there. About the click2dial, the user (extension) to whom the portal belongs must be registered and shown green before you use the Dial button for click2dial. I am sure you are doing that, I just wanted to clear that. Apart from that, another reason I could think of in which it wouldn't work properly would be if you are not using a snom phone for the call. If it's another phone, it could be that their CSTA call management has some problems or not completely compatible. Again it works perfectly for us here and I would like to know the version you are using.

Unfortunately, that noise (which only happens sometimes) seems to be the browser problem which somehow does not shut down the audio completely even when asked to do so. But it does disappear on its own after a few seconds.

Unauthorized User. Are you sure your username and password are correctly saved before synching?

[5] 2013/04/20 10:55:04: Activesync Status Error: Failure 2. Status = 8 That status for Sync means: Object not found. The client issued a Fetch or Change operation that has an ItemID (section 2.2.3.84) value that is no longer valid on the server (for example, the item was deleted). Is it possible there were no contacts there? Also I don't know why auto-discovery fails when you leave the address blank? Do they say anything about auto-discovery? Also if not what address do they want to use for activesync. Sometimes the obvious well known address, like you are using, is correct but sometimes its completely different, in which case it has to be found out, especially if it doesn't respond to auto-discovery.

It has been added. Although I don't understand yet why it didn't work with a single trunk like the others.

On snom ONE, if you provide: outbound proxy address: outbound.vitelity.net domain: sip29.vitelity.net and the account and password that you may have, does it work flawlessly in both directions? If not, it cannot be added yet because that much information should be enough to get it working, no fuzzy inside details.

Can you please provide the following settings of the provider, so that we can add it. Outbound Proxy Address: Domain:

It has been put back. I am sorry it had been lost during the modification.

For now can you try the exchange server address directly, if you know it, i.e. put https://the-exchange-ip-here in the address field (.75 that you were talking about). That will directly try the exchange by-passing auto-discovery which you say is not working for you. Please do press Save and then Sync. This will at least give us an idea where the problem lies. Also I asked you if giving us access to a temporary account on your server (for testing) could be an option?

Have you tried leaving the address field empty, so that the server is auto-discovered? You've probably done this, but just to be on the same page: The username would be the email address of the user, for example abc@example.com. Then of course the password. Then leaving the address field empty, press save. And then press Sync. A log would be very helpful if that doesn't work. Clear the log, then Sync and then send us the refreshed log. If your exchange server is on public IP (accessible through internet), then maybe we could get a test account to find the issue. By the way, although the auto-discover (leaving address field empty) should work, but in case it doesn't, you have to enter the full URL of the exchange server with the https://, for example https://example.com. Maybe we should make that clearer, although with auto-discover it is hardly used. Thanks.