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

Intervening Network Region Question

Status
Not open for further replies.

lopes1211

Technical User
Jan 11, 2002
2,843
US
Question about intervening regions with Digital phones on G450's.

I want my digital phones at NR50 to connect to NR12 by going through NR1. I have the intervening region set in NR50 and NR2. Am I missing something? list trace is still showing NR50 calls to NR12 as directly connected to NR12. No reference to NR1.


display ip-network-region 50 Page 4 of 20

Source Region: 50 Inter Network Region Connection Management I M
G A t
dst codec direct WAN-BW-limits Video Intervening Dyn A G c
rgn set WAN Units Total Norm Prio Shr Regions CAC R L e
1 1 y NoLimit n t
2 1 y NoLimit n t
3 1 y NoLimit n t
4 1 y NoLimit n t
5 1 y NoLimit n t
6
7 1 y NoLimit n t
8 1 y NoLimit n t
9 1 y NoLimit n t
10 1 y NoLimit n t
11 1 y NoLimit n t
12 1 n 1: : : n t
13 1 y NoLimit n t
14 1 y NoLimit n t




display ip-network-region 12 Page 7 of 20

Source Region: 12 Inter Network Region Connection Management I M
G A t
dst codec direct WAN-BW-limits Video Intervening Dyn A G c
rgn set WAN Units Total Norm Prio Shr Regions CAC R L e
46
47
48
49
50 1 n 1: : : n t



Call from a phone in NR50 to an endpoint in NR12:

08:55:20 G711MU ss:eek:ff ps:20
rgn:12 [192.168.31.82]:8002
rgn:50 [192.168.1.114]:2050
08:55:20 xoip options: fax:T38 modem:pT tty:US uid:0x505ee
xoip ip: [192.168.1.114]:2050
08:55:27 idle station 6811602 cid 0x80d
08:55:40 TRACE COMPLETE station 6811602 cid 0x0







-CL
 
got inter-region direct IP enabled on 50 and 2?

Generally, everything should be direct to procr in NR 250 and 250 has no DSPs.

Now, I'd presume a MPLS hub and spoke where all spokes are equal and 50-->12 at the IP routing level would still go through the core. I suppose you have a good reason to not do that. Is 12 for something like call recording and you want to nail up certain DSPs for it?

In any case, if 12 reaches everything through 1 with no direct inter-region, that might help. Still, if that site's down, bad things happen. That's why they say procr 250, everything direct to 250, indirect to everything else thru 250.

Now, say NR1 is west coast DC and NR2 is east coast and you want your...west call recorder for example to use NR1 first, you can make bogus NR249.
West coast sites hit NR1 thru 250 and 2 thru 250 and 249. East coast sites you want to use DSPs in NR2 should be indirect to NR2 thru 250, and indirect to NR1 thru 250 and 249. CM calculates based on intervening region hop count.

The whole reason for using a core NR with no DSPs for procr is so that you can do this stuff. If 50-->12 always thru 1, the west data center, if 2 isn't an option, then the day it dies, failover doesn't work between those NRs.
 
We're converting our WAN over to a new topology and needed this as temp fix.

1 is on an MLPS with 50
1 is also connected to a different MPLS with 12

50 and 12 are not on a shared WAN. I would have thought what I had defined would have worked.

-CL
 
and yes 50 & 12 inter were flagged to No

-CL
 
inter and intra? what about 1? unless he's no to inter-region as well, he might be why they're not going thru it.
 
Connect 50 to 1 and connect 12 to 1 but don't put in any inter connectivity between 50 and 12. This will force 50 to anchor to a resource in 1.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top