No CDR MCU logs on MSDS

Similar Questions

• Application of floor on Codian MCU

  Hi all

  I want to know the meaning of the events by Codian MCU log output when endpoint sent a request for floor.

  There are newspapers that I captured after that I sent a request floor MXP endpoint.

  Conference CONFERENCE Info 13959 29/07/2012 17:29:43.254 'Name of the Conference' - set floor participating 1272

  Participant of CONFERENCE Info 13960 29/07/2012 17:29:43.254 1272: grateful request floor

  13961 29/07/2012 17:29:43.299 CONFERENCE Info participant_message_fn 1272: request floor

  Could someone let me know what each line means?

  Best regards and thanks in advance

  Kotaro Hashimoto

  Hi Kotaro-san,

  Third line in the newspapers show the message, it is not sent by MCU.

  It shows the real message received by request IE MCU for floor.

  Not sure what is "fn" stands for.

  Kind regards

  Sagar

• SIP call failures

  Hey all,.

  I'm an EX90 out in the field, running TC6.3.  The EX90 is registered via H323 & SIP at our VCS-E that is running X7.2.2.  The user can call our via H323 MCU without problem, but if the same call via SIP of his unit it disconnects immediately and says "No multimedia codecs shared" in the VCS.

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

  EX90 joint papers and they have been taken with the 'Extended loggin' enabled.

  Thank you

  Justin Ferello
  Technical Support Specialist
  KBZ, a Cisco authorized dealer
  http://www.KBZ.com
  e/v: [email protected] / * /

  There is no shared multimedia codecs from the MCU - it supports encryption, as endpoint is dealing with media encryption forced - RTP/BIBI, if xConfiguration conference 1 encryption Mode is set to BestEffort, so maybe it's the profile type parameter that requires.

  You will likely see the MCU logs to see what he doesn't like.

  Thank you

  Guy

• MSD vs MCU recompose the behavior

  In TMS, there is an option, 'Attempts to connect for scheduled calls' and a 'time of connection for calendar (in seconds) calls' of coorisponding.  There is also a similar function within the MCU 8510, "Failed preconfigured participants renumbering of behavior."

  1. Plan us all of our meetings within TMS, how these two systems to coordinate the recall of failed calls and participants, or do at all?
  2. When you use an MSDS, it overrides the MCU Redial function?
  3. As TMS adds all regular calls in the list of preconfigured participants, what callback behavior method would be the most beneficial or practical since it is located in the TMS and MCU 8510?

  'Connection Timeout for planned guest' TMS and the "bis participating preconfigured failure behavior" on MCU service similar recomposition.

  If you use "connection for calls Timeout to demand" on MSDS, then "Failed preconfigured participants behavior redial" on MCU must be configured to as 'never bis.

  For recommendation, if you are investigating CCC and conference log on TMS, recommend to use "Connection for scheduled calls Timeout" TMS as well as you can manage the call log callback instead of wait for the update of MCU call State.

• MSDS number for MCU (Codian)

  Hello guys,.

  In TMS (v13.2.2), you can set up a MCU (Codian) and provide a number and a step that TMS should use as the number to dial

  It restarts every day!

  Is it possible to change this behavior and continue through the range of numbers until it reaches the end of the beach before starting again with the first issue?

  The current behavior (every day starting with the same number) is a security risk that those who dialed the number on the wrong day could end up in a conference.

  Any idea?

  Vincent

  Hello Vincent.

  Currently MSDS does not use the numbers in step, as you have noticed they restart at the beginning once it is free or actually used.

  This has been asked several times, I remember some discussions here and there, and I think has submitted a request for feature by someone, but don't remember or can't find old discussions.

• Random Jabber disconnections of MCU calls

  Good afternoon

  Hope you can help me. I've seen a few posts with these error messages in but they are not quite what is happening here

  My customer is having a problem, where a number of their Jabber users (for windows) is randomly calls MCU is disconnected on their server of telepresence. The disconnection occurs in less than a minute.

  None of the presentations are shared when this happens.

  The errors are:

  Operation BYE failed because the network error

  End of appeal because INVITE it transaction timeout

  Call due to the failure of closing invitations

  GST 320 - software version: 4.0 (2.8)

  Made - known Jabber clients versions 4.4 and 4.7

  Currently waiting for the client to update me on MSDS, blade of conductor and versions of software VCSE and VCSC

  event_log_screenshot.PNG

  

  telepresence_server_status.PNG

  

  I hope you can help

  Thank you very much

  Luke

  In general, this is because of a network problem, where SIP messages are not sent correctly between Jabber and reliable TP server, in this case, I'm guessing the OK/acknowledgement of receipt are not sent to the head of the Orchestra/TP server and the server TP is disconnecting the call. Is there a firewall in the mixture, do you SIP ALG turned on? If I look at the firewall and disable SIP algo

• Automatically add the MCU recorded lectures

  Hi all

  When you create a conference call between and endpoint and a registration server, the MCU should be automatically added to these conferences. At present, the MCU will only add itself when the particular codec models are currently in use.

  for example

  Click new conference, add ONE of the following, codec models

  1700MXP
  770mxp
  880MXP
  Edge 95MXP
  3000MXP

  Add TCS registration server and it WORKS, the MCU is automatically added. This allows us to customize the page layout (we generally to mute the video of the CSTC). See green arrow in the attached jpeg.

  Repeat the process on any of these models.

  C40
  SX80
  SX20
  C20
  EX60
  Polycom HDX 8000 HD
  6000MXP

  Now, it fails. The MCU not will automatically itself add to the Conference. See the red arrow in the attached jpg.

  Any ideas? The only thing that I know so far is that its broad base of model of endpoint. I have searched on the parameters of MCU, MSDS etc but can't find anything related to this at all.

  Thank you very much

  Rhys

  Don't know why the MCU is automatically added for some endpoints and not others without knowing more about the configuration keys and the option on the endpoints.

  If you want the MCU to always add to scheduled conferences, you must set the following options under administrative tools > Configuration > conference settings:

  1. External MCU use in routing: always
  2. MCU route Type preferred: Cisco TelePresence MCU

  The configuration of this setting is the only way to ensure an MCU is always included, please note that this is a system wide setting and will affect all scheduled conferences regardless of the number of participants and who they are.  If you wish, you can also set the first option above 'Always, except for point to point', which will allow you to choose when the SCM must be used if you have rather a choice between point-to-point and multipoint calls using the MCU.

• TMS 14.3.1 played not well with Codian MCU 4520 - bug?

  TMS 14.3.1

  Codian MCU 4.4 4520 (3.57)

  After upgrading from 14.3 to 14.3.1 MSDS that I find THAT TMS is no longer recognizing the Codian as being registered at a Registrar SIP (VCS - C x7.2.2) and active SIP server address is empty.

  As a result, it is no longer allow me to plan only calls SIP; that is to say:

  

  In the above Conference, participants at the Summit must be either H.323 or SIP, participating below place SIP (JabberVideo customer 'business'), as well as participating number 3 (customer 'free' JabberVideo).

  Before the upgrade, I've always had the choice of SIP, H.323, and if necessary, IP, now I have only the choice of H.323 and where appropriate, IP.

  Curiously, when using multi-way, it will connect to the customer external jabber.com as SIP - SIP, while in a scheduled call, he'll be H.323 - SIP and appeal in the VCS - E it actually displays H.323 - H.323.

  I have no problems with the old MPS800; Active listed address in TMS SIP server as per normal, and I can choose to H.323, SIP and IP.

  So, is this a bug?

  /Jens

  Please note the answers and score the questions as "answered" as appropriate.

  In the MCU configuration.xml, should say something like:

  user_name VCS.example.com"registrar_name =" example.com"="[email protected] / * /"/ >" "

  The field that is empty in your TMS screenshot ("Active SIP server address") must have been populated by proxy_name value in the confiuration.xml that I can see.

  EDIT: looks like we have made a code change in TMS 14.3.1 when it comes to check the address of the SIP server: in previous versions, read and used TMS 'registrar_name', but from 14.3.1, it reads and uses the "proxy_name" instead.

  Kjetil-

• Meter "Remaining time" on page Conferences MCU

  Hello!

  During the planning of a conference at TMS involving a MCU, once the Conference begins the time remaining, such as expressed in the MCU is 15 minutes more than what you have planned.

  Is it a kind of fill that TMS sends to the MCU, a bit like TMS as one endpoint in a special appeal as being occupied for the next 5 minutes?

  This is seen in the following combinations: TMS14.3 (beta) / MCU 4.4 (3.54) & TMS13.0/MCU 4.3 (2.32)

  Thank you!

  Hello

  It is in fact be design. TMS does like that to ensure that MSDS is the tearing down of the Conference; We do not want the MCU to demolish SE for example if there are subtle differences between the MCU and TMS.

  Kind regards

  Kjetil

• Schedule a conference recorded on MSDS

  Hi friends,

  I need your help!

  We got a Cisco TMS, VCS, 4515 MCU environment and a VCR. Everything works fine, all the server are registered with MSDS and we are able to plan the Conference normally.

  There is just one detail, when we go to the TMS web page to create a new conference, we do not have the ability to check the "Recording" at this conference, the option does not appear. According to the help page of TMS, this 'Recording' option should only appears if the TMS has a "Record" to it. We have a record device available in TMS, that is the VCR, in fact, it appears on the MSDS Portal as a "recording and streaming devices", so I think that the 'Record' option should appear when a new conference is scheduled.

  This option should appear when we have VCR or is it only available when we Tandberg Content Server as a record device?

  I looked for documentation, but I found nothing.

  TKS,

  Paulo Souza

  Hi Paulo

  If you want to get the record numbers in the menu drop-down, I'm sorry but it is not possible for the IPVCR. This only works for the content server (TCS).

  / Magnus

• Reports > CDR > time user CDR

  Hi all

  I'm under TMS V13.0 with VCS 6.1 and we were see CDR USER CDR Records and now we are not.  Is there a time limit as to how often they appear?  If I make a call 8 PM CST and my server TMS in CSE.  I hang up the call 8:10 PM CST I'd be able to go in the CDR Records and see the call displayed record immediately or is there a period of time it is updated.  CDR Records have something to do with the replication Agent MSDS?

  New to this part of TMS any advice would be appreciated.

  Thank you

  Wally

  Walter,

  It's very interesting, your location is totally different from mine, yet we never had problems with our CDRs or MOVI CDRs.

  *s Feedback 3:
  Status: On
  URL: "https://10.9.8.190/tms/public/feedback/code.aspx"
  Expression: "/Event/CallDisconnected"
  Expression: "/Event/CallConnected"
  Expression: "/Event/CallFailure"
  Expression: "/Event/RegistrationAdded"
  Expression: "/Event/RegistrationChanged"
  Expression: "/Event/ResourceUsage"
  Expression: "/Event/AuthenticationFailure"
  Expression: "/Status/Warnings"
  *s/end
  

• CDR GW on TMS

  Hi all

  Does anyone know if TMS 13.1.x may collect or receive logs ISDN GW 3241 (v2.1) CDR?

  There is a tab in TMS (in the system, records > call log), but it is always empty.

  PS: The Gulf war is added as a system in TMS, with SNMP. In this context, they don t use TMS to plan calls.

  Thank you

  This is a known bug (CSCts33831), and a fix will be released in Cisco TMS 13.1.2.

  You can get 13.1 TMS to pick up the ISDN GW CDRs by running the following SQL query on your database TMSng:

  ----       INSERT INTO objSystemCDRProcessStatus (SystemId, LastUpdated, LastAttempt, LastEventReceived)                   SELECT Id,'1900-01-01T00:00:00Z','1900-01-01T00:00:00Z', GETDATE() from objSystem                   where objSystemType_Id = 41                   AND Id in (select Codec_Id from objFolder_System)                   AND Id NOT IN (select SystemId from objSystemCDRProcessStatus) ----

  You'll only run the query once, unless you later add a new GW to your TMS.

• MCU 4501 gatekeeper

  Hello

  Problem - gatekeeper integrated Cisco MCU 4501 cannot connect to a neighbour a keeper:

  

  In a nearby doorman it configured as a neighbour.

  Why would it be?

  In this case, I think you must turn on the logging feature H323/SIP on the MCU-> h323/SIP Journal newspapers, try to make a call and see what requests appear from the endpoint in the log that results.

• Automation of MCU events

  Hi all

  Is there a way by which we can get notifications automatically at certain events in MCU?

  For example: get an email notification, because soon the video ports reached its capacity. As in MSE 8510 soon 20 HD ports get used email or some sort of notification can be sent to the admin. Right now the only way is to keep monitoring the page Conference or event logs. If there is a way by using another application (can be in curl) / syslog server MCU can send a trap and then it can still trigger a mail server to send an email, or any other way, please let me know.

  Thanks in advance.

  Kind regards

  Gerard

  This has been asked several times before, even by myself, and if anything has been done recently, it is not possible.  There is even an open for this enhancement request apparently CSCuc94233.  Alternately, if you use the conductor, you could get something close to him using the capacity of the conductor to monitor the ability of the configured conference bridges.

  Here are some of the latest discussions.

  Video-Load-MCU-5310-through-XML-RPC

  Need-Monitor-Media-port-Utilization-8510

• TMS by booking with MCU in cascade

  Hello

  My client has questions about booking TMS, they have 2 microcontrollers (4205,5320), CTS and 14.2 TMS endpoints

  They want to use 5320 as the main rooms for booking, but if the resource on 5320 is not sufficient for the booking then cascade 4205 to increase capacity.

  I found in the admin MSDS distribution routing guide (low cost print routing and better) but I'm not sure this device meet the requirement.

  The Administrator's guide also said "Different MCU models using cascade when manually configure cascade is not supported in Cisco TMS"

  Note it doesn't you different medium cascading of MCUS in TMS is not supported?

  Anyone try this before please advice.

  Thank you.

  Kind regards

  Wassila

  You can't necessarily force TMS to use a 5320 on a 4205. Remember, TMS treats all the ex-codians as the same, so it is not defined which, two bridges, TMS will prefer.

  Also note that MSDS does not automatically cascade; cascading always requires the invention of the user. The user must explicitly choose a distribution algorithm.

  Kjetil-