SIP Call Failures

[Justin Ferello]

Hey all,

I got an EX90 out in the field, running TC6.3.  The EX90 is registered via H323 & SIP to our VCS-E which is running X7.2.2.  The user can call our MCU via H323 without issue, however if he calls the same number via SIP from his unit it disconnects right away and says "No shared media codecs" in the VCS.

I looked at all the configs on his unit and they are fine.  I am not able to reproduce the problem from other units.      

Logs attached from EX90 and they were taken with the 'Extended loggin' enabled.

Thank you,

Justin Ferello
Technical Support Specialist
KBZ, a Cisco Authorized Distributor
http://www.kbz.com
e/v: justin.ferello@kbz.com       

[gubadman]

Hi Justin,

I'm still looking at the logs, but first thing I noticed is:

*r DiagnosticsResult Message 21 Type: SIPProfileType

*r DiagnosticsResult Message 21 Level: Warning

*r DiagnosticsResult Message 21 Description: SIP Profile Type set to Cisco, not registered on CUCM

*r DiagnosticsResult Message 21 References: vendor=other&profile=cisco

The SIP Profile Type should be set to Standard if connecting to a VCS.

Thanks,

Guy

[Justin Ferello]

Guy,

Yes, I noticed that as well this morning, had the user change to standard and try again, still seeing the same issue on the VCS.

Thank you,

Justin Ferello
Technical Support Specialist
KBZ, a Cisco Authorized Distributor
http://www.kbz.com
e/v: justin.ferello@kbz.com

[gubadman · Accepted solution]

The no shared media codecs is coming from the MCU - does it support encryption, as the endpoint is dialling with forced media encryption - RTP/SAVP, though xConfiguration Conference 1 Encryption Mode is set to BestEffort, so it might just be the profile type setting forcing that.

Probably need to see logs from the MCU to see what it doesn't like.

Thanks,

Guy

[Justin Ferello]

Guy,

The MCU does have encryption disabled because BFCP does not work with encryption on the MCU software.  Anyway how can he be forcing encryption when the setting is BestEffort?  Also, we did change the 'Type' to standard and still having the same issue, I shoul,d have new logs shortly.

Can you show me where in the logs you can tell that the encryption is being forced?  I would like to learn

Thank you,

Justin Ferello
Technical Support Specialist
KBZ, a Cisco Authorized Distributor
http://www.kbz.com
e/v: justin.ferello@kbz.com

[gubadman]

Hi Jusin,

In the file all.log in the current\eventlog\ directory - the messaging is in there. The INVITE is sent at Nov 26 11:15:52.920

And it has RTP/SAVP on the media lines and crypto lines in the SDP within the INVITE.

Thanks,

Guy

[Justin Ferello]

Guy,

Thank you for the hint, it was the encryption mode.  I had him change it from BestEffort to Off, save and then change it back to BestEffort and now he can connect fine to the MCU.

Thank you,

Justin Ferello
Technical Support Specialist
KBZ, a Cisco Authorized Distributor
http://www.kbz.com
e/v: justin.ferello@kbz.com

[gubadman]

No problem. Good to hear it's fixed.

Thanks,

Guy

[Martin Koch]

It is also interesting to know how the Media encryption mode settings on the vcs for the zones are where your

client and the mcu are in.

What is the setting on the mcu for Encryption (encryption and srtp)?

Besides that I would think of disabling sip to the mcu, use h323 and let the vcs interwork and

keep the media encryption mode on the vcs zones to auto.

Please remember to rate helpful responses and identify helpful or correct answers.