Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Hi All,
I have two Acano X3 servers with which I am regularly polling the /api/v1/system/load API node to retrieve the mediaProcessingLoad value.
According to the Load Balancing Calls Across Cisco Meeting Servers White Paper, the X3's have a maximum ...
Hi All,
We have a CMS running 2.2.8 receiving an inbound INVITE from an SBC (below EXHIBIT A) advertising g.711alaw, which the CMS supports. However, the OK response from CMS is omitting the g.711alaw and causing the call to be torn down (EXHIBIT B)....
CUCM version 11.0.1.
When running the CAR, CDR > Search > By User/Phone Number/SIP URL. The Media Info value for all records is null.
All devices are TelePresence Endpoints running CE8.3.0 e.g. MX300/700/800 or DX80.
Does anyone know why this might b...
Hi All,Does anyone know if it is possible to customize the TMS CMR Create Email Message template? I don't see anywhere this is noted in the guide or the template in the TMS Edit Email Templates section. Current text placed into the email when a user ...
I've identified the cause of the problem now. Pending implementation to production and confirmation from TAC. The Supported header includes an "x-nortel-sipvc' extension, which when removed causes the CMS to send PCMA and PCMU correctly in it's SDP:
...
It's definitely a bug; we are working with TAC now.
I've done further testing, and the problem is isolated to specifically g.711alaw. If I send g.711ulaw only the call will establish no problem. So the issue seems to be specifically with the g.711a...
Hey Patrick,
Yes, the SIP detailed trace is what I had in the original thread (just the specific messages extracted). The logbundle shows nothing more then the same SIP messages mixed with the the logs from my other reply unfortunately.
Hey Zoltan, thanks for the reply. No, no hints as to why it's happening. Without SIP Tracing, these are all the logs CMS provides.
Oct 12 07:18:35 user.info CMS01 host:server: INFO : call 170: recognised as Nortel SIP GWOct 12 07:18:35 user.info C...