atcomsystems.ca/forum Forums TDM Business Telephone Systems Inter-Tel Telephones & Systems Destination Unreachable

Hello,

I've been dealing with an issue between 2 Axxess 8.2 boxes that cannot communicate with each other. 4 digit dialing from either side will say 'destination unreachable' and I cannot import/export from session manager. One side has a cisco 2600 router and the other as a 3600 route. Seems to be routing fine. There is no firewall between the two boxes. I also run a CT gateway. Below is a snippet of whats being said on it:

09/01/2010 08:10:23.754 OAI Message Received: 048,SI,,0007,667*706,6:3261,I,22,
09/01/2010 08:10:23.754 OAI Message Received: 049,XC,,0007,667*706,6:3261,6:3261,N,36
09/01/2010 08:10:26.754 OAI Message Received: 050,ES,,0009,667*506,6:3355,,I,6:90001,,,E,6:3355,6:3261,C,35
09/01/2010 08:10:26.754 OAI Message Received: 051,ET,,0009,667*506,6:3355,13
09/01/2010 08:11:59.752 OAI Message Received: 052,XC,,0009,667*506,6:3355,6:3355,N,36
09/01/2010 08:14:41.748 OAI Message Sent: _NO,0
09/01/2010 08:14:41.748 OAI Message Received: 053,CF,_NO,0,0
09/01/2010 08:15:47.747 OAI Message Received: 054,SI,,0009,667*806,6:3355,I,22,
09/01/2010 08:15:47.747 OAI Message Received: 055,OR,,0009,667*806,6:3355,,I,6:92000,3355,C,22
09/01/2010 08:15:47.747 OAI Message Received: 056,CI,,0009,667*806,6:3355,3355
09/01/2010 08:15:50.747 OAI Message Received: 057,XC,,0009,667*806,6:3355,6:3355,N,36
09/01/2010 08:15:50.747 OAI Message Received: 058,SI,,0009,667*906,6:3355,I,22,
09/01/2010 08:15:53.747 OAI Message Received: 059,OR,,0009,667*906,6:3355,,I,1:3146,3355,C,22
09/01/2010 08:15:53.747 OAI Message Received: 060,FA,,0009,667*906,6:3355,3146,C,13
09/01/2010 08:15:53.747 OAI Message Received: 061,XC,,0009,667*906,6:3355,6:3355,N,36
09/01/2010 08:15:56.747 OAI Message Received: 062,SI,,0009,667**06,6:3355,I,22,
09/01/2010 08:15:59.747 OAI Message Received: 063,OR,,0009,667**06,6:3355,,I,1:3146,3355,C,22
09/01/2010 08:15:59.747 OAI Message Received: 064,FA,,0009,667**06,6:3355,3146,C,13
09/01/2010 08:15:59.747 OAI Message Received: 065,XC,,0009,667**06,6:3355,6:3355,N,36
09/01/2010 08:16:11.747 OAI Message Received: 066,SI,,0009,667*#06,6:3355,I,22,
09/01/2010 08:16:11.747 OAI Message Received: 067,OR,,0009,667*#06,6:3355,,I,6:92000,3355,C,22
09/01/2010 08:16:11.747 OAI Message Received: 068,CI,,0009,667*#06,6:3355,3355
09/01/2010 08:16:23.747 OAI Message Received: 069,NT,,0009,667*#06,6:90004,4841031,C,22
09/01/2010 08:16:23.747 OAI Message Received: 070,DE,,0009,667*#06,6:90004,4841031,E,6:3355,,,,,I,4841031,,3355,C,22,
09/01/2010 08:16:38.747 OAI Message Received: 071,ES,,0009,667*#06,6:90004,4841031,E,6:3355,,,I,4841031,,C,35
09/01/2010 08:16:38.747 OAI Message Received: 072,ET,,0009,667*#06,6:3355,0
09/01/2010 08:17:47.949 OAI Message Received: 073,XC,,0009,667*#06,6:3355,6:3355,N,36

It appears to be talking just fine. I recently had a power outage which seemed to have taken out my IPRC (Networking) Card on one side. I removed with session manager, popped the card out and replaced with a new one. Changed the IP address to what it was originally.

Any ideas would be much appreciated.

Pete

Can you ping each IPRC card from either side. One true test would be to telnet into the IPRC card on the "B" side and try to ping the IPRC card on the "A" side and vice versa. If the ping's are successful we know the connectivity is fine and then it is more than likely a setting in the system programming.

Did you change any of the ports on the IPRC in the original setup? Do you have a saved copy of the DB that you can pull up in local mode and compare to a live system?

When you created the new IPRC network card in programming, did you change the IP Connection from the default P6000 to whatever it needs to be?

Hi Stix1,

I used telnet to connect to the CPU on the B side @ 192.168.16.180 and pinged across the WAN to the IPRC (Networking) card @ 192.168.1.160 on the A side.

Ping a host

Host name or IP address: 192.168.1.160
PING server 192.168.1.160
64 bytes from 192.168.1.160: icmp_seq=0, time=4ms
64 bytes from 192.168.1.160: icmp_seq=1, time=4ms
64 bytes from 192.168.1.160: icmp_seq=2, time=3ms
64 bytes from 192.168.1.160: icmp_seq=3, time=5ms
64 bytes from 192.168.1.160: icmp_seq=4, time=4ms
64 bytes from 192.168.1.160: icmp_seq=5, time=4ms
64 bytes from 192.168.1.160: icmp_seq=6, time=4ms
64 bytes from 192.168.1.160: icmp_seq=7, time=4ms
64 bytes from 192.168.1.160: icmp_seq=8, time=6ms
64 bytes from 192.168.1.160: icmp_seq=9, time=4ms
64 bytes from 192.168.1.160: icmp_seq=10, time=5ms
64 bytes from 192.168.1.160: icmp_seq=11, time=8ms
64 bytes from 192.168.1.160: icmp_seq=12, time=6ms
64 bytes from 192.168.1.160: icmp_seq=13, time=6ms
64 bytes from 192.168.1.160: icmp_seq=14, time=3ms
64 bytes from 192.168.1.160: icmp_seq=15, time=4ms
Sent 16 packets, received 16 OK, 0 bad
Press a key to return.

Ping from A to B was perfect. I sent the ping from the CPU which is at 192.168.1.155. In this case the CPU is an actual PC. I'm unsure if there's a way to ping from an IPRC itself. Pinging router to router was perfect as well.

This (ping from B to A) is good since I replaced the card because before I did that, it was receiving only about 50% of the packets out of 16 sent. I really actuall thought this was the root of my problem but unfortunately, it wasn't.

I haven't changed any ports on the original setup but I'd like to compare the saved copy. I didn't realize I could pull up in local mode. Anything special I need to know to pull a local copy for comparison?

Hi DND ON,

When I re-added the new IPRC card, it assigned itself a new interation of the P6000. I believe its P6007. I can't remember if it just assigned it what the number used to be or used a new one. I probably need to look at the DB locally to compare.

In your network configuration, each node is looking for a specific IP Connection. If the connection ID is not correct, they will not communicate.

I normally use P6001 for node 1, P6002 for node 2, etc.

Log into each site and compare the IP Connection assigned to the IPRC against your network configuration. If they’re not the same, you’ll have to change one.

When I consoled to the CPU/PCM-F card on the A side, I get this:

01:632- 10:28 09-01 M2039 INF HW CP Dead Socket Response From node 6, Reason =
+304
-01:633- 10:29 09-01 M2039 INF HW CP Dead Socket Response From node 6, Reason =
+304
-01:634- 10:29 09-01 M2039 INF HW CP Dead Socket Response From node 6, Reason =
+304

DND ON,

Ah yes! I will do this right now and see if those things are off.

Pete

Perfect! Much appreciated! Seems to be working good now. Basically changed the IP Connection ID on the B side that was addressing site A to the new ID assigned to the new card that I had replaced last night. Instantly fixed this issue.
I just knew the power that be would have an answer for this! Thanks again

Pete

Great! When the sites won't communicate, it's normally the IP address or IP Connection.

I've fat-fingered my share of them.