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!

Inbound Calls Failing NEC 2000 IPS

Status
Not open for further replies.

parkland

MIS
Dec 4, 2009
27
0
0
US
Have a new carrier coming in. Using their PRI as back up to other two PRI from different carriers. REplacing third PRI with new carrier. Have 3 PRI cards in system. Putting new carrier on third PRI card. Outbound calls work but inbound calls do not. Below is infomation from carrier. Have had technician look and DNIS is setup correctly. Third PRI is setup for outbound and inbound calls.

This call has been fail to fast busy:

Bearer Capability i = 0x8090A2
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98381
Exclusive, Channel 1
Facility i = 0x9F8B0100A1180201330201008010545820576972656C6573732043616C6C
Protocol Profile = Networking Extensions
0xA1180201330201008010545820576972656C6573732043616C6C
Component = Invoke component
Invoke Id = 51
Operation = CallingName
Name presentation allowed
Name = TX Wireless Call
Display i = 'TX Wireless Call'
Calling Party Number i = 0x2180, '2102045758'
Plan:ISDN, Type:National
Called Party Number i = 0x80, '2085'
Plan:Unknown, Type:Unknown
*Jun 13 19:43:11.732: ISDN Se0/0/0:23 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x80B1 --------------
Cause i = 0x819F - Normal, unspecified

That call has been complete:

Bearer Capability i = 0x8090A2
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98381
Exclusive, Channel 1
Facility i = 0x9F8B0100A10B02013402010080034E4253
Protocol Profile = Networking Extensions
0xA10B02013402010080034E4253
Component = Invoke component
Invoke Id = 52
Operation = CallingName
Name presentation allowed
Name = NBS
Display i = 'NBS'
Calling Party Number i = 0x2180, '9736382100'
Plan:ISDN, Type:National
Called Party Number i = 0x80, '2085'
Plan:Unknown, Type:Unknown
*Jun 13 19:44:05.020: ISDN Se0/0/0:23 Q931: RX <- CALL_PROC pd = 8 callref = 0x80B2 ------------
Channel ID i = 0xA98381
Exclusive, Channel 1

I put red arrow for two different messages from customer’s PBX
 
How many digits in CMD 3512 for that route are you set for and how many digits is telco sending?
 
Compare the program settings between your 3 PRI's. If they are the same, then, swap the smart jack with one of the working circuits? See if the problem moves or stays.
 
Carrier is sending 4 digits. Confirmed they are sending 2085. PBX is set to receive 4 digits. Currently receive 4 digits from current carrier. This PRI is replacing a working PRI. I tried all 3 PRI cards with same results from new carrier. Outbound works inbound does not. No fault messages for errors. New carrier sees D Channel up. I can make outbound without issues.
I have read on some posts where cards needed to be updated. These cards are original with the system and about 4 or 5 years old.
Is there a way to monitor the d channel like Nortel systems?
 
Ok, so I was able to get the new PRI to work both inbound and outbound. I confirmed New carrier is set to NI2 but I changed my card setting to Northern Telecom and inbound and outbound calls are now working. Not sure why but everything is working now and that is all that matters.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top