Direct IP Route in Cluster error

[kwahodi]

Hi,

We have a cluster set up with 6 controllers running MCD 5.0 PR2. Direct IP route has been set up for calls between the offices. We are experiencing an issue where the Sydney PBX can call extensions in the Melbourne PBX no worries. But the Melbourne users are unable to call the Sydney extensions. When a user in Melbourne dials a Sydney extension (4 digits), they get an INVALID error after the 4th digit is dialled. Both controllers can ping each other with no issues. Below are my SHOW XNET ALL and RMESS Verify results:

-------------------------------------------------------------------------------
 1 1 11 254   |156   |    1 |          |Established   |         |      |       
 1 1 11 253   |159   |    2 |          |Established   |         |      |       
 1 1 11   1   |161   |    3 |          |Established   |         |      |       
 1 1 11 250   |146   |    3 |          |Established   |         |      |       
 1 1 11 252   |160   |    4 |          |Established   |         |      |       
 1 1 11 251   |157   |    5 |          |Established   |         |      |       
-------------------------------------------------------------------------------

RMESSAGE: Connected to PBX  2                                                   
RMESSAGE: Verification successful to PBX  2                                     
RMESSAGE: Disconnected to PBX  2

Point to note that this controller can call all the other sites with no issues. Any idea what else I need to check?

Cheers!
Steve.

[sarond]

Have you got your entry in ARS for Melbourne to dial the Sydney CEID?

[kwahodi]

Yep,

So in ARS digits dialled, I have 7772 (Sydney CEID) with 4 digits to follow using route 12. Route 12 in ARS routes is Direct IP Route. Not sure what else I could try.

Cheers!
Steve

[sarond]

Check that the IP Address is correct for Sydney in the ICP/PBX Networking form.

[kwahodi]

Hi,

Confirmed IP address for Sydney is correct in the ICP/PBX Networking form. Any troubleshooting steps I could try?

Cheers!
Steve

[ralph]

I've had this happen to me before.
It was one of the strangest problems I've had to deal with.
The direct IP route would fail.
Checking all the programming proved to be all right.
A data save / restore did not resolve.
I finally routed the calls through a third PBX.
Then I discovered that if I routed the call via XNET it worked fine.
It ran that way for quite some time and then the XNET route failed.
Then I found that routing it over a direct IP route worked.
Baffling.

The final solution was to set up a route list.
1) direct IP
2) XNET
3) third PBX.

Ralph

[ralph]

Oh...and...
I've also seen it happen when someone put a wrong subnet mask in the system.

Ralph

[kwahodi]

Ok, I've just noticed this - my SHOW XNET ALL results are coming up with 2 established connections to pbx 3 (itself). Is this normal? To route via XNET, do I have to set up IP/XNET trunk profiles? Also, checked the subnet mask and all looks good.

Cheers!
Steve

[kwahodi]

How would you route via a third PBX? I don't think I have ever attempted that.

[ralph]

You just add the third PBX to a route list and then change your ARS to point to the list.

Ralph

[VinceWhirlwind]

on the MEL controller, do a "LOCATE EXT " on the SYD extension.
Does it recognise it as a "Remote Directory number"?
On the Remote Directory Numbers form, look for the SYD extension - check the CEID.
On the Cluster Elements form, check against this CEID and see which CEID digits this has
On the ARS Digits Dialed form, find the CEID digits and check which route this points to
On the ARS Routes form, find the route and check the Digits Mod is correct/the same as for all other similar routes
On your ICP/PBX form, check your CEID for SYD, on the IP Network tab what IP address is there.
On Maintenance Commands, ping the IP address in that last form
 
Check MEL & SYD for SDS errors.

[kwahodi]

Right, this is what I have found out:
- When I do a "LOCATE EXT" from the MEL controller of a Sydney extension, (e.g. Ext 2206) I get this "LOCATE: Invalid or nonexistent extension number or id number." In the Remote Directory numbers form in MEL controller, this extension 2206 is not there. However, there are some Sydney extension numbers in this form e.g. Ext 2214. When I do LOCATE EXT from the MEL controller to ext 2214, "I get The number refers to a remote directory number.Remote DN to CEID 2, routing digits 7772" - which I believe is the expected result. My problems seems to be that not all the Sydney extension numbers are showing up in the RDN form of the MEL controller. On the SYD Controller RDN form, all the MEL extension numbers are there.
- No SDS errors on both controllers.
- ARS checks out OK
- I can ping the ip address in the ICP/PBX form no worries.

It would seem to me that the RDN form on MEL controller has not updated. Any other suggestions?

Cheers!
Steve

[VinceWhirlwind]

I guess I would try switching off data sharing from SYD  and then reenable it, see what happens.
 
I'd be nervous the DB is corrupt somehow. Definitely take an uptodate backup from all controllers before any more fiddling.