No Route to specific transit network

[Praest]

Hi

I have been google my ass of, to find an answer to my problem, but nothing seems to help.
So I am hoping that someone in here can help me out.

My problem is like this..

I have 11 IPO connectet in a SCN, with one unit as the center of them all.
There are IP Lines between the center IPO and all the others.

My problem is that I experience call beeing disconnectet when they are answered.
I have made some logs from System Monitor and in this I can see the following.

CMLineRx: v=90
CMReleaseComp
Line: type=IPLine 90 Call: lid=90 id=155 in=1
Cause=2, No route to specific transit network/(5ESS)Calling party off hold
83333510mS CMLOGGING: CALL:2012/05/3013:41,00:00:01,002,1713,I,7608,7608,AMLarsen1,,,0,,""n/a,0
83333511mS CMLineTx: v=100
CMReleaseComp
Line: type=IPLine 100 Call: lid=0 id=10176 in=0
Cause=2, No route to specific transit network/(5ESS)Calling party off hold

The caller here in the log, is me.

I have tried to use difference phone types (4610SW IP / 1616 / 1616L)
The core version of the IPO is: 6.1.22
The center unit is IPO 500V2, and the others are 406 and 500v2.

Can everyone help me further in finding an solution to this problem?

Thanks


Question: What are you good ad?
Answer: I'm GOOD in bed.
Yesterday I slept 9 hours.

 

[amriddle01]

Try turning off Direct Media Path for the extensions and SCN lines

 

[Praest]

Hi

I have already turned this off, but I'm still getting the error.

It's not every time that an call being disconnected when answered, but out of 10 times it happens 3 times, so it's a problem that people notice now. :-(

Question: What are you good ad?
Answer: I'm GOOD in bed.
Yesterday I slept 9 hours.

 

[tlpeter]

This is what is means:

Cause No. 2 - No route to specified transit network (national use).
This cause indicates that the equipment sending this cause has received a request to route the call through a particular transit network which it does not recognize. The equipment sending this cause does not recognize the transit network either because the transit network does not exist or because that particular transit network not serve the equipment which is sending this cause.

Basically, something is wrong

BAZINGA!

I'm not insane, my mother had me tested!

 

[Praest]

Hi

I have also found out, what the problem means, but still this doesn't help me out, in finding out how to solve this.

Any ideas here?

Question: What are you good ad?
Answer: I'm GOOD in bed.
Yesterday I slept 9 hours.

 

[amriddle01]

What are the system firmware levels for the systems, i.e what is the highest vs the lowest

 

[tlpeter]

I think there is a mismatch on your trunk settings and what your povider needs/has.


BAZINGA!

I'm not insane, my mother had me tested!

 

[amriddle01]

Are these calls coming into the main system on ISDN or are they a remote site via the main systems ISDN line? Does this effect all calls or just those to remote sites?

 

[Praest]

To answer some of your questions...


All IPO runs at the same firmware version: 6.1.22 (The IPO 406V2 can't go any higher)


I don't think so.
As far as I have found out, the problem only exist internally between the IPO, when dialing local numbers though SCN.


In all the test that I have performed, the problem never exist when the call first arrives at an ISDN line, and then out in the SCN.
I only exist when calling an user directly though the SCN connection.


Question: What are you good ad?
Answer: I'm GOOD in bed.
Yesterday I slept 9 hours.