We're currently performing interop tests beteen OCS R2 and other PBXes in our lab (various releases of Cisco Call Manager and Alcatel-Lucent Omni PCX Enterprise).
We've run across an interesting issue where a call initiated by the Alcatel System is rejected with a 488 status code and an Invalid Gateway media error message.
The whole calls setup looks as follows:
Actors: caller: 3462 on PBX 10.145.27.72 Mediation Server: 10.145.206.156
I sniffed the entire traffic and there's no a single RTP packet going either way so it's really something about the INVITE that the mediation server doesn't like. Does anybody have an idea what that could be? The Contact field seems a little suspicious but the user part may be left out as it seems, but other than that it looks pretty standard to me.
My colleagues asked me to do some more detailed traces which reveal the culprit:
$$END-MEDIATIONSERVER TL_WARN(TF_COMPONENT) [1]07E4.02FC::02/12/2009-13:23:27.875.0000017f (MediationServer,MCCapabilitySet.CreateAudioMCMediaFormatFromSdp:mctypes.cs(272))Unexpected codecID CodecG7231 not found in the global dictionary. Codec name: G723/8000 TL_ERROR(TF_PROTOCOL) [1]07E4.02FC::02/12/2009-13:23:27.875.00000180 (MediationServer,GatewaySDP.ParseSdpOffer:gatewaysdp.cs(1207))( 0000000001B26EB8 )$$START-MEDIATIONSERVER MediationCall: 16fda7ebf94a439ab9082525ff225b0c CallId: 40ef70b2c54db65e2cb0754445efe07a@10.145.27.72 From: sip:+41448153462@10.145.27.72 To: sip:+419000@10.145.206.156;user=phone Direction: Inbound Start-Line: SDP parsing failed: Invalid media
Regardless of whether a codec is supported or not, this shouldn't happen - a sip device is supposed to ignore codecs it doesn't support and respond with the one it picked. I suppose the question becomes if it's possible to simply add the codec to the global dictionary.
