HiPath 4000 unable to transfer external calls to SIP router

[JW22]

We have a HiPath 4000v3 networked to a SIP router (closed networking). We are unable to transfer (consultation) external calls. We can transfer internal calls. We can transfer external calls from the SIP router to the HiPath, but not from the HiPath to the SIP router. 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 created stns in wabe and netrte codes. We have entered a remote DNNO in wabe. All node numbers in richt and ldat are the same level (0-0-10). We have played with settings in COT.

thank you for your assistance

 

[donb01]

What about supervision timers, or other functions that typically supervise the call handoff. Something might be seeing the transfer release from the transferring station as a call release?

Just throwing that out there for brainstorming....

 

[Iamnothere]

Sounds like it could be a Trunk-to-Trunk issue. In the 4K trunk config, TDCSU, look at the "COS" parameter, then query AMO COSSU --> COS and see if the classmark "TTT" is present in the Voice column. If not, add it.

Perform this same action for the COS of the calling party phone on the 4K, so that the caller has permission to setup a Trunk-to-Trunk call.

Also in TDCSU, ensure that the value for parameter "FWDX" is set to 5 or higher.

 

[JW22]

Thank you. Confirmed that TTT is in cos we are using. Increased FWDX from 1 to 6. Still not able to join initial DID call and IP phone via Siemens phone. Transferring stn shows "waiting" when IP phone answers. Here are our COT values (100 for CO trunks and 115 for SIP trunk). tx again.

Still looking at timers to find right one involved in releasing a call. tx

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 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
NETWORK CALL TRANSFER, EXPLICIT CALL TRANSFER NCT
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

AMO-COT -111 CLASS OF TRUNK FOR CALL PROCESSING
DISPLAY COMPLETED;
<dis-cot:115;
DIS-COT:115;
H500: AMO COT STARTED

COT: 115 INFO: 5-DIUS2/DIUN2 NETWORKING QSIG
DEVICE: S2CONN SOURCE: DB
PARAMETER:
TRUNK CALL TRANSFER XFER
TRUNK SIGNALING ANSWER ANS
KNOCKING OVERRIDE POSSIBLE KNOR
CALL EXTEND FOR BUSY, RING OR CALL STATE CEBC
NETWORKWIDE AUTOMATIC CALLBACK ON BUSY CBBN
NETWORKWIDE AUTOMATIC CALLBACK ON FREE CBFN
NETWORKWIDE CALL FORWARDING PERMITTED FWDN
NETWORKWIDE FORWARDING NO-ANSWER FNAN
TRANSFER OF USER ITR GROUPS VIA S0/S2 (NWU) ITRN
DON'T RELEASE CALL TO BUSY HUNT GROUP BSHT
END-OF-DIAL FOR BLOCK IS SET BLOC
CALL EXTENSION BY AC TO BUSY STATION WITH CAMP-ON CECO
TSC-SIGNALING FOR NETWORKWIDE FEATURES (MANDATORY) TSCS
INCOMING CDR BY ZONE OR FROM LINE ICZL
INCOMING CDR ACTIVATE PER TRUNK ICZO
USE DEFAULT NODE NUMBER OF LINE DFNN
NETWORK CALL TRANSFER, EXPLICIT CALL TRANSFER NCT
VOICE MAIL VM

 

[Iamnothere]

I am not familiar with your term "SIP Router". What type of trunk is the connection between the 4K and the SIP Router? Is this a SIP trunk? Is it ISDN? A SIP Router is obviously SIP on one side, but the other side could be practically anything. Please explain what connects to the SIP Router from the 4K.

 

[JW22]

We have a Quintum router connected on the other side of the 4K. We have connected it as S2CONN with Protvar=Ecma1 (QSig). OK?

 

[sbcsu]

It is possibly the node numbering.
But to find out what is wrong do a trace using the diagnostics folder in the assistant.
Trace the S2CONN trunk going to the Quintom.
It is possible that the Quintom is rejecting the call in which case you should contact the sip supplier.

 

[sbcsu]

Oh and make sure you add the following to your COT

RECALL IF USER HANGS UP IN CONSULTATION CALL RCL
TRUNK CALL TRANSFER XFER
TRUNK SIGNALING ANSWER ANS
CHANGEOVER FROM HOLD TO RING TONE CHRT
CALL EXTEND FOR BUSY, RING OR CALL STATE CEBC
TIE LINES TIE