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

CANNOT SEE THE NUMBER OF THA PERSON THAT IS CALLING

Status
Not open for further replies.

Supportvzla

Technical User
Oct 9, 2002
137
0
0
VE
I have 2 PBXs Option 11C. the first one has a DID (R2MF) conection with the public switch. I activated the CNA in the Did trunks so I can see the phone number of the person that is calling.
I have a tie ISDN conection between the 2 PBXs.
In the second switch, users cannot see the number of the person that is calling from the public switch even thou they can see the name and the number when an extension in switch A calls an extension in switch B.

Am I missing something?

supportvzla
 
Do you have ND2 in the RCAP field of the D-Channel?

 
yes.
If I call from extension1 (in switch A) to extension2 (in switch B) I see all the information (Dn, Name)in extension2
If I forward extension1 to extension2 I get the number of the person that is calling from the public switch (OK)
If I program an ACD Qeue (in switch A)with NCFW to extension2 I also get the public switch number (Ok).
But normal calls from the public switch (tandem switch A)dont show the number in extension2

supportvzla
 
did you try to enable DCH MON on PRI connection between A and B in LD96 to see if it is a CLID information in setup msg. from switch A?
 
I did but I dont know how to translate that information to english

supportvzla
 
can you show us an example of this DCH mon
 
Try this command
LD 96
.SET MSGO x MON 0
.SET MSGI x MON 0
(x is your d-channel number)
This sets the message output level to provide some english translation.
Then I would like to try:
.ENL MSGO X FEAT CPNW
I've never seen the output for this so if you want to post it that would be great. Seems like this is targeted to your need.
Otherwise the standard command may provide enough information:
.ENL MSGO x
Of course you would want to focus on the outgoing messages for the originating PBX and the incoming messages for the PBX with the phone/display that should be working.
 
DCH 15 IMSG SETUP REF 00008019 CH 1 25 TOD 20:32:08
FEAT :NAS
PROGRESS: ORIG ADDR IS NOT ISDN
CALLED #:1003199 NUM PLAN: PRIVATE
DCH 15 OMSG STP ACK REF 00008019 CH 1 25 TOD 20:32:08
DCH 15 OMSG ALERT REF 00008019 CH 1 25 TOD 20:32:08
FEAT :NAS
DCH 15 OMSG CONNECT REF 00008019 CH 1 25 TOD 20:32:12DCH 15 IMSG CONN ACK REF 00008019 CH 1 25 TOD 20:32:12
DCH 15 OMSG DISC REF 00008019 CH 1 25 TOD 20:32:12
CAUSE :NORMAL CALL CLEARING
DCH 15 IMSG RELEASE REF 00008019 CH 1 25 TOD 20:32:12

If I forward an ext1 in pbx 1 to ext2 in pbx 2 I get:

DCH 15 IMSG SETUP REF 00008019 CH 1 25 TOD 20:32:38
FEAT :NAS
PROGRESS: ORIG ADDR IS NOT ISDN
CALLING #:2129553113 NUM PLAN: NUM UNKNOWN
CALLED #:1003199 NUM PLAN: PRIVATE
DCH 15 OMSG STP ACK REF 00008019 CH 1 25 TOD 20:32:38
DCH 15 OMSG ALERT REF 00008019 CH 1 25 TOD 20:32:38
FEAT :NAS
DCH 15 OMSG NOTIFY REF 00008019 CH 1 25 TOD 20:32:38
REDIR REASON:CALL FORWARD UNCONDITION
REDN #:3199 NUM PLAN: PRIVATE
DCH 15 OMSG CONNECT REF 00008019 CH 1 25 TOD 20:32:40
DCH 15 IMSG CONN ACK REF 00008019 CH 1 25 TOD 20:32:40
DCH 15 OMSG DISC REF 00008019 CH 1 25 TOD 20:32:42
CAUSE :NORMAL CALL CLEARING
DCH 15 IMSG RELEASE REF 00008019 CH 1 25 TOD 20:32:42
DCH 15 OMSG REL COMP REF 00008019 CH 1 25 TOD 20:32:42


 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top