Moving to QSIG

[TIgerV]

Tonight, after hours, I am going to try to move my 4ESS PRI to a QSIG trunk.
In theory, I should be able to do a regen-TDCSU:1-1-1-0,,,,; and then Copy and Paste, changing "ATT4ESS" to "QSIG".

Should it be that easy?

Attached is my table if anyone else wants to help. :-D

TIger

 

[TIgerV]

Can I just do a
CHA-TDCSUROTVAR = QSIG; ???????

TIger

 

[donb01]

I would assume (you know how that goes) that you can just use CHA-XXXX and change the protocol. That's how it works on all my 9006 stuff, and if I remember correctly because it has been a while, usually when you change the first one the system says you can't have differing protocols in the trunk group and changes all the other ones at the same time.

I would deactivate the trunk before changing the protocol, in fact it might make you do it.

I assume if you do a REGEN with the same PEN number even though you are changing a parameter it will try to create a new trunk (because the statement will be an ADD statement) and you will get an error that the PEN is already in use.

I use REGEN in this fashion for quickly creating station copies, but always change the PEN and STNO because it is creating a new one.

 

[TIgerV]

I heard back from Unify last night. It won't let you change the protocol, you have to blow the old trunk group out, reinstall it, and then relink all your routing.

They estimated 30 minutes on the phone.

It's worth it, though. I really need caller ID to prioritize my calls in the queue; and I'm getting "PRIVATE NUMBER" for everyone now.

TIger

 

[sbcsu]

Yes you will need the new PRODE
CHA-PRODEVCD=1;

Have used AT&T 4ESS
Only 23? channels
The rest of them are setup on the 2nd circuit but are left deactivated.

 

[TIgerV]

I stopped on this sentence from the AMO manual: "Use of this AMO requires well-founded specialized knowledge with respect to protocol conversion."





TIger

 

[sbcsu]

Yeah,
I have a system with 4ESS and QSIG setup on it with no issues, however when I set it up the support personnel said - go ahead but we cant support it.
But it has worked fine for years.

 

[sbcsu]

And sorry it's not CHA-PRODE
its
COPY-PRODEVCD,1;

 

[TIgerV]

I didn't get this done, since there is much more involved than I can handle.

However, I am getting 7 digit caller ID from the distant end, and the Hiptah says "PRIVATE NUMBERING PLAN" and doesn't display it on the phones (I can see a good 7 digit ID on the trace!!)

Would moving from 4ESS to QSIG possibly correct this?

TIger

 

[sbcsu]

Add a KNFOR entry for that trunk
Example: ADD-KNFOR:1-1-999,ISDN,INTERNAT,INTERNAT,TRANSP,SEND1,SEND1,YES,IGNOR;
OR
ADD-KNFOR:1-1-220,ISDN,INTERNAT,INTERNAT,TRANSP,SEND1,SEND1,YES,IGNOR;
OR if that does not work
ADD-KNFORNNO=999,NPI=ISDN,TONIN=NATIONAL,TONOUT=NATIONAL;
Where the DNNO is the node specified in the trunk

If this does not work get a REGEN from a system where this incoming numbering works as it could also be the COP/COT setup

 

[TIgerV]

I get the same results. :-(

TIger

 

[TIgerV]

The tonin parameter for the entered dnno becomes only effective if dnno is added to the kndef table, type own


TIger

 

[donb01]

Also in your station config for all your phones if you are using Assistant (which might be the same stuff sbcsu just gave you in AMOs)...

In the BASIC 3 Tab:

Put in a full 10-digit number for Public Number (if in the US)
Fur Numbering Plan Identifier it should be ISDN
For Type of Number it should be National (if in the US)

I don't know if that affects the incoming data, but it will affect the outgoing data. I know when I create a new phone these values are not populated by default, so someone should have entered them at some point, whether that was you or your vendor.

This may or may not have any impact on your results, but it won't hurt!

 

[TIgerV]

Mine are all set.
That changes the outbound, but not inbound.

TIger