CUCM 11.0

[ReallyRotten]

I have recently experienced an issue I've never encountered. I swapped a PRI over to a newly IDENTICAL configured gateway. Outbound calling worked, however, the 1st call would be successful, but after I hung up the call and hit redial, the annunciator would come on and I'd hear "your call cannot be completed as dialed". So, after much head banging, the PRI was switched back to the original gateway. The problem persisted. NO changes were made. Anyone have a similar experience? Any suggestions?

It's call manager 11. There is a SIP trunk from CUCM to the Gateway and the gateway is configured as H323. Not a set up I did. :|

The other thing that happened on the newly IDENTICALLY configured gateway were a couple of ISDN errors that I have never seen before:
ISDN Se0/0/0:23 SERROR: isdn_init_name_iecs: Connected name not supported for this switch type
000565: Dec 13 08:37:06.490: ISDN Se0/0/0:23 SERROR: process_pri_simple: NO name in GTD

 

[gnrslash4life]

Seems like a caller id error. But I dont think thats causing your call failure. Have you run any debugs on the router when trying to make a call?

Certifications:
A+
Network+
CCENT
CCNA Voice
TVOICE
CAPPS
CIPTV1
CIPTV2

 

[ReallyRotten]

Yes and there is no debug available for the failure because as soon as I hit redial a 2nd time, I hear the annunciator. The call never makes it to the gateway.

 

[gnrslash4life]

Did you check DNA to see if the call is routing to the proper trunk?

Certifications:
A+
Network+
CCENT
CCNA Voice
TVOICE
CAPPS
CIPTV1
CIPTV2

 

[ReallyRotten]

Yes. So how it is working: make 1 call (local, LD, international, doesnt matter) and that call is successful. Press redial after hanging up the first call and that's when I hear the annunciator.

Do you have any insight on the ISDN errors I posted?

 

[gnrslash4life]

Yes, as stated before, its related to caller id. If your call is never hitting the gateway, you dont have an isdn issue. Are you positive both calls are trying to hit the same gateway?

Certifications:
A+
Network+
CCENT
CCNA Voice
TVOICE
CAPPS
CIPTV1
CIPTV2

 

[ReallyRotten]

I figured it out. There were 2 route groups in 1 route list. One of the route groups wasn't functioning, this is why every 2nd call was failing. The ISDN errors though I have never seen.

 

[gnrslash4life]

Yeah, I figured it was that. Glad you found it.

Certifications:
A+
Network+
CCENT
CCNA Voice
TVOICE
CAPPS
CIPTV1
CIPTV2