katerina

Today I got to the office and tested this myself. I configured 2 extensions just as you said: 1. extension 123 - configured on a snom 870 Account number: 123 1234 First name (e.g. "John"): Mr Last name (e.g. "Smith"): X 2. extension 124 Account number: 124 1235 First name (e.g. "John"): Mr Last name (e.g. "Smith"): Y Then I call from an external trunk, from 1234 to 124. I see on the screen then Mr X is calling, which is correct right? (see photo: 1234 calls 124.bmp) But you say you see Mr Y on the screen instead of Mr X, right?

Good idea. But first disable TLS (and reprovision the phones) so we can see the SIP messages

Hello, Using snom ONE's built in LDAP would be the way, but this feature has some known bugs on the M9 software which we are currently working on.

Ok you mean under "Account number(s):" . This means you have set an alias, and the PBX thinks the call comes from the extension. If you remove the mobile number from the "Account number(s)" list and just leave the internal extension number you shouldn't have this problem. If you need the mobile number to be associated with a name, I would suggest you add it in the Address book. So to answer the question, I would say it is an intention

Ok, then it is not the LDAP bug. Are the mobile phone numbers set anywhere else in the server then in the address book? For example as aliases? Do you think you could post the snom ONE log here or send me a PM with it? (with level 9 and all SIP messages enabled please)

Does the trunk return a failure message? In this case it would be an idea to use failover and loop back to an auto attendant. You could try the following: - add an auto addendant that says "No more lines" or whatever you want to say to the user on call failure - set Failover Behavior to "On all error codes" in trunk settings - add two dialplan rules, one with smaller priority to your trunk and one with greater priority with "Try loopback" to your auto attendant - disable loop detection from Admin settings

Hello, Which version are you using? In the latest release there is an LDAP bug. We can send you a bugfix, just tell us your operating system.

Are you sure you didn't just delete the domain and left the alias? In which order did you delete them?

mattlandis, could you reproduce this again? Just as info to everyone, lerman's problem was fixed by increasing the "Maximum Number of Accounts" in the edit domain page (it was set to 10, and he already had more than 10 accounts)

Dann kann es sein, dass die Einstellung "Maximum Number of Accounts" bei dem Domain eingesetzt war.

Hallo gustav, Welche Lizenz benutzen Sie? Wenn Sie die freie Version benutzen, können Sie nur bis 30 Kontos einrichten.

You are right, the exact version number was missing from the release notes. I added it now. Unfortunately we can't provide release notes for the custom versions. If we start doing that it becomes very hard to maintain.

Not yet, we are still analysing the issue.

Great, thanks for the info randoff

Ok, please send me the tar, I can test it on a standard installation.

I take it you are using Pbxnsip for external trunks, right? In this case an idea would be to create an extension in Pbxnsip (http://wiki.snomone.com/index.php?title=Extension_Accounts) and then create a SIP channel in Asterisk which registers as the extension you created. (http://www.voip-info.org/tiki-index.php?page=Asterisk%20SIP%20Channels) Then you can route all calls from the Pbxnsip trunks to the asterisk extension

I uninstalled snom ONE, installed it again from http://wiki.snomone.com/index.php?title=Downloads, and then tried the following: - added an IVR - removed an extension and added it back - removed an alias and then added it back - removed a domain completely and then added it back All my tests were successfull. What am I missing? Can you explain step by step what you are doing?

Here it is for centos (32 bit): http://pbxnsip.com/snomone/beta/centos32/pbxctrl-centos5-2011-4.2.1.4015 And for debian: http://pbxnsip.com/snomone/beta/debian/pbxctrl-debian4.0-2011-4.2.1.4016

Please see this post

The problem you reported is very similar to a known bug which we already fixed. Please tell me your operating system, and I will send you a fix version for you to test.

Let me make sure I understand: you installed snom ONE, then deleted 49, and then the system did not let you add another extension? This should no happen. Which version did you install? As workaround you can always reinstall snom ONE and once you have a fresh installation of the latest version you should have no problem adding an IVR even if you already have 10 Extensions.

Hi colink, I see you are using version 4.2.0.3950 . Can you please upgrade to the latest version (.3981) and try again ? (http://wiki.snomone.com/index.php?title=Upgrades)

Try removing the POST line and Content-type header. Here is a trace of a working example and a small test application you can run in python, I hope it helps: test5.zip test3.zip

Ok, then take http://pbxnsip.com/snomone/beta/win64/pbxctrl-2011-4.2.1.4013.exe

Hi Colin, Ok, keep us updated.