Jerry, I'm assuming that you mean that Cisco calls are making it to Asterisk, but Asterisk calls are getting the rejection.
Looking at this again, there is probably not a network path issue since packets are being sent and received. Doing some quick research on what Cisco defines as a "503 Service Unavailable", there is a Cisco document that gives a better explanation: http://www.cisco.com/en/US/docs/ios/12_2t/12_2t11/feature/guide/ftmap.html A CCM trace on the CM's end might give a better reason why the 503 was returned. Sorry for putting you on the wrong path before. Dean Jerry Geis wrote: >> >> Warning: 399 "Routing failed: ccbid=6361 socket=ast_server:5060" >> >> Confirm the Cisco CM can ping ast_server. Also try using the IP address >> versus a name. >> >> Dean >> > > Dean > > I have asked the person onsite to try the ping... > > Actually we are using IP address and not names. I just change to a name > so as to not show the IP address on > the list. > > Jerry > > _______________________________________________ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > > AstriCon 2009 - October 13 - 15 Phoenix, Arizona > Register Now: http://www.astricon.net > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users > _______________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- AstriCon 2009 - October 13 - 15 Phoenix, Arizona Register Now: http://www.astricon.net asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
