Hi,
I’m quite new on this forum so I appologize for any stupid question. If I’m wrong please correct me.
Now question:
Does anyone now how to use Linksys Corporate Directory in Linksys SPA-9XX phones with out SPA-9000 Key system? I was googling but found nothing usefull.
Best regards
Piotr Goczal
the best place to start would be the admin guide for the spa-9xx phone. I don’t think they are made publicly available, so good luck finding one.
The next thing to do would be to set up a TFTP server and watch what the phone is trying to grab from it. I have a feeling there will be a csv or xml directory in there somewhere. Then find someone who has a 9000 and ask them to tftp grab that file and send it to you. You can then figure out the format and write your own…
[quote=“IronHelix”]the best place to start would be the admin guide for the spa-9xx phone. I don’t think they are made publicly available, so good luck finding one.
[/quote]
I’ve access to this guide and of course there is nothing about corporate directory.
[quote=“IronHelix”]
The next thing to do would be to set up a TFTP server and watch what the phone is trying to grab from it. I have a feeling there will be a csv or xml directory in there somewhere. Then find someone who has a 9000 and ask them to tftp grab that file and send it to you. You can then figure out the format and write your own…[/quote]
No, it’s done via SIP INFO message.
Etheral says:
Phone:
Request-Line: INFO sip:dir@ip_of_asterisk_box SIP/2.0
Method: INFO
Asterisk:
Status-Line: SIP2.0 403 Unauthorized
Status-Code 403
Regards
Piotr
I think if you go read a little you will find that IronHelix is correct.
the phone can be provisioned three ways http / https / TFTP
in the gui you would need to set the tftp to on.
[quote=“bubba”]
the phone can be provisioned three ways http / https / TFTP
in the gui you would need to set the tftp to on.[/quote]
Yes, phone can be provisioned but tftp, http, and https but in my opinion corporate directory is not done via tftp (unfortunatelly).
Debug from asterisk:
<-- SIP read from 212.191.2.17:50601:
INFO sip:dir@212.191.2.2 SIP/2.0
Via: SIP/2.0/UDP 212.191.2.17:50601;branch=z9hG4bK-2a2e75f6;rport
From: “Piotr Goczal” sip:XXX@212.191.2.2;tag=d042bee5d3707c80o0
To: sip:dir@212.191.2.2
Call-ID: 121c6e86-6f353092@212.191.2.17
CSeq: 2784 INFO
Max-Forwards: 70
User-Agent: Linksys/SPA941-4.1.15
Content-Length: 0
— (9 headers 0 lines)—
Receiving INFO!
Transmitting (no NAT) to 212.191.2.17:50601:
SIP/2.0 403 Unauthorized
Via: SIP/2.0/UDP 212.191.2.17:50601;branch=z9hG4bK-2a2e75f6;rport;received=212.191.2.17
From: “Piotr Goczal” sip:XXX@212.191.2.2;tag=d042bee5d3707c80o0
To: sip:dir@212.191.2.2;tag=as167b23e7
Call-ID: 121c6e86-6f353092@212.191.2.17
CSeq: 2784 INFO
User-Agent: Asterisk PBX
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Content-Length: 0
Regards
Piotr