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!

Cannot get Caller ID number over IP trunk

Status
Not open for further replies.

chipig

Technical User
Nov 8, 2007
205
CA
I cannot get caller ID number to show on our main PBX.All I get is DDD.

We have the following setup:

PBX(Asterisk) ---(ISDN route 17)---> IPS 2000 #1 ----8IPLA(route 20)-----> IPS 2000 #2

IPS 2000 #1 can receive both calling name and extension number. IPS 2000 #2 only receive calling name but shows DDD as caller's number.

I have checked many commands related to Caller ID but now I'm really running out of ideas....

If PBX #2 can get calling name correctly, it should also be able to show the 4 digits number as PBX # 1 does.







 
Can you post the commands that you have adjusted?

You may be missing an LCR setting that allows CID pass through.
Or, the trunk route command related to CID pass through.
CMD 35145>tk rt>0
CMD 8A5xxx>165>0
 
Both route have the right setting:

IPS 2000 #1:
35145>20:0-
35145>17:0-

IPS 2000 #2
8A5015>165:0-
8A5020>165:0-

Could it be something else?
 
No luck so far,

Here are my results:

PBX 1:

08>379>0
35281>17:0-
35281>20:0-
35282>17:0-
35282>20:0-

PBX 2:

08>379>0
35281>20
CODE NOT USED

Revision of PBX 2 is older by the way.




 
By the way if I check the voice trunk of extension in PBX 2 here what I get:

E8>2300:D051-

I don't get it.... Because route 20 of the 8IPLA card use these trunk:

0701>0400:D100-
0701>0401:D101-
0701>0402:D102-
0701>0403:D103-
0701>0404:D104-
0701>0405:D105-
0701>0406:D106-
0701>0407:D107-
0701>0408:D108-
0701>0409:D109-
 
The 8IPL-A card is the PAD card. Those trunks are assigned as DDxxx. Any trunks assigned with Dxxx is an analog or digital trunk.
 
Those Digital trunks are assigned to a card somehow...
How can I make sure it is assigned to the right card?
PBX 1 is connnected to PBX 2 by IP only with no other link.

 
The IPPAD card uses physical LEN's. The PAD trunks assign in a similar fashion to any station. Whatever slot it is in is the LEN location. The biggest difference is if you have the 24 port daughter board installed on it. Then you need 4 card slots of LEN's to assign them.
EX: card is located in slot 00 = LEN 00000 - 00007.
The first PAD trunk would be DD000 - DD007.
 
You are right here are my lens:
I still don't know why I only get the calling name.
It's looks like PBX 1 do not pass the CID number.



PBX 2
14>00000:DD000-
14>00001:DD001-
14>00002:DD002-
14>00003:DD003-
14>00004:DD004-
14>00005:DD005-
14>00006:DD006-
14>00007:DD007-
14>00008:DD008-
14>00009:DD009-
14>00010:DD010-
14>00011:DD011-
14>00012:DD012-
14>00013:DD013-
14>00014:DD014-
14>00015:DD015-
14>00016:DD016-
14>00017:DD017-
14>00018:DD018-
14>00019:DD019-
14>00020:DD020-
14>00021:DD021-
14>00022:DD022-
14>00023:DD023-
14>00024:DD024-
14>00025:DD025-
14>00026:DD026-
14>00027:DD027-
14>00028:DD028-
14>00029:DD029-
14>00030:DD030-
14>00031:DD031-

PBX 1
14>00033:DD001-
14>00034:DD002-
14>00035:DD003-
14>00036:DD004-
14>00037:DD005-
14>00038:DD006-
14>00039:DD007-
14>00040:DD008-
14>00041:DD009-
14>00042:DD010-
14>00043:DD011-
14>00044:DD012-
14>00045:DD013-
14>00046:DD014-
14>00047:DD015-
14>00048:DD016-
14>00049:DD017-
14>00050:DD018-
14>00051:DD019-
14>00052:DD020-
14>00053:DD021-
14>00054:DD022-
14>00055:DD023-
14>00056:DD024-
14>00057:DD025-
14>00058:DD026-
14>00059:DD027-
14>00060:DD028-
14>00061:DD029-
14>00062:DD030-
14>00063:DD031-

 
Check CMD 15136 Calling Number/Calling Name Display for ISDN/T1-ANI/
MFC-R2 incoming call
00-15
0/1
Calling Number Display
Calling Name Display

CMD 35156 Calling Name Display for incoming call from ISDN/ T1-ANI/MFC-R2 route
0 = 1000-Slot Memory Block No. 3
1 = 1000-Slot Memory Block No. 2, 3
3 = Not provided
[Series 3700 R12.2]




 
Sorry, still not working. I keep looking I guess...
It has something to do with route 20 but I don't know what.



 
You might consider creating a new route and moving everything over. Sometimes starting with a clean slate is easier than trying to find the issue on an existing route.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top