Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Siemens Hipath 4000v4 unable to perform trunk to trunk transfer

Status
Not open for further replies.

JW22

Technical User
Sep 28, 2011
14
ZA
We are unable to transfer (consultation) external calls. We can transfer internal calls. The external call rings at the future stn and when the transferring stn hangs up to transfer the call, the call is cut (not possible shows on the screen).

We have TTT in the COS of our trunk and transferring stn.

COT: 100 INFO: 100-DIUS2/DIUN2 TELKOM EURO ISDN
DEVICE: S2COD SOURCE: DB
PARAMETER:
RECALL IF USER HANGS UP IN CONSULTATION CALL RCL
TRUNK CALL TRANSFER XFER
TRUNK SIGNALING ANSWER ANS
KNOCKING OVERRIDE POSSIBLE KNOR
CALL EXTEND ONLY FOR CALL STATE CEOC
CALL EXTEND FOR BUSY, RING OR CALL STATE CEBC
REGENERATED CO DIALTONE ON OUTGOING SEIZURE COTN
DON'T RELEASE CALL TO BUSY HUNT GROUP BSHT
SEND NO NODE NUMBER TO PARTNER LWNC
INCOMING CIRCUIT FROM SYSTEM WITHOUT LCR NLCR
CALL EXTENSION BY AC TO BUSY STATION WITH CAMP-ON CECO
INCOMING CDR BY ZONE OR FROM LINE ICZL
INCOMING CDR ACTIVATE PER TRUNK ICZO
USE DEFAULT NODE NUMBER OF LINE DFNN
B-CHANNEL NEGOTIATION (PREV. PREFERRED-PREFERRED COLLISION) BCNE
NO NOTIFICATION FOR CONFERENCE SUPPL. SERVICE NOCI
NO OUTGOING CALLTRANSFER INFOS ( REMOTE HOLD/ECT) NOCT
CONVERT ALTERNATE ROUTING ON ERROR TO CFU ARCF
NO TONE NTON

We have installed the latest Hipath 4000 patches.

thank you for your assistance
 
Make sure the COS for your phones and trunks have at least TTT checked as one of the classmarks.
 
hello. thank you - COS for phones and trunks do have TTT checked.
 
I know there is more to it than that - there was just a conversation about this not too long ago and I can't remember which thread it was or I would refer you. TTT is one of them, but there are a couple more on the 4000 that need to be checked.

I looked at my Trunks CO and I have this:

Voice1: CTLS

Voice2: MB

Voice3: TNOTCR, TA, TTT

Data: NOCO, NOTIE

Fax: NOCO, NOTIE

 
DIS-ZAND:ALLDATA;

Check that EXCOCO is set to YES.

DIS-TDCSU for the COS of the trunks and ensure that TTT is enabled for that COS.
 
Hi, thanks - our settings are as you have suggested:

DIS-COSSU:COS,10;
H500: AMO COSSU STARTED
+------+-----------------+---------------+-----------------+
| COS | VOICE | FAX | DTE |
+------+-----------------+---------------+-----------------+
| 10 |>10-NON DISPLAY PHONE |
| | TA | TA | TA |
| | TSUID | TNOTCR | TNOTCR |
| | TNOTCR | BASIC | DSM |
| | CDRATN | | BASIC |
| | CDRSTN | | |
| | CDRC | | |
| | CDRINT | | |
| | COSXCD | | |
| | CFNR | | |
| | VCE | | |
| | RSVLN | | |
| | TTT | | |
| | MTRACE | | |
| | CFB | | |
+------+-----------------+---------------+-----------------+

DIS-ZAND:ALLDATA;
H500: AMO ZAND STARTED
GENERAL SYSTEM DATA:
====================
TRANSFER = EXTEND , ALERTN = YES ,
AUTHUP = TA ,
RNGBKTN = YES , TRANSINH = NO ,
NIGHT = TA ,
ITRFWD = YES , HOLDTN = MUSIC , ANATESIG = TONE ,
DSSLT = 15, CODTN = YES , CONFSUB = NO ,
DATEDIS = DDMM, CNTRYCD = 6 , RCLLT = NO ,
MELODY = 1, TRCD = , CPBLOWL = 80 ,
CPBUPPL = 100, CUTHRU1A = YES , PREDIA = YES ,
SIUANN = 2, CO = NO , COEXN = 0 ,
CBKNO = 5 , SEVDIG = NO , PNNO = 10-11 -76 ,
DISPMODE = MODE1, PNODECD = 808400, ROUTOPTP = YES ,
ROUTOPTD = NO , CALLOFF = YES , PARARING = YES ,
DSSDEST = YES , ONEPARTY = YES , MSGDELAY = NO ,
EXCOCO = YES , TRDGTPR = NO , COANN = YES ,
HOTDIAL = NO , TRANSTOG = YES , NOCFW = NO ,
HOLDHUNT = NO , POSTDDLY = YES , EXBUSYOV = YES ,
OVRMST = NO , OVRHUNT = NO , CONITPRO = YES ,
RECHUNT = NO , CALLACMP = NO ;
 
I take it that COS 10 is the COS being used by trunks then as displayed in AMO-TDCSU. Is that correct?

Could you DIS-KNMAT; and DIS-TDCSU;
 
That COS has "non display phone" for it's description. Have you looked to see if there are any other ones that have "trunks" for their description? My vendor titled them all specifically for what they were used for.

Do your DIS-COSSU with no number after COS and look at them all. If there is one that says Trunks explore that further.
 
hi - so yes, cos 10 is used by the TDCSU for our CO trunks. We are using cos 120 (fwdexternal) for our stations. Both have TTT in them. We don't have any Cossu's labelled specifically for trunk.

DIS-TDCSU:1-1-25-0;
H500: AMO TDCSU STARTED
+------------------------ DIGITAL TRUNK (FORMAT=L) -------------------------+
| DEV = S2COD PEN = 1-01-025-0 TGRP = 1 |
|---------------------------------------------------------------------------|
| PROTVAR = ETSI INS = Y SRCHMODE = CIR |
| COTNO = 100 COPNO = 100 DPLN = 0 |
| ITR = 0 COS = 10 LCOSV = 1 |
| LCOSD = 1 CCT = TELKOM ISDN DESTNO = 99 |
| SEGMENT = 1 DEDSCC = DEDSVC = NONE |
| FACILITY = DITIDX = SRTIDX = |
| TRTBL = GDTR SIDANI = N ATNTYP = CO |
| CBMATTR = NONE NWMUXTIM = 10 TCHARG = N |
| SUPPRESS = 0 DGTPR = CHIMAP = N |
| ISDNIP = ISDNNP = |
| PNPL2P = PNPL1P = PNPAC = |
| TRACOUNT = 31 SATCOUNT = MANY NNO = 99 |
| ALARMNO = 2 FIDX = 1 CARRIER = 1 |
| ZONE = EMPTY COTX = 100 FWDX = 10 |
| DOMTYPE = DOMAINNO = TPROFNO = |
| INIGHT = CCHDL = |
| UUSCCX = 16 UUSCCY = 8 FNIDX = 1 |
| CLASSMRK = EC & G711 & G729AOPT SRCGRP = |
| TCCID = SECLEVEL = TRADITIO |
|---------------------------------------------------------------------------|
| BCNEG = Y BCGR = 1 LWPAR = 1 |
| LWPP = 0 LWLT = 0 LWPS = 0 |
| LWR1 = 0 LWR2 = 0 |
| DMCALLWD = DMCSEC = VNNO = |
| SVCDOM = |
| BCHAN = 1 && 30 |
| |
+---------------------------------------------------------------------------+



<DISPLAY-KNMAT:;
DISPLAY-KNMAT:;
H500: AMO KNMAT STARTED
H01: NO ENTRY WITH THE REQUIRED ATTRIBUTES AVAILABLE

AMO-KNMAT-111 NODE DATA FOR NETWORKING
DISPLAY COMPLETED;
<REGENERATE-KNMAT:;
REGENERATE-KNMAT:;
H500: AMO KNMAT STARTED

AMO-KNMAT-111 NODE DATA FOR NETWORKING
REGENERATE COMPLETED;

thanks.
 
The configuration looks OK.

This may be a stupid question but when you are trying the trunk to trunk transfer you are prefixing the required number with the trunk access code.

The other thing, could you change the DESTNO in TDCSU from 99 to 0 and then try the trunk to trunk transfer.
 
hi, thank you for all the suggestions.

We do dial with the trunk access code - no success

Tried changing the DESTNO in TDCSU but it still doesn't work.

We are able to transfer the call, but when the transferring party hangs up the call comes back to them - almost as if it is being rejected by the end party or that the transferring party can't drop the call.

thanks again.
 
I've just being looking at the COT 100,could you de-activate the parameter NOCT and then try it.
 
hi - just done it and still not working. Please keep the ideas coming. tx
 
Might be a disconnect supervision thing in the COP/COT stuff?

If you are actually trying to transfer the calls to an external number (transfer, dial 9-Nxx-xxxx, wait for answer, disconnect) wit about the LCRCOSV ??

Just brainstorming here...
 
You will have to get the node numbering correct, in the TDCSU, ZAND and RICHT and LDAT.
If the node numbering is not correct it will be looking up its own *~%$ and wont allow you to transfer trunk to trunk.

 
Post a Regen of the system or just
TDCSU
RICHT
LDAT
KNMAT
KNFOR
KNDEF
ZAND alldata
 
I have no config suggestions since I do not work with Euro-trunks or B-channel negotiation. However, just to clarify: in the title of your post, it mentions trunk-to-trunk transfer. But in your first post, you do not mention trunk-to-trunk, but rather you state "future station" and "transferring station". You are truly attempting to transfer a call from one trunk to another trunk, correct?

You showed the config for the incoming CO trunks. Are you attempting to transfer the call out on the same trunk circuit?
If so, could the Central Office be blocking your attempt to connect two B-channels together?
If not, please show the "other" trunk config. Cornet, perhaps?

Can you perform a CONFERENCE with the same stations and trunks?

Are you attempting an ANNOUNCED transfer - where the first call is placed on soft hold while the transferring party speaks with the new party, then hangs up and the two outside parties are JOINED. During the "announcement", such as "Hello - I am transferring a call to you from Mr Smith", the two external trunks are not yet connected.

Or is this a BLIND transfer, where the transferring party simply dials the external number and hangs up? Here the two external parties are immediately connected when the transferring party hangs up.

Try both methods. Do both methods fail?

You mentioned the term "CONSULTATION" in the first sentence. Are you SURE that the correct methodology is being used by the user? Is the transferring party using "TRANSFER" or "CONSULTATION"?

Display FEASU. This may be a system feature issue. Good luck!!
 
Hello. We have a solution!!

We have decided to set up ONS (one number service). This works perfectly allowing us to transfer external calls to a trunk.

We know this isn't the true solution, but it works for us. If you know why the HiPath can transfer trunk to trunk via ONS, but not normally, please tell us.

One other thing we forgot to mention (in the initial request above) is that we are able to transfer an internal call to a trunk, but not trunk to trunk. We transfer blindly.

Thank you again for all the suggestions above, we worked through them all, but still couldn't get it to work.
 
Struggling with this one but I've attached the COT parameters of a system where this works.

COT: 4 INFO: 4:Q931 EXTERNAL
DEVICE: INDEP SOURCE: DB
PARAMETER:
PRIORITY FOR AC WILL BE DETERMINED FROM MESSAGE PRI
RECALL IF USER HANGS UP IN CONSULTATION CALL RCL
TRUNK CALL TRANSFER XFER
TRUNK SIGNALING ANSWER ANS
CHANGEOVER FROM HOLD TO RING TONE CHRT
KNOCKING OVERRIDE POSSIBLE KNOR
CALL EXTEND FOR BUSY, RING OR CALL STATE CEBC
NETWORKWIDE AUTOMATIC CALLBACK ON BUSY CBBN
DON'T RELEASE CALL TO BUSY HUNT GROUP BSHT
DESTINATION NUMBER WITH PREFIX DIGITS TO CDR DPRE
SEND NO NODE NUMBER TO PARTNER LWNC
CONNECTION TO ROUTE OPTIMIZATION NODE ROPT
INCOMING CIRCUIT FROM SYSTEM WITHOUT LCR NLCR
TSC-SIGNALING FOR NETWORKWIDE FEATURES (MANDATORY) TSCS
INCOMING CDR BY ZONE OR FROM LINE ICZL
INCOMING CIRCUIT FROM SYSTEM WITHOUT LCR (DATA) NLRD
AOC PER CALL (AUTOMATICAL OR ON REQUEST), MAND. CORNET-NQ AOCC
CDR FOR BREAK OUT TO CARRIER CDBO
CONTROLLED TRUNK AND LINE SELECTION CTLS
RESERVED ELEMENT NOCI
RESERVED ELEMENT NOCT
NO TONE NTON

I had an issue a while back whereby users were unable to pickup external calls using their pickup button and this was resolved by adding DSDL to the COT. This was unique to one site only so it may be worth trying the COT with that in.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top