Problem Calling a Certain Directory Number ?

[Nameless-IT]

We have 2 sites. Site 1 , Site 2

The problem is happening with a specific DN (Ex: 5058)

5058 is located in Site 2

When calling 5058 from any location in site 2 , no problem

When 5058 calls any DN in site 1 , no problem.

When calling 5058 from site 1 , busy signal.

knowing that all other numbers are working fine between sites.

[Mike_Brezicky · Accepted solution]

Some things you can check:
Check the CSS / Partition setup.
Are the sites / phones all in the same cluster?
Enter the call into the Dialed Number Analyzer to see what it expects to happen.
Pull trace file from RTMT and check the SDI logs for the SIP (or SCCP)trace.

Finally, if it still looks 100% - try a hard delete and recreate the number.

[Nameless-IT]

Problem Solved.

I managed to track down the problem using DNA (Awesome tool for troubleshooting)

The problem was that the same DN 5058 was created in Site 1. It was then bound to an unused Cisco Jabber Account. This caused calls to match on this number instead of Route pattern 5XXX leading to Site 2.

Everyone thanks for your help. I was really lost their.

[Nithin Eluvathingal]

Run Dialed Number Analyze  on site 1 and you will come to know more about what's the call flow   when you dial 5058 . 

[Nameless-IT]

It helped. Thanks.