cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
502
Views
0
Helpful
8
Replies

Testing special outbound dialing

billmatthews
Level 1
Level 1

We have a CUCM 8.6 environment, with a couple different cube gateways with various SIP trunks.

For normal operations we have a partition that points to a route list/group that lists our gateways in the correct order.

However for testing I would like to be able to force a call out our secondary gateway.   What's the best way to set that up? 

I could create a route pattern for a specific external DID, and point that to a different route group?

Or could I put a single device (test phone) in a different partition so all calls from that phone go out via a different route group?

Thanks

2 Accepted Solutions

Accepted Solutions

Chris Deren
Hall of Fame
Hall of Fame

Create seperate Route Group, Route List, set of Route Patterns in test parition, assigned that PT to test CSS, and assign that CSS to your test phone.

HTH,

Chris

View solution in original post

Make sure the domain matches what is on the GW and what is on CUCM GW.  Also, try issuing "no mgcp", "mgcp". But your best option would be to ditch MGCP and use SIP instead as MGCP is known for chronic issues such as this.

HTH,

Chris

View solution in original post

8 Replies 8

Chris Deren
Hall of Fame
Hall of Fame

Create seperate Route Group, Route List, set of Route Patterns in test parition, assigned that PT to test CSS, and assign that CSS to your test phone.

HTH,

Chris

That process worked perfectly, thank you.

I was able to individually test all my CUBE routers with SIP trunks.

However I was unable to test my outbound PRIs.

When I place the PRI gw first in my route list, it doesn't use it...the call goes through the SIP routers. 

Any ideas?  Any debug commands I could use on my PRI gw to see if that's why it was failing?

Provide "debug isdn q931" and "debug voice dialpeer" from the PRI GW?

What protocol are you using to control it from CUCM?

Chris

No output from the debug commands, so I think it isn't even trying that gateway, despite it being first in the RL.

Protocol is MGCP

I also ran a Dialed Number Analyzer, and confirmed it should be using the PRI GW. 

Is the PRI port showing registered? Can you provide "sh ccm-manager" output from the GW?

Chris

Yep thanks that's the problem, the GW is not registering...

sh ccm-manager

MGCP Domain Name: PRIGW01

Priority        Status                   Host

============================================================

Primary         Backup Ready             10.10.22.5

First Backup    Registering with CM      10.20.22.5

Current active Call Manager:    None

Backhaul/Redundant link port:   2428

Failover Interval:              30 seconds

Keepalive Interval:             15 seconds

Last keepalive sent:            15:48:41 EST Jun 24 2013 (elapsed time: 7w0d)

Last MGCP traffic time:         14:34:58 EST Dec 5 2013 (elapsed time: 00:00:18)

Last failover time:             14:34:58 EST Dec 5 2013 from (10.60.227.7)

Last switchback time:           14:34:28 EST Dec 5 2013 from (10.50.227.7)

Switchback mode:                Graceful

MGCP Fallback mode:             Not Selected

Last MGCP Fallback start time:  None

Last MGCP Fallback end time:    None

MGCP Download Tones:            Disabled

TFTP retry count to shut Ports: 2

Backhaul Link info:

    Link Protocol:      TCP

    Remote Port Number: 2428

    Remote IP Address: 10.10.22.5

    Current Link State: OPEN

    Statistics:

        Packets recvd:   0

        Recv failures:   0

        Packets xmitted: 0

        Xmit failures:   0

    PRI Ports being backhauled:

        Slot 0, VIC 1, port 0

        Slot 0, VIC 0, port 0

FAX mode: cisco

Configuration Error History:

Make sure the domain matches what is on the GW and what is on CUCM GW.  Also, try issuing "no mgcp", "mgcp". But your best option would be to ditch MGCP and use SIP instead as MGCP is known for chronic issues such as this.

HTH,

Chris

Thanks, the no mgcp/mgcp fixed it.

I'll consider a move to SIP.

Thanks very much for all the help