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

Problem with Media Processor TN2302

Status
Not open for further replies.

PiateK

Technical User
Aug 9, 2002
2
PL
Hello :)

I have g3v11 with ip trunk licence and I try to configure TN2302 to VOIP trunk. But I have a bright red led on board and this card can't "wake up".

In "test board xxxxx" i have errors on IPMEDPRO tests:

# 1379 result fail error code 2805
# 1383 result fail error code -
# 1505 result abort error code 2806

#52
#1371
#1406 are pass

Ip node name, ip interface have been adminidtered.

C-lan was configured ok and (also I can administrate by lan).

Adam

 
1379 - 2805 FAIL The number of pings received did not match the number sent(normally one ping sent). This means that no ping responses were received from the gateway defined on the ip-interfaces form for the Media Processor.

1. Retry the command at 1-minute intervals a maximum of 3 times.


1383 - None ABORT System resources required for this test are not available.
1. Retry the command at 1-minute intervals a maximum of 5 times.


1505 - could not find any reference to this test number.



By the results I did find references for, it looks as if your MedPro is not plugged into your LAN. Check the LAN cable between the MedPro and your network drop. If all this is good and the red light does not go out on the card, the MedPro is probably defective.

 
Is it normal that Minor alarms are raised against the IPMEDPRO and (8)MEDPROPT's right after installing the board but before defining any Ip node name or ip interface?
 
Assuming it is normal, I went ahead and defined node name and interface info and alarms went away. However ping
ping ip-address nnn.nnn.nnn.nnn board UUCSS fails with code 2805 using the assigned IP address of the MedPro and its slot info. Off to the reference books......
Anybody reading this that has any comments/suggestions, please jump in.
 
Hmmm,
Testing the board reveals that it passes test 52 (Control Channel Looparound) and 1371 (IP Address Query), fails 1383 (cannot find this test) and 1379 (Ping test), and passes 1406 (board diagnostics). Does anybody know what test 1383 is?
If I ping the address assigned to the CLAN from the CLAN board location I get a PASS

If I ping the address assigned to Intuity Audix from the CLAN board location I get a PASS

If I ping the address assigned to the TN2302 from the CLAN board location I get a FAIL

If I ping the address assigned to the TN2302 from the TN2302 board location I get a FAIL

This last one gets me.....Shouldn't I be able to ping within the system like I'm trying above, even if I were having cabling problems. Isn't it like pinging the IP address of your computer--from your computer?
Does it matter that our network admin gave me an IP address for the MedPro that is subnetted differently (255.255.255.192) than the IP address he gave me some time ago to use for the C-Lan board (255.255.255.224? The addresses are from the same class C (ex. 213.54.127.51 and 213.54.127.88 respectivly)(BTW, these are NOT the actual IP addresses). Anybody have any insight as to what to try next? I'm running out of ideas.


Does it matter that the CLAN is in carrier A and the Medpro board is in carrier B?
 
Try this with your IP Med Proc board..

A. busy board NNNN
B. status board NNNN to determine traffic level
C. disable board in ip-interfaces form (i.e., change "y" to "n" in left-most column of the ip-interfaces form)
D. reset board NNNN
E. enable board in ip-interfaces form (i.e., change "n" to "y" in left-most column of the ip-interfaces form)
F. release board NNNN

mmcalli, you will get alarms on that board after physically installing it. you must fully administer it before those alarms will go away.
 
Thanks PBXTech,
I followed your steps (except there is no "Status board" command (in V9.5 anyway). And I still get errors and ping from outside to the board fails as does pinging the address assigned to the TN2302 from the TN2302 board location (ping ip-address 127.0.0.0 board 01b01). If I try ping ip-address 127.0.0.0 board 01a03 (The C-lan card) it passes. To me this should be just like pinging your local host address [127.0.0.0] on a PC which indicates to me that the problem is not in any cabling issue as I'm pinging internal to the PBX and not relying on any cabling.
Does that sound like a valid assumption to you?
 
I thought it was 127.0.0.1, not the last octet .0? What are the patch cables going to from out of the RJ45 connectors? Check the data switch/router ports and look for a link light on that. Do you have a link light on the front of the TN2302?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top