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 gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

The caller ID issue on Hipath 4000 V4

Status
Not open for further replies.

GaryPing

Technical User
Sep 10, 2015
6
TW
Hello Sir, Madam,
We have one Hipath4000 V4 system and that have 2 E1 PRI connections, one is connect to telco and other one is connect to 3rd party PBX.
We are facing the caller ID issue
Example: A is outside user (002387567), B is Hipath4000 user (4000), C is 3rd PBX user (3000)
Incoming call from A to B, the user 4000 can see the caller ID is well as 002387567
Then the B transfer the call to C, the user 3000 can see the caller ID is 4000 only,
So how to define for the user 3000 that can see the caller ID is also outside user A?

Thanks so much

Gary
 
Hi,
What protocol is the trunk using between 4K & 3K

DIS-TDCSU:
 
Hi Sir,

Thanks your prompt reply on this

The HP4000 is using ETSI protocol to the 3rd party PBX, the 3rd PBX is other brand product.

Best regards.
Gary

 
Just to clarify.

ISDN -> HiPath 4000 -> HiPath 3000 ?

Is it a HiPath 3000 at the end or 'other brand product'

If it is a HiPath 3000 then you will get full transparency of incoming and outgoing calls both internal and external.
However if it is an 'other brand product' then you will only get the incoming number.

If it is a 3000 at the end then change to protocol to CORNV33 or ECMAV2 depending on the age of the 3000 with SEGMENT=1

Also COP/COT settings on the 4K as follows:

ADD-COP:110,RLSB&RLSA&NOAN&RMSG&RRST,TA,TA;
CHANGE-COP:110,COPADD,,,,INDEP,"2MB LINK TO HIPATH3750";
ADD-COT:110,RCL&ANS&USD&KNOR&CEBC&TIE&CBBN&CBFN&FNAN&COTN&IEVT&ITRN&BSHT&DPRE&LWNC&SATC&NLCR&APPR&TSCS&ICZL&ICZO&UUS1&UUS2&UUS3&US1E&NLRD&SNBE&CTLS&NTON;
CHANGE-COT:110,COTADD,,INDEP,"2MB LINK TO HIPATH3750";
 
Thanks Sir,

The 3rd PBX is other brand product, so that whether possible to get the external caller ID if we change the protocol by ECMA1?

Thanks with best regards.
Gary
 
Can you try ECMAV2 if not supported by the other PBX then try ECMAV1
Then if they fail you have to revert to ETSI
A good 2MB tester is handy in these situations if you can borrow one.

It also can happen that the other system might have different names for these protocols so just try ECMAV2/ECMAV1

ETSI is normally used for links to PTT/Carrier/Circuit Providers

ECMAV2 works with Xpressions, Dialogic and others.

The HiPath can provide reference clock to the other system if required. (AMO REFTA)
If the speech path is currently working then your LWPAR is probably correct.

Deactivate the Circuit first
DEA-DSSU:L,PEN,1-2-3-4;

Change the Protocol
CHA-TDCSU:pEN=1-2-3-4,PROTVAR=ECMAV2;

Activate the circuit
ACT-DSSU:AUL,BCHAN,1-2-3-4;
RES-DSSU:pEN,1-2-3-4;

Display status
DIS-SDSU:ALL,,PEN,PER3,1,2,3,4;
 
Hi sir,

Thanks so much for your kindly support on this, I will try that.

Thanks with best regards.
 
The 3rd party brand name is "TeleSynergy" which is software base IPPBX.
 
Sounds like an Asterisk type of system.
Here is some info on Asterisk which may be useful Link
 
You are welcome!
Let us know how you get on with it
Regards
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top