Problem with call forwarding HIPATH 4000 V6 2

[youfo007]

hello,

We have HiPath 4000 V6
I have problem with call forwarding

Situation 1:

I receive call from external user (ex. another trunk isdn s2conn) and transfer to another our local user. I receive no answer or busy tone.

Situation 2

I receive call from external user (ex. another trunk isdn s2conn) and I'd like transfer to our other external user through a link. I receive no answer or busy tone.

When I receive no answer or busy tone, the situation remains like this.

I tried to check several parameter (feasu, ziel, COS1, cos2, lcosv1, zand) and the problem still persists.

this is the command I use:


ADD-ACTDA:STN,7854,FWD,STATIONV,CFU,GEN,VCE,6312548;





thanks for any advice

best regards

 

[youfo007]

to be visible and bright, I put in a text file attached

 

[sbcsu]

It is important to change the NODE in RICHT,TDCSU & LDAT

REG-KNDEF;

There is a default one in there that you are using which is site specific.
Grab that line and add in the node 666 with the other values the same.

Change the RICHT,TDCSU & LDAT as previously advised.

Ensure that the node is setup in those three things.


After that if it does not work then you have to start a trace in the assistant to see where/why it is failing

 

[youfo007]

Please how to start a trace in assistant ?

 

[sbcsu]

Is the Node now setup correct ?

It is important to change the NODE in RICHT,TDCSU & LDAT

REG-KNDEF;

There is a default one in there that you are using which is site specific.
Grab that line and add in the node 666 with the other values the same.

Change the RICHT,TDCSU & LDAT as previously advised.


To trace in the assistant:

Open Assistant - If on Atlantic LAN

http://192.0.2.5

Click Client Preparation if not done previously - go through this 'next & next' to ensure you meet all the setup.
If your Java is incorrect you will not be able to do the trace.


When Client Preparation is finished then Logon to Assistant.
Click on 'Diagnostics' on the Left hand menu
(If it is not there then it needs to be enabled)

Click on Switch Diagnosis Support
Then Click Real Time Diagnosis System
Log on there (Any name will do)

Put in the ISDN Pen and start trace

 

[youfo007]

the node which you speak is always DNNO

ok, actually I changed the three (TDCSU, RICHT, LDAT) on the DNNO 666.

the tdcsu on the DNNO is the NNO?

a question on the number to put on the DNNO? that it is arbitrary or must be checked in another setting. because on AMO-ZAND DNNO = 101.?

for the trace, they are attached to it are clear.

I have many questions but I'll give you time to check the first trace.

 

[sbcsu]

Hi
The ZAND is fine,

From the looks of the trace there is an incoming call and then it is trying to call out again on the same B Channel


Please do the following:

REG-COT:10;

CHA-COT:10,COTDEL,AICF&CFTR&CFVA;
CHA-COT:10,COTADD,BSHT;

Try it again then please

 

[youfo007]

the problem is not solved yet unfortunately

although changing the COT

I completely agree with you on that but how? "From the looks of the trace there is an incoming call and then it is trying to call out again on the same B Channel"

attached file you will find the trace for Monitor.


Thanks

 

[sbcsu]

Hi,
Try adding a new COT then assign the trunk to it.
You can always change it back.

ADD-COT:100,RCL&XFER&ANS&CHRT&CEOC&CEBC&CPS6&RCLS&COTN&IEVT&BSHT&LWNC&NLCR&ICZL&ICZO&UUS1&UUS2&UUS3&NITO&SNBE&IICB&CDBO&RCBS&DSDL&LINC&NCHD&USBT&CTLS&NPIS&NOCT&NTON,,;
CHANGE-COT:100,COTADD,,S2COD,"TESTING PRIMARY RATE";

CHA-TDCSUEN=1-1-115-0,COTNO=100,COPNO=100,COTX=100;

To change it back just substitute 2 instead of 100

 

[sbcsu]

With the COT 100 above if you are having problems with incoming direct dial inwards (DDI) then remove the parameter LINC.

Also for reference here is the COP

ADD-COP:100,ANS&L3AR&APPR&RMSG&RRST&DTM1,TA,TA,,;
CHANGE-COP:100,COPADD,,,,S2COD,"TEST PRIMARY RATE";

 

[youfo007]

thank you very much for your help and support

the Forward passed successfully.

but with this solution I have two problems:


I can't dial an external Trunk with 4 number 1xxx, and I can call the same Trunk with 7 number 8xxxxxx.

after the Forwarding the number displayed on the recipient is the number returned and not the number that called.


Thanks for All !!

 

[sbcsu]

So - let me be sure - the COT/COP change has fixed the forwarding problem ??

So for dialling out do a REG-LDPLN; and past here.


For the forwarding number/originator number
Try
CHA-COT:100,COTDEL,NOCT;

Try forwarding, if not fixed then

CHA-COT:100,COTADD,NOCT;
CHA-COT:100,COTDEL,NPIS;

Try forwarding, if not fixed then

CHA-COT:100,COTADD,NPIS;
CHA-COT:200,COTDEL,DSDL;

 

[youfo007]

yes the COP/COT has resolved the problem on the forwarding

Now, I tried to retype all over again with a COT and COP = 10. (attached file).

the Forwarding it works very well as the display of the number.

it just remains for me a problem, when I Forward 7xxx to 1xxx it does not work.

thank you

 

[sbcsu]

Hi
Delete the LDPLN that has all the x-x-x-x-x in it

and make it like this

ADD-LDPLN:LCRPATT,0,6-XXXXXX,,260,,,1,,,,N;

 

[sbcsu]

Now what is not working (what is left to fix) ?

 

[youfo007]

yes it is ok.

called in 7xxx is resolved, thanks to you. changing the dialing CD to TIE.

what is the different between 6-x-x-x-x-x-x and 6-xxxxxx.??

after this solution, I wanted to do everything TIE. How deleted some prefix: it gives me a message:

DEL-WABE:CD,30,,,AFFWDVCE,,;
H500: AMO WABE STARTED
F02: SPECIFY CODE FOR PARTNER DIGIT ANALYSIS RESULT
CD2 = 30
F30: PARAMETERS CD UND CD2 HAVE THE SAME VALUES

AMO-WABE -111 DIALLING PLANS, FEATURE ACCESS CODES
DELETE NOT COMPLETED;

 

[sbcsu]

Hi,
All outbound calling is now TIE,
CO is no longer used. (Even though you are using a CO it is labelled/setup as TIE in WABE)

6-x-x-x-x-x-x and 6-xxxxxx.??


When you dial 6-xxxxxx the system then looks at the LDAT 260.
In LDAT 260 you have an LODR (probably LODR 260)
LODR 260 probably says
ECHO,1; (Dial out 6)
ECHO,2; (Dial out all the xxxxxx after 6)
END;

When you dial 6-x-x-x-x-x-x - again it looks at LDAT 260
In LDAT 260 you have LODR 260
LODR 260 ONLY says to dial 6 then ONE X
after that all the other x-x-x-x are left there and not dialled.

Field 1 is 6 - sent by LODR ECHO 1
Field 2 is x - sent by LODR ECHO 2
Field 3 is x - nothing happens
Field 4 is x etc. - Nothing happens


DEL-WABE:CD,30,,,AFFWDVCE,,;
Some WABE codes are linked.
When you set them up you need to setup the 'opposite code' as well
When you delete the code you need to know and mention the 'opposite code' as well.

Example:
SETUP:

ADD-WABE:**9001,,,AFFWDVCE,N; (The 'N' means no code for rotary/dial pulsing devices as most phones are DTMF now)
ADD-WABE:**9002,,,DFWDVCE,N;

To delete any of the above you have to delete both as follows:
DEL-WABE:CD,**9001,,,AFFWDVCE;
F02: SPECIFY CODE FOR PARTNER DIGIT ANALYSIS RESULT
CD2 =
**9002;

Done !


Have you had the opportunity to go to any training provisions in your area yet as I know you might find them of use ?

Regards

 

[sbcsu]

OK reading back up it looks like LDAT 260 is using LODR 8

If you DIS-LODR
you will see LODR 8
and the steps that it takes to send out the numbers when you dial 8-x or 8-xxxx

The x means any digit or group of digits
If you know how many digits it takes then put in the required amount but no more

 

[sbcsu]

Might I also suggest that you use the latest Comwin
A copy is located HERE

After you install it
Log on to the HiPath

Click on 'Macro' then 'Retrieve System Variant'

After that you could type for example
DEL-WABE:CD

then right mouse click on that and go to MML-Editor

This Comwin Edit/MML Editor will guide you through the AMO's
However you do have to complete the Macro/Retrieve System Variant so as it knows the version...

 

[youfo007]

All I can say is thank you so much.

for training, I had some training but they were not very advanced.

now everything works.

 

[sbcsu]

Hi youfo007
Glad you are sorted out for now.
Hope all goes well.

Are you an on-site tech or do you travel around a bit ?