SPA9k - New Firmware supporting LDAP

[Zeko]

There are new firmware for SPA9k phones that provides LDAP corporate directory search option. (6.1.3a 9/30/2008)

Has anybody tried this LDAP feature ?

Is it possible to install LDAP server on Windows or Linux in order
to maintain shared phonebook now ? (not just when hosted on LinkSYS PBX platform)

[bull_tpk]

To keep things simple and for a small phone system, I would prefer it to be simple like share the reception phone's 100 number directory. Then they can easily admininster it themselves

[karakal]

I wasn't able to connect my SPA962 with the new firmware to our Active Directory Server (which is a LDAP Server)... :-(

[Zeko]

I have upgraded SPA922 and SPA942 to new firmware 6.1.3a.

Both phones are not trying to communicate with LDAP server at all.

LDAP field options in release notes are not same as in phone WEB user interface.

[karakal]

I had problems with the other features of the new firmware too. And my phone wasn't stable anymore. It turned out that I had to do a factory-reset after upgrading the firmware and to reconfigure my phones.

After that, the other new features worked out fine.

I will attempt to configure LDAP again and keep you all informed about my failure or success.

[Zeko]

I have tried BLF and SD with SPA942 and Asterisk.

Working fine.

[humba3]

@Zeko: what's the syntax you used for Asterisk? Did you get pickup to work as well (afaik pickup uses * codes and not the RFC to pick up calls so it might be different.. I know the phones use RFC to pick up themselves (worked without a glitch on my Epygi Quadro))?

[Zeko]

;sip.conf

notifyringing=yes
notifyhold=yes
Subscribecontext=blf_context
limitonpeers = yes ; important

[phone111]
type=friend
call-limit=1

;extensions.conf

[blf_context]
exten => 111,hint,SIP/phone111



;SPA 942, LineKey2
Extension: disabled
Short Name: OtherPhone
Share Call Appearance: private
Extended Function: fnc=blf+sd;sub=112@$PROXY

[Mr.Mekulic]

Phone SPA 962 fw:6.1.3a
Asterisk:1.4.11 tried also on 1.4.21.2

I've tried Zeko-s settings, but I get an warning in asterisk:

[Oct 15 15:12:24] WARNING[2461]: chan_sip.c:14673 handle_request_subscribe: SUBS
CRIBE failure: unrecognized format: 'multipart/related' pvt: subscribed: 0, stat
eid: -1, laststate: 0, dialogver: 0, subscribecont: '', subscribeuri: ''

and here is SIP debug for the peer, the warning message keeps repeating so here is debug from one warning to the next:

[Oct 15 15:12:24] WARNING[2461]: chan_sip.c:14673 handle_request_subscribe: SUBS
CRIBE failure: unrecognized format: 'multipart/related' pvt: subscribed: 0, stat
eid: -1, laststate: 0, dialogver: 0, subscribecont: '', subscribeuri: ''
Really destroying SIP dialog '73f24ab1-83ccc742@10.0.0.121' Method: SUBSCRIBE
    -- Zap/1-1 is ringing
Reliably Transmitting (no NAT) to 10.0.0.121:5060:
OPTIONS sip:224@10.0.0.121:5060 SIP/2.0
Via: SIP/2.0/UDP 10.0.0.26:5060;branch=z9hG4bK5527f483
From: "asterisk" <sip:asterisk@10.0.0.26>;tag=as632a9d98
To: <sip:224@10.0.0.121:5060>
Contact: <sip:asterisk@10.0.0.26>
Call-ID: 24ae4cbc266fea0d3a17457f7f51321b@10.0.0.26
CSeq: 102 OPTIONS
User-Agent: PBX Lama
Max-Forwards: 70
Date: Wed, 15 Oct 2008 13:12:53 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Supported: replaces
ontent-Length: 0


---
pbx*CLI>
<--- SIP read from 10.0.0.121:5060 --->
SIP/2.0 200 OK
To: <sip:224@10.0.0.121:5060>;tag=84d1e5fe9015596di0
From: "asterisk" <sip:asterisk@10.0.0.26>;tag=as632a9d98
Call-ID: 24ae4cbc266fea0d3a17457f7f51321b@10.0.0.26
CSeq: 102 OPTIONS
Via: SIP/2.0/UDP 10.0.0.26:5060;branch=z9hG4bK5527f483
Server: Linksys/SPA962-6.1.3(a)
Content-Length: 0
Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER
Supported: replaces


<------------->
--- (10 headers 0 lines) ---
Really destroying SIP dialog '24ae4cbc266fea0d3a17457f7f51321b@10.0.0.26' Method
: OPTIONS
pbx*CLI>
<--- SIP read from 10.0.0.121:5060 --->
SUBSCRIBE sip:208@10.0.0.26 SIP/2.0
Via: SIP/2.0/UDP 10.0.0.121:5060;branch=z9hG4bK-b5ebcf84
From: "224" <sip:224@10.0.0.26>;tag=bc1374011313fd48
To: <sip:208@10.0.0.26>
Call-ID: 763baab8-b0c41aa1@10.0.0.121
CSeq: 1001 SUBSCRIBE
Max-Forwards: 70
Contact: "224" <sip:224@10.0.0.121:5060>
Accept: multipart/related
Accept: application/rlmi+xml
Accept: application/dialog-info+xml
Expires: 1800
Event: dialog
User-Agent: Linksys/SPA962-6.1.3(a)
Content-Length: 0
Supported: replaces, eventlist


<------------->
--- (16 headers 0 lines) ---
Creating new subscription
Sending to 10.0.0.121 : 5060 (no NAT)
Found peer '224'

<--- Transmitting (no NAT) to 10.0.0.121:5060 --->
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 10.0.0.121:5060;branch=z9hG4bK-b5ebcf84;received=10.0.0.121
From: "224" <sip:224@10.0.0.26>;tag=bc1374011313fd48
To: <sip:208@10.0.0.26>;tag=as2d391e23
Call-ID: 763baab8-b0c41aa1@10.0.0.121
CSeq: 1001 SUBSCRIBE
User-Agent: PBX Lama
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Supported: replaces
WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="7b60b2cb"
Content-Length: 0


<------------>
Scheduling destruction of SIP dialog '763baab8-b0c41aa1@10.0.0.121' in 832 ms (M
ethod: SUBSCRIBE)
pbx*CLI>
<--- SIP read from 10.0.0.121:5060 --->
SUBSCRIBE sip:208@10.0.0.26 SIP/2.0
Via: SIP/2.0/UDP 10.0.0.121:5060;branch=z9hG4bK-83c719cc
From: "224" <sip:224@10.0.0.26>;tag=bc1374011313fd48
To: <sip:208@10.0.0.26>
Call-ID: 763baab8-b0c41aa1@10.0.0.121
CSeq: 1002 SUBSCRIBE
Max-Forwards: 70
Authorization: Digest username="224",realm="asterisk",nonce="7b60b2cb",uri="sip:
208@10.0.0.26",algorithm=MD5,response="6424492e5b9d3f94cbed25b4185eecff"
Contact: "224" <sip:224@10.0.0.121:5060>
Accept: multipart/related
Accept: application/rlmi+xml
Accept: application/dialog-info+xml
Expires: 1800
Event: dialog
User-Agent: Linksys/SPA962-6.1.3(a)
Content-Length: 0
Supported: replaces, eventlist


<------------->
--- (17 headers 0 lines) ---
Creating new subscription
Sending to 10.0.0.121 : 5060 (no NAT)
Found peer '224'
Looking for 208 in sip (domain 10.0.0.26)

<--- Transmitting (no NAT) to 10.0.0.121:5060 --->
SIP/2.0 489 Bad Event (format multipart/related)
Via: SIP/2.0/UDP 10.0.0.121:5060;branch=z9hG4bK-83c719cc;received=10.0.0.121
From: "224" <sip:224@10.0.0.26>;tag=bc1374011313fd48
To: <sip:208@10.0.0.26>;tag=as2d391e23
Call-ID: 763baab8-b0c41aa1@10.0.0.121
CSeq: 1002 SUBSCRIBE
User-Agent: PBX Lama
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Supported: replaces
Content-Length: 0


<------------>
[Oct 15 15:12:54] WARNING[2461]: chan_sip.c:14673 handle_request_subscribe: SUBS
CRIBE failure: unrecognized format: 'multipart/related' pvt: subscribed: 0, stat
eid: -1, laststate: 0, dialogver: 0, subscribecont: '', subscribeuri: ''
Really destroying SIP dialog '763baab8-b0c41aa1@10.0.0.121' Method: SUBSCRIBE

the BLF LED on the phone is amber or "Failed to subscribe (received 4xx response)" to quote the release notes

Could somebody please help me out with this ?

[jlamanna]

Hi,
Did you ever find a resolution for this?

Thanks.