<DIV> Type-o. I meant TRACE, not trade. Check the TRACE file for call setup and see if there's an allocation error. I have seen this issue happen with a SIP trunk configuration in Call Manager 4.x. Every call over a SIP trunk in 4.x requires a MTP.</DIV>
<DIV>-Dennis Hartmann<BR><BR>----- Original Message -----<BR>From: dhartma5@optonline.net<BR>Date: Monday, April 23, 2007 1:33 pm<BR>Subject: Re: [cisco-voip] VG224 T.38<BR>To: voip@mrga.ch<BR>Cc: cisco-voip@puck.nether.net<BR><BR>> I have seen this issue a lot and it's normally related to <BR>> media resources. Call setup and call teardown work properly, <BR>> but the final step of call setup fails. Analyze your call <BR>> manager trade file to see if the Call Manager is trying to use a <BR>> transcoding or media termination point resource. <BR>> <BR>> Sincerely,<BR>> Dennis Hartmann<BR>> <BR>> ----- Original Message -----<BR>> From: voip@mrga.ch<BR>> Date: Monday, April 23, 2007 9:20 am<BR>> Subject: [cisco-voip] VG224 T.38<BR>> To: cisco-voip@puck.nether.net<BR>> <BR>> > Hello all<BR>> > <BR>> > we still have a problem with a VG224 Gateway. We connected it <BR>> to our<BR>> > Callmanager<BR>> > 4.2(3) and configured some ports (MGCP). When we want to make <BR>> a call<BR>> > from a<BR>> > phone attached to the VG224 the destination phone rings and I <BR>> > can pick<BR>> > up the<BR>> > call. However I don't get a voice connection. The call <BR>> > terminates and I<BR>> > get the<BR>> > busy signal. After that I have to reboot the Port on the VG224.<BR>> > <BR>> > Has anyone an idea??<BR>> > <BR>> > Thanks Reto<BR>> > <BR>> > It seems that the problem is related to T.38 (see packet <BR>> capture <BR>> > below):<BR>> > No. Time Source Destination <BR>> > Protocol Info<BR>> > 34 7.574297 <BR>> > MGCP MDCX<BR>> > 205 AALN/S2/1@gw MGCP 0.1<BR>> > <BR>> > Frame 34 (208 bytes on wire, 208 bytes captured)<BR>> > Ethernet II, <BR>> > Internet Protocol, <BR>> > User Datagram Protocol, Src Port: 2427 (2427), Dst Port: 2427 (2427)<BR>> > Media Gateway Control Protocol<BR>> > MDCX (ModifyConnection)<BR>> > Transaction ID: 205<BR>> > Endpoint: AALN/S2/1@gw-test-fx1.hel.kko.ch<BR>> > Version: MGCP 0.1<BR>> > [The response to this request is in frame 36]<BR>> > Parameters<BR>> > CallId (C): A0000000010000b0000000F5<BR>> > ConnectionIdentifier (I): A<BR>> > RequestIdentifier (X): 9<BR>> > LocalConnectionOptions (L): L: p:20, a:PCMU, s:off, <BR>> > t:b8, fxr/fx:t38<BR>> > Packetization period (p): 20<BR>> > Codecs (a): PCMU<BR>> > Silence Suppression (s): off<BR>> > Type of Service (r): b8<BR>> > Unknown parameter: fxr/fx:t38<BR>> > ConnectionMode (M): recvonly<BR>> > RequestedEvents (R): L/hu<BR>> > QuarantineHandling (Q): process,loop<BR>> > <BR>> > <BR>> > No. Time Source Destination <BR>> > Protocol Info<BR>> > 36 7.577209 <BR>> > MGCP 510 205<BR>> > fx: setting cannot be supported<BR>> > <BR>> > Frame 36 (82 bytes on wire, 82 bytes captured)<BR>> > Ethernet II,<BR>> > Internet Protocol, <BR>> > User Datagram Protocol, Src Port: 2427 (2427), Dst Port: 2427 (2427)<BR>> > Media Gateway Control Protocol<BR>> > Response Code: The transaction could not be executed, <BR>> > because a protocol<BR>> > error was detected. (510)<BR>> > Transaction ID: 205<BR>> > Response String: fx: setting cannot be supported<BR>> > [This is a response to a request in frame 34]<BR>> > [Time from request: 0.002912000 seconds] <BR>> > <BR>> > <BR>> > <BR>> > _______________________________________________<BR>> > cisco-voip mailing list<BR>> > cisco-voip@puck.nether.net<BR>> > https://puck.nether.net/mailman/listinfo/cisco-voip<BR>> > <BR>> </DIV>