asterisk users - Mar 2003 - ADSI Programming of the Aastra Powertouch 480

Hello list,

First, * kicks butt in about every way.

Next, I have a little problem I was hoping you might be able to help me
with.  Some of you may recognize me from the IRC channel.  This is my
first post, so I apologize in advance for its length.

I've acquired a T400P (Quad T1 card) and two Zhone Z-Plex 10
Channel Banks from Digium.  They mostly work fine (one Zhone has an
intermittent problem that is not related to this).  Upon building
Asterisk from CVS, I was surprised how much of it worked so very well.
Emboldened by this, I set out to order some ADSI phones to capitalize on
this feature.

I purchased two Aastra Powertouch 480 phones through one of their major
distributors.  It was purportedly unprogrammed and unlocked.

I connected the phone and set up an extension for the GetCPEID app.
This worked swimmingly.  I then attempted to complete the gauntlet by
using the ADSIProg application to program it.  That, however, does not
work.

I was told by various people on the IRC channel that they believed I had
a locked phone.  After much consultation I have determined that a
successful upload requires the following:
 * The correct feature description number.
 * The correct security code for the phone.
 * A slot without the locked flag enabled.

The example configuration as well as the representative at Sayson (a 3rd
party service that will program ADSI phones with custom scripts for
customers who just need "pretty buttons") claimed as well that
0x0000000f was the correct FDN.

Through their service, I was able to determine that this phone was also
programmable with security code 0x00000000.  I also was given
information on how to reset this phone to factory setup (thus removing
any "locked" slots but not resetting any security code).  If anyone
wants that procedure, let me know.

Finally, I was able to verify that all slots were empty (all showed
<available> in the services list.

So basically, this phone is unlocked and can be programmed with no
security code by multiple 3rd party services, but not ADSIProg.

I have gotten relatively far with support from Sayson and Aastra, but
the vibe I'm getting at this point is that "ADSI is a standard, we
implement it but we're not responsible for helping you develop your
implementation".  The specs are available from Telcordia (and perhaps
belcor?) for a paltry few k$.

On the hard facts side, attempting to program it from both the Voicemail
system and ADSIProg causes the following message to appear on the
screen:
    +--------------------+
    | Asterisk PBX       |
    | download refused.  |
    | Conflict with:     |
    |  <available>       |
    +--------------------+
      -                -
      -                -
      -                - Quit

As you might think, an error message saying there is a conflict with an
empty slot is confusing to me.  Looking at the source it appears the
function that does this (adsi_begin_download) sends an
ADSI_DOWNLOAD_CONNECT and then proceeds to send the compiled script.
Looking at adsi.h, I notice there is also an ADSI_LOAD_SCRIPT function
that does not appear to be used by Asterisk.  I've been wondering if
perhaps this Aastra phone (earlier ones appear to work without a hitch)
implements the standard differently.  Specifically, it mentions in their
brochure that it is ADSI 2.0 compatible.  That makes me wonder if there
hasn't been some sort of clarification in terms of which ADSI command
codes are used here.

The failure in communication is very basic, as this problem occurs in
the connection function (really the first bytes sent to the darn thing).
As I can't afford the spec, if someone could clear this up, I'd
appreciate it--as this is the last hurdle to clear before adopting this
at our site!

Thanks,

Jayson Vantuyl
Computing Edge, Inc.

Hello list,

First, * kicks butt in about every way.  If you recieve this twice,
sorry about that.  I accidently sent it from the wrong address the first
time.

Next, I have a little problem I was hoping you might be able to help me
with.  Some of you may recognize me from the IRC channel.  This is my
first post, so I apologize in advance for its length.

I've acquired a T400P (Quad T1 card) and two Zhone Z-Plex 10
Channel Banks from Digium.  They mostly work fine (one Zhone has an
intermittent problem that is not related to this).  Upon building
Asterisk from CVS, I was surprised how much of it worked so very well.
Emboldened by this, I set out to order some ADSI phones to capitalize on
this feature.

I purchased two Aastra Powertouch 480 phones through one of their major
distributors.  It was purportedly unprogrammed and unlocked.

I connected the phone and set up an extension for the GetCPEID app.
This worked swimmingly.  I then attempted to complete the gauntlet by
using the ADSIProg application to program it.  That, however, does not
work.

I was told by various people on the IRC channel that they believed I had
a locked phone.  After much consultation I have determined that a
successful upload requires the following:
 * The correct feature description number.
 * The correct security code for the phone.
 * A slot without the locked flag enabled.

The example configuration as well as the representative at Sayson (a 3rd
party service that will program ADSI phones with custom scripts for
customers who just need "pretty buttons") claimed as well that
0x0000000f was the correct FDN.

Through their service, I was able to determine that this phone was also
programmable with security code 0x00000000.  I also was given
information on how to reset this phone to factory setup (thus removing
any "locked" slots but not resetting any security code).  If anyone
wants that procedure, let me know.

Finally, I was able to verify that all slots were empty (all showed
<available> in the services list.

So basically, this phone is unlocked and can be programmed with no
security code by multiple 3rd party services, but not ADSIProg.

I have gotten relatively far with support from Sayson and Aastra, but
the vibe I'm getting at this point is that "ADSI is a standard, we
implement it but we're not responsible for helping you develop your
implementation".  The specs are available from Telcordia (and perhaps
belcor?) for a paltry few k$.

On the hard facts side, attempting to program it from both the Voicemail
system and ADSIProg causes the following message to appear on the
screen:
    +--------------------+
    | Asterisk PBX       |
    | download refused.  |
    | Conflict with:     |
    |  <available>       |
    +--------------------+
      -                -
      -                -
      -                - Quit

As you might think, an error message saying there is a conflict with an
empty slot is confusing to me.  Looking at the source it appears the
function that does this (adsi_begin_download) sends an
ADSI_DOWNLOAD_CONNECT and then proceeds to send the compiled script.
Looking at adsi.h, I notice there is also an ADSI_LOAD_SCRIPT function
that does not appear to be used by Asterisk.  I've been wondering if
perhaps this Aastra phone (earlier ones appear to work without a hitch)
implements the standard differently.  Specifically, it mentions in their
brochure that it is ADSI 2.0 compatible.  That makes me wonder if there
hasn't been some sort of clarification in terms of which ADSI command
codes are used here.

The failure in communication is very basic, as this problem occurs in
the connection function (really the first bytes sent to the darn thing).
As I can't afford the spec, if someone could clear this up, I'd
appreciate it--as this is the last hurdle to clear before adopting this
at our site!

Thanks,

Jayson Vantuyl
Computing Edge, Inc.

The phone still appears to be "locked" as we get a similar error on
our
locked Vista 350's.  The unlocked 390's we have do not get this error
message.

You mentioned that you have an "unlock" procedure.  Would you mind
passing
this on?  I could try it on my 350 to see if it works.
> I connected the phone and set up an extension for the GetCPEID app.
> This worked swimmingly.  I then attempted to complete the gauntlet by
> using the ADSIProg application to program it.  That, however, does not
> work.
> 
> I was told by various people on the IRC channel that they believed I had
> a locked phone.  After much consultation I have determined that a
> successful upload requires the following:
>  * The correct feature description number.
>  * The correct security code for the phone.
>  * A slot without the locked flag enabled.

>I connected the phone and set up an extension for the GetCPEID app.
I have a 480 & it is completely *UNLOCKED* why dont you post that getCPEID
data & lets see if we have the same version Info
>The example configuration as well as the representative at Sayson (a 3rd
>party service that will program ADSI phones with custom scripts for
>customers who just need "pretty buttons") claimed as well that
>0x0000000f was the correct FDN.
that is correct for feature slot 1 & 2
the 3rd slot is 0xffffffff
& the auto load slot (4th slot) is 0x01000006 & the same for the
security
code

>Through their service, I was able to determine that this phone was also
>programmable with security code 0x00000000.  I also was given
>information on how to reset this phone to factory setup (thus removing
>any "locked" slots but not resetting any security code).  If
anyone
>wants that procedure, let me know.
can you post this procedure for ALL of us the ML

> I have gotten relatively far with support from Sayson and Aastra, but
> the vibe I'm getting at this point is that "ADSI is a standard, we
> implement it but we're not responsible for helping you develop your
> implementation".  The specs are available from Telcordia (and perhaps
> belcor?) for a paltry few k$.
Alex Pilosov and Digium both kicked in to purchase ths spec for the
implementation, and it was the Telcordia specs that our ADSI
implementation is based upon.
> On the hard facts side, attempting to program it from both the Voicemail
> system and ADSIProg causes the following message to appear on the
> screen:
>     +--------------------+
>     | Asterisk PBX       |
>     | download refused.  |
>     | Conflict with:     |
>     |  <available>       |
>     +--------------------+
>       -                -
>       -                -
>       -                - Quit
>
> As you might think, an error message saying there is a conflict with an
> empty slot is confusing to me.
This is what happens when your phone is locked.  Factory reset does not
reset the lock.  The lock feature was implemented so that vendors could
tie you to their particular variant of the Astra phones.  The idea of a
PBX *without* tying you to a specific phone is so inconceivable that, as
far as I know, it is not really possible to purchase phones in general
that are not locked -- although I think Greg Vance had made some progress
along such a path at one point.

Mark

>Well, I almost cried... Here's why:
>
>I followed the unlock procedure on my unlocked 390, and it worked as
>outlined, so I did the big test; I tried to unlock my 350 that I've been
>trying to unlock for months.
>
>There isn't a Mute button, so I hit the Flash button instead.  Voila, it
>said "Memory erase".  I tried programming it with ADSIProg, and
WOOHOO!  It
>worked!  My previously impermeable Vista 350 is now Asterisk-ADSI capable!
>
>THANK YOU THANK YOU THANK YOU!
>
>There are several others on this list that will be just as happy to hear
>this!
>
http://www.telephonedepot.ca/item69.htm
Wade ..Gotta call these guys Friday AM , & see if we can get em to test a
few
us ~ $42/Unit
WaHOOO

On Thu, Mar 27, 2003 at 04:45:20PM -0800, TC wrote:
> I have a 480 & it is completely *UNLOCKED* why dont you post that
getCPEID
> data & lets see if we have the same version Info
Which security code did you use to program it?  Just 0x00000000 (that is
the code for *UNLOCKED* phones, right?)?

Jayson