AT&T PRI Sw Type

[jeter]

With AT&T using pri type 5ess what is the recommended type to set on call manger? The GW router is set correctly but in CM there are no specific 5ESS paramter.

Second question what would cause MGCP to bounce from SUB to PUB every few minutes at my remote GW. My thoughts are that the 1.5 MPLS circuit is the problem. I do not see the local GW's bouncing.




Spc NVARNG
Tek-TIP Member 19,650

 

[ptdog]

As for the switch type in CCM, I used 5E8 Custom and it works. Try 5E8 if it does not work.

As for the MGCP bounce, ensure MGCP packets are getting proper QOS for the MPLS. If anything, it may be IOS related. Most of my MGCP problems has been IOS related. A quick upgrade fixes the weird MGCP issues I have had.

If you suspect the MPLS, can you see problems with the CE router that connects to the MPLS. I would check for errors there to check things out.

 

[DallasBPF]

do you have QoS set up between the sites?

here is an example of how we have it set up between us and a remote site (remote config);

class-map match-all voice-traffic
match access-group 105
match dscp ef
class-map match-all voice-signal
match access-group 105
match dscp cs3
!
!
policy-map Dallas_Corp-VoIP
class voice-traffic
priority 768
class voice-signal
bandwidth 64
class class-default
fair-queue
!
interface Multilink1
ip address XXXXXXXXXXXXXXX 255.255.255.252
ip route-cache flow
ppp multilink
ppp multilink group 1
service-policy output Dallas_Corp-VoIP
!
access-list 105 remark ***CLASSIFY VOICE TRAFFIC***
access-list 105 permit ip 172.16.**.0 0.0.0.255 172.16.**.0 0.0.0.255
access-list 105 permit ip 172.16.**.0 0.0.0.255 172.16.**.0 0.0.0.255

source - remote voice vlan
destination - HQ voice vlan

Dallas, Texas
Telecommunications
CCNA, Net+
Working on MCSA, Convergence+, CCVP

 

[jeter]

Thanks for the reply.

We have QOS setup and all seems to be okay.

The problem we have noticed, is that when we see latency on the network (MPLS) with ping times in excess of 400ms for periods of time is when the sub fails over to pub thus causing the temp failure. This happens every two to three minutes.

During the evening when all is running at 40ms across the mpls circuit I never see the problem. The customer has upgraded thier IOS, but we still have the same issue.

Keep in mind that if we change the remote phones to use the host Pri's they work just fine. Cisco is now looking at trace logs!!!!






Spc NVARNG
Tek-TIP Member 19,650