[cisco-voip] Inbound calls on FXO ports (MGCP) fail - error in
CCM traces
Erick Bergquist
erickbe at yahoo.com
Fri Jun 10 02:30:02 EDT 2005
Update to my own posting,
Now also seeing the problem one or two times with
inbound calls on FXO ports which have attendantDN set
to a IP phone which is registered/working fine on
system. This is a call coming from another gateway
also.
In CCM Detailed traces with all options checked, see
call come in then this error, then busy sent to
gateway. No attempts of trying to call the IP phone,
attendantDN. nothing in SDL traces is revealing
either. The outside calling party hears a ring then
busy signal.
So appears problem is not related with CTI but with
MGCP/FXO ports and CCM in general now that seeing it
for another gateway not routing to CTI route point.
MGCP TrunkD: ERROR Unable to receive call for FXO
Trunk-check portType/callAttendent
Anyone see activity like this before off and on? I
have a TAC case open but in wait and see mode until
next issue occurs to look at more traces.
--- Erick Bergquist <erickbe at yahoo.com> wrote:
> We have issue where we are losing inbound calls
> frequently due to calls hearing a ring, then a busy
> signal.
>
> 2811 MGCP Gateway going to CCM 4.02(a) SR1a
> FXO ports Attendant DNs configured for CTI Route
> Point
> DN.6 FXO ports on gateway, all configured same in
> CCM
> and problem is happening on different ports at
> different times of day.
>
> 2811 is on 12.4(1) IOS and CUE is on 2.1.1
>
> CTI RP is a AutoAttendant trigger on a AIM-CUE
> module
> in 2811.
>
> On calls that fail, we see this in CCM detailed
> trace.
>
> ERROR Unable to receive call for FXO Trunk-check
> portType/callAttendent
>
> Trace snippet (CCM Detailed):
>
> 06/07/2005 15:13:58.105
>
CCM|<CLID::StandAloneCluster><NID::172.16.1.2><CT::2,100,58,1.744
> 826><MN::MGCPEndPoint><MV::aaln/S0/SU0/3 at GW2801
> ><DEV::>
>
>
> 06/07/2005 15:13:58.105 CCM|MGCPTrunkD - ERROR
> Unable
> to receive call for FXO
> Trunk-check portType/callAttendent
>
DN.|<CLID::StandAloneCluster><NID::172.16.1.2><CT::2,100,58,1.744
> 826><IP::172.19.4.2><DEV::aaln/S0/SU0 at GW2801>
>
>
> 06/07/2005 15:13:58.105 CCM|MGCPHandler send msg
> SUCCESSFULLY to: 172.19.4.2
> 200 325636426
>
|<CLID::StandAloneCluster><NID::172.16.1.2><CT::2,100,58,1.744826
> ><IP::172.19.4.2><DEV::aaln/S0/SU0 at GW2801>
>
> 06/07/2005 15:13:58.105 CCM|MGCPTrunkD -
> MGCPOutputStartTone: 76
> endpointId=AALN/S0/SU0/3 at GW2801
>
|<CLID::StandAloneCluster><NID::172.16.1.2><CT::2,100,58,1.744826
> ><IP::172.19.4.2><DEV::aaln/S0/SU0 at GW2801>
>
> 06/07/2005 15:13:58.105 CCM|MGCPHandler send msg
> SUCCESSFULLY to: 172.19.4.2
> RQNT 237010 AALN/S0/SU0/3 at GW2801 MGCP 0.1
> X: 0
> R: L/hu, D/[0-9ABCD*#]
> S: T/ro
> Q: process,loop
>
>
>
> __________________________________
> Yahoo! Mail
> Stay connected, organized, and protected. Take the
> tour:
> http://tour.mail.yahoo.com/mailtour.html
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
__________________________________
Discover Yahoo!
Use Yahoo! to plan a weekend, have fun online and more. Check it out!
http://discover.yahoo.com/
More information about the cisco-voip
mailing list