Problem changing a key

[riteeh]

Hello,

I am having this problem with a PBX when attempting to change a couple of keys on a TN on a customer's PBX. This problem is happening on multiple TNs with different DNs so it is not a single TN causing the error.

TN: 005 0 01 07
Current KEY value: 00 SCR 4101 0 MARP
Current KEY value: 01 SCR 5101 0 MARP
Desired KEY value: 00 SCR 2101 0 MARP
Desired KEY value: 01 SCR 3101 0 MARP

Here is a log of what happens:

LD 11<CR>

REQ: CHG<CR>
TYPE: 3903<CR>
TN 005 0 01 07ÃSCH0030 (pbx sent garbage byte, this happens fairly often on this PBX with the TN prompt)
TN 005 0 01 07<CR> (resent TN)
..
.. (<CR> through every prompt until KEY, no more garbage received from PBX)
..
KEY 00 SCR 2101 HNT FNA<CR>SCH0600 (PBX outputted 'HNT FNA' as soon as I have space after inputting the DN)
KEY 01 SCR 3101 HNT FNA 0<CR>Ã (this time I sent the ' 0' anyway and the PBX sent SCH6712)
SCH6712

At this point I logour and give up. What is going on here? Is this a symptom of DN/TN block corruption? I have not tried this same transaction by omitting the CLID (' 0') in case the database is corrupt.

Thanks in advance for any info or suggestions.

 

[cmawbey]

try a NUL on key x first then reassign it

 

[acewarlock]

Does this only happen on this 1 TTY, or does it happen on any TTY you try it on?

May be a bad TTY/Term


This is a Signature and not part of the answer, it appears on every reply.

This is an Analogy so don't take it personally as some have.

Why change the engine if all you need is to change the spark plugs.

 

[geirendre]

Hum... didn't think you could do it that way.
Shouldn't it be like this:

REQ: chg
TYPE: 3904
TN   12 0 0 0
ECHG yes
ITEM key 2 scr 54321 hnt fna
SCH6711
SCH6712
SCH0360
     KEY 2 scr 54321 hnt fna 0
SCH6712
SCH0360     #No luck that way, try this:
     KEY 2 scr 54321
       MARP
       CPND
       VMB
     KEY
ITEM cls hta
ITEM hunt 0
ITEM cls fna
ITEM fdn 0
ITEM

Or am I missing something?

 

[acewarlock]

Your missing something.

If SCR 2101 exisits on another phone, than thats why you get the HNT FNA after you do a space after the DN. the other set is controlling it.


This is a Signature and not part of the answer, it appears on every reply.

This is an Analogy so don't take it personally as some have.

Why change the engine if all you need is to change the spark plugs.

 

[riteeh]

acewarlock,

2101 and 3101 do in fact exist on a different TN. It seems strange that HNT FNA would be prompted. I would have expected a SCH code if there was an issue with inputting the CLID.

What would be the correct way to handle this situation? I presume performing the CHG without providing a CLID should go through successfully? The second appearance of this DN will be removed, but we want to add it to the new TN before removing it from the old one.

Thanks for the help thus far.

 

[acewarlock]

It is giving the HNT FNA as this is what it is on the other phone and right now it is the MARP phone and controlling it.
You can just make the change and then change it on the other phone and then prt the 1st phone to see if you need to make any more changes.

Can i ask, are you just swapping these phone with each other?


This is a Signature and not part of the answer, it appears on every reply.

This is an Analogy so don't take it personally as some have.

Why change the engine if all you need is to change the spark plugs.

 

[riteeh]

acewarlock,

Thanks for the info. A user has moved to a new location that already contains a phone programmed with DN, so we're just changing KEY 0 and KEY 1 to be the same as his old phone and disabling the old phone.

Thanks

 

[Nortellian]

Fix the tty. It is causing you problems by sending illegal characters.

 

[acewarlock]

It would be easier to swap the crossconnects or swap the TN's.


This is a Signature and not part of the answer, it appears on every reply.

This is an Analogy so don't take it personally as some have.

Why change the engine if all you need is to change the spark plugs.