Hello,
i have over 150 Polycom IP 320 321 Telephone phones and one big Problem.
I have connected all telephones with our openldap (with or without Server-Side-Sorting) Addressbook:
<dir.corp dir.corp.address="10.0.1.1" dir.corp.autoQuerySubmitTimeout="0" dir.corp.backGroundSync="1" dir.corp.baseDN="OU=xxx,OU=addressbook,DC=xxx,DC=xxx" dir.corp.bindOnInit="1" dir.corp.cacheSize="128" dir.corp.domain="" dir.corp.filterPrefix="" dir.corp.pageSize="32" dir.corp.password="xxx" dir.corp.port="389" dir.corp.scope="sub" dir.corp.sortControl="0" dir.corp.transport="TCP" dir.corp.user="uid=xxx,ou=xxx,ou=accounts,dc=xxx,dc=xxx" dir.corp.viewPersistence="0"> <dir.corp.backGroundSync dir.corp.backGroundSync.period="86400"> </dir.corp.backGroundSync> <dir.corp.attribute dir.corp.attribute.1.filter="" dir.corp.attribute.1.label="Nachname" dir.corp.attribute.1.name="sn" dir.corp.attribute.1.searchable="1" dir.corp.attribute.1.sticky="0" dir.corp.attribute.1.type="last_name" dir.corp.attribute.2.filter="" dir.corp.attribute.2.label="Firma" dir.corp.attribute.2.name="o" dir.corp.attribute.2.searchable="0" dir.corp.attribute.2.sticky="0" dir.corp.attribute.2.type="other" dir.corp.attribute.3.filter="" dir.corp.attribute.3.label="Vorname" dir.corp.attribute.3.name="givenName" dir.corp.attribute.3.searchable="0" dir.corp.attribute.3.sticky="0" dir.corp.attribute.3.type="first_name" dir.corp.attribute.4.filter="" dir.corp.attribute.4.label="Nummer" dir.corp.attribute.4.name="telephoneNumber" dir.corp.attribute.4.searchable="0" dir.corp.attribute.4.sticky="0" dir.corp.attribute.4.type="phone_number"> </dir.corp.attribute> </dir.corp> <dir.corp.vlv dir.corp.vlv.allow="1" dir.corp.vlv.sortOrder="sn givenName"> </dir.corp.vlv> </dir>
We have installed the license on the telephone to use ldap. Ldap is working, the phone can search Names from the addressbook. But if i search a name with umlaut e.g. "hö" then the following is happend:
SIP <= 3.3.5 -> telephone reboot ( i cant see any requests on server)
SIP 4.0.0 -> no reboot, but no entry found..
SIP 4.1.0 -> telephone reboot. ( i cant see any requests on server)
But if i search "hö" by using the advanced search, all is correct.
i have debugt our ldap-server and see the problem.
SIP 4.0
Quicksearch example (Polycom genereates the following filter, which is wrong):
(&(sn>=0)(sn<=zz)(?sn=h\FFFFFFC3\FFFFFFB6*))
Advancedsearch example (Polycom genereates the following filter which is okay):
(&(sn>=0)(sn<=zz)(sn=h\C3\B6*))
FFFFFF <- what is this???
thanks
Our System:
openldap-2.4.35 (testet also with openldap-2.4.12)
Debian Squeeze
Polycom IP 321 / IP 320
Regards
Sebastian
Hello Sebastian,
welcome to the Polycom Community.
This requires full troubleshooting via Support and I suggest to either raise a ticket via your Polycom reseller and/or contact Polycom support directly.
They will most likely instruct you to provide a Wireshark trace from a spanned port and changing of the LDAP log levels.
Please ensure to provide some feedback if this reply has helped you so other users can profit from your experience.
Best Regards
Steffen Baier
Polycom Global Services
If official support is required please check how to phone or open a case here
----------------Hi,
thanks for the answer. My Problem is 1 years old and i have allready opend 3 service Tickets in this time. Polycom says that i must contact my Polycom reseller for an RMA, and i have no support rights by Polycom..?!
I think our reseller cant help us. I think the error is in the phone firmware.
Yesterday i have an workaround for out IP 321 (but not IP320) Phones created:
Polycom ldap filter is wrong: (&(sn>=0)(sn<=zz)(?sn=h\FFFFFFC3\FFFFFFB6*))
LDAP RFC: LDAP want an 2 hex key after "\"...
FFFFFF <- is wrong
i have configured our ldapserver to rewrite the searchFilter:
slapd.conf:
overlay rwm rwm-rewriteEngine on rwm-rewriteContext default rwm-rewriteContext searchFilter rwm-rewriteRule "(.*)\FFFFFF(.*)" "$1\$2"
Result:
Openldap search now correct: (&(sn>=0)(sn<=zz)(?sn=h\C3\B6*))
This only works on SIP 4.0 what is not compatible to "Polycom SoundPoint IP 320"
All other SIP Firmwares cant create an search filter. There are en fatal exception on the telephone and reboot.
Testet firmware:
3.3.0
3.3.1
3.3.2
3.3.3
3.3.4
3.3.5 (latest Version for IP320)
The same error comes:
- if no ldap Server are reachabel (also set an not existing server.address IP)
- No entry are in the ldap directory
- with or without VLV, SORT
In my latest tests, i found the Problem in the new "config" Structure. (SIP < 3.0.0 =sip.cfg is working!!, SIP >= 3.0.0 is not working)
But i want the latest release, to use the new needed features.
In my tests with SIP >=3.0.0, i am used an minimal configuration, only dir.corp, ramdisk (needed on IP320 to change the language to German) . I am used the default configfiles from the SIP Download.
I will make some more tests...
Hello Sebastian,
please email me via the community mail the service tickets so I can look into this.
Best Regards
Steffen Baier
If official support is required please check how to phone or open a case here
----------------Hello Steffen,
i have send you an PM.
Some more tests:
On all SIP >= 3.3.0 i am become the following exception:
0613090247|ldap |1|79|ldapQueryNoSort::fillQuery:query repeating m_qDepth=4 0613090247|ldap |1|79|ldapQueryNoSort::fillQuery:qDepth=<4> same=<0> incl=<No> 0613090247|ldap |1|79|ldapEntry::show:fillQuery::prevTop <BXXXX> <XXXX> <442> <> <> <> <> <> 0613090247|ldap |1|79|ldapEntry::show:fillQuery::prevBot <NXXXX> <XXXX> <411> <> <> <> <> <> 0613090247|ldap |1|79|ldapEntry::show:fillQuery::top <AXXXX> <XXXX> <466> <> <> <> <> <> 0613090247|ldap |1|79|ldapEntry::show:fillQuery::bot <BXXXX> <XXXX> <442> <> <> <> <> <> 0613090247|ldap |1|79|ldapQueryNoSort::fillQuery:query too deep 0613090247|ldap |1|79|cDynamicData::getData:get enabled - filter NOK <> 0613090251|sys |*|79|soSystemLogException vector 2 in tApp1 0613090251|sys |*|79|soSystemLogException running taskShow: 0613090251|sys |*|79|################ ################ 0613090251|sys |*|79| 0613090251|sys |*|79| NAME ENTRY TID PRI STATUS PC SP ERRNO DELAY 0613090251|sys |*|79|---------- ------------ -------- --- ---------- -------- -------- ------- ----- 0613090251|sys |*|79|tApp1 9432b380 94af47f0 170 SUSPEND 944dcae4 94af4140 380003 0 0613090251|sys |*|79| 0613090251|sys |*|79|stack: base 0x94af47f0 end 0x94aeb7f0 size 36848 high 11632 margin 25216 0613090251|sys |*|79| 0613090251|sys |*|79|options: 0x4 0613090251|sys |*|79|VX_DEALLOC_STACK 0613090251|sys |*|79| 0613090251|sys |*|79|VxWorks Events 0613090251|sys |*|79|-------------- 0613090251|sys |*|79|Events Pended on : Not Pended 0613090251|sys |*|79|Received Events : 0x0 0613090251|sys |*|79|Options : N/A 0613090251|sys |*|79| 0613090251|sys |*|79|$0 = 0 t0 = 9c01 s0 = 0 t8 = 711880 0613090251|sys |*|79|at = 1 t1 = 9c00 s1 = 0 t9 = 18 0613090251|sys |*|79|v0 = 36008d84 t2 = 4 s2 = 0 k0 = 0 0613090251|sys |*|79|v1 = 36008d80 t3 = 0 s3 = 0 k1 = 0 0613090251|sys |*|79|a0 = 94a2f342 t4 = 0 s4 = 0 gp = 94872280 0613090251|sys |*|79|a1 = 94a2f312 t5 = 36 s5 = 0 sp = 94af4140 0613090251|sys |*|79|a2 = 18 t6 = 18 s6 = 0 s8 = 94af4140 0613090251|sys |*|79|a3 = 8 t7 = 29e528 s7 = 0 ra = 944dcadc 0613090251|sys |*|79|divlo = 0 divhi = 0 sr = 9c01 pc = 944dcae4 0613090251|sys |*|79|soSystemLogException running tt: 0613090251|sys |*|79|################ ################ 0613090251|sys |*|79|940ac990 : 940a8600 (94c81920, 2, 1, 0) 0613090251|sys |*|79|940a879c : 944dc87c (94af41c8, 946e4bc0, 94af41f0, 94af41f8) 0613090251|sys |6|79|soSystemLogException logging complete, rebooting...
Regards
Sebastian
Hi Sebastian,
I have asked our T2 support to look into this and re-open your latest ticket.
Best Regards
Steffen Baier
If official support is required please check how to phone or open a case here
----------------thank you very much
Hello,
Is there news here?
In the log file, it says "query too deep".
0613090247|ldap |1|79|ldapQueryNoSort::fillQuery:query too deep
I have that same message when querying OpenLDAP:
1129084756|ldap |1|00|[findSubset:255] found=<Yes> data=<Ve9gfi> subset=<0>
1129084756|ldap |1|00|[setQLimits:212] 1::<UP> m_curSubset=<0/1>
1129084756|ldap |1|00|[show:310] setQLimits 1::top <Ve9gfi>
1129084756|ldap |1|00|[show:310] setQLimits 1::bot <zz>
1129084756|ldap |1|00|[assmCondition:384] ...1
1129084756|ldap |1|00|[fillQuery:435] qDepth=<1> same=<0> incl=<Yes>
1129084756|ldap |1|00|[show:310] fillQuery::prevTop <Ve9gfi>
1129084756|ldap |1|00|[show:310] fillQuery::prevBot <zz>
1129084756|ldap |1|00|[show:310] fillQuery::top <Ve9gfi>
1129084756|ldap |1|00|[show:310] fillQuery::bot <Ve9gfi>
1129084756|ldap |1|00|[fillQuery:494] query too deep
1129084756|ldap |0|00|[assmQuery:170] assmCondition error numC=<-1>
1129084756|ldap |0|00|[assmQuery:179] query cleared & released
And here is my configuration with a VVX-600:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<!-- Generated features.cfg Configuration File -->
<polycomConfig xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="polycomConfig.xsd">
<dir>
<dir.corp
dir.corp.address="ldap://dir.hamshackhotline.com"
dir.corp.autoQuerySubmitTimeout="0"
dir.corp.backGroundSync="0"
dir.corp.baseDN="ou=phones,ou=phonebook,dc=hamshackhotline,dc=com"
dir.corp.bindOnInit="0"
dir.corp.cacheSize="128"
dir.corp.cacheSize.VVX101="64"
dir.corp.customError=""
dir.corp.domain=""
dir.corp.filterPrefix=""
dir.corp.pageSize="32"
dir.corp.pageSize.VVX101="16"
dir.corp.password=""
dir.corp.persistentCredentials="0"
dir.corp.port="389"
dir.corp.querySupportedControlOnInit="1"
dir.corp.scope="sub"
dir.corp.serverSortNotSupported="0"
dir.corp.sortControl="0"
dir.corp.transport="TCP"
dir.corp.user=""
dir.corp.viewPersistence="0">
<dir.corp.allowCredentialsFromUI
dir.corp.allowCredentialsFromUI.enabled="0">
</dir.corp.allowCredentialsFromUI>
<dir.corp.attribute
dir.corp.attribute.1.addstar="0"
dir.corp.attribute.1.filter="(callsign=%)"
dir.corp.attribute.1.label="callsign"
dir.corp.attribute.1.name="callsign"
dir.corp.attribute.1.searchable="1"
dir.corp.attribute.1.sticky="0"
dir.corp.attribute.1.type="first_name">
</dir.corp.attribute>
<dir.corp.auth
dir.corp.auth.useLoginCredentials="0">
</dir.corp.auth>
<dir.corp.backGroundSync
dir.corp.backGroundSync.period="86400">
</dir.corp.backGroundSync>
<dir.corp.viewPersistence
dir.corp.viewPersistence.form="1">
</dir.corp.viewPersistence>
<dir.corp.vlv
dir.corp.vlv.allow="0"
dir.corp.vlv.sortOrder="cn telephoneNumber">
</dir.corp.vlv>
</dir.corp>
<dir.local
dir.local.passwordProtected="0"
dir.local.readonly="0"
dir.local.UIenabled="1">
<dir.local.contacts
dir.local.contacts.maxNum="500"
dir.local.contacts.maxNum.VVX101="99"
dir.local.contacts.maxNum.VVX150="99"
dir.local.contacts.maxNum.VVX1500="9999"
dir.local.contacts.maxNum.VVX201="99">
</dir.local.contacts>
</dir.local>
<dir.search
dir.search.field="0">
</dir.search>
</dir>
<feature
feature.corporateDirectory.enabled="1"
log.render.level="0"
log.render.file.upload.append.sizeLimit="51200"
log.render.file.size="1000"
log.level.change.ldap="0"
</feature>
</polycomConfig>
The data that I'm hoping to query is at DN=ou=phones,ou=phonebook,dc=hamshackhotline,dc=com
And when I query using Apache Directory, I get the data that I expect.
Thanks,
Greg
Hello @VE9GFI ,
Welcome to the Poly Community.
Both the communities Must Read First or Read 1st and if available the FAQ reference the basic minimum information a new or follow-up post should contain.
This ensures the questions having to be asked are limited and any new or follow-up post contains the right amount of details to ensure any voluntary participant within the community does not spend additional time chasing basic information.
Unfortunately, your post fell a bit short of the above-explained requirements and we kindly ask you, therefore, to ensure to read these sections and ensure a reply (not Edit!) provides as much detail as possible
Please ensure you familiarise yourself with the FAQs listed in my signature for your convenience.
The best and quickest way forward is to contact our Support organization as the community is run by volunteers only.
Please ensure to provide some feedback if this reply has helped you so other users can profit from your experience.
Best Regards
Steffen Baier
If official support is required please check how to phone or open a case here
----------------