Cisco CallManager Fundamentals, Second Edition [Book]
Results 11 - 46 Conference Calls Secure Meet-Me Conference Ad Hoc Conference Linking Conference Linking using Join Configure Meet-Me to authenticate with Password/PIN when joining meet-me conferences in Cisco Unified Communications Manager (CUCM). Configuring Cisco Unified CallManager CDR, page 2 User A () calls into a meet-me conference bridge with the phone number • User B ().
When the File Manager runs, it deletes files with dates outside the configured preservation duration. It also checks whether disk usage has exceeded the high water mark. If so, the system deletes the processed CDR files until the low water mark is reached, starting with the oldest files.CUCM MeetMe Conference
However, if any CDR file to be deleted was not successfully sent to the specified billing server, the system leaves it in the CDR Repository and raises a notification or alarm. The system creates a flag file during the configured maintenance window, which denies access to the CDR files for the CDR ondemand Service. The system removes the flag file after the maintenance window expires. It receives SOAP requests for CDR file name lists based on a user-specified time interval up to a maximum of 1 hour and returns all lists that fit the duration that the request specifies.
All SFTP connections require userid and password information for each session setup. A separate SFTP session gets set up for every file that is sent, and the session is closed after the file has been sent. The system prohibits service during the maintenance window. You may also need to refer to the latest Data Migration Assistant User Guide and the latest upgrade documentation. See the CMR Processing section on page The CDR records store information about a call.
The CMR records store information about the quality of the streamed audio of the call. The system writes the CDR to a flat file text file. The system writes records when significant changes occur to a given call, such as ending the call, transferring the call, redirecting the call, splitting the call, joining a call, and so forth. The system sends these records to EnvProcessCdr, where they are written to the flat files.
The number of records that are written varies by type of call and the call scenario. When Diagnostics are enabled, the device generates CMR records for each call. The system also sends these records to EnvProcessCdr where they get written to flat files. The system writes the records to comma-delimited flat files and periodically passes them to the CDR Repository. Filename Format The following example shows the full format of the filename: Line 1 List of field names comma separated Line 2 List of field type comma separated Line 3 Data comma separated Line 4 Data comma separated The following example shows a flat file: Cisco Unified Communications Manager generates two different types of call information records: CMRs contain diagnostic information about the quality of the streamed audio of the call.
If one of these endpoints is involved in a call, it will generate a CMR record after the call terminates. Each endpoint in the call generates a separate CMR record. If the call involves endpoints that do not support call diagnostics, no record gets generated for that endpoint. A call from a Cisco phone to an H. Each type of call, such as conference calls, call transfers, forwarded calls, and calls through gateways, produce a set of records that get written to ASCII files at the end of the call.
The translated number, not the actual dialed digits, appears in the CDR. For example, many companies translate calls toso the caller does not need to dial an outside line in an emergency.
In these cases, the CDR contains even though the user dials Note Gateways can perform further modifications to the number before the digits are actually output through the gateway. The CDR does not reflect these modifications.
- Evading disasters
- Cacti Links
Partitions and Numbers Within a CDR, a combination of extension number and partitions identifies each phone that is referenced, if partitions are defined.
When partitions exist, fully identifying a phone requires both values because extension numbers may not be unique. The Partition field stays empty when a call ingresses through a gateway.
When a call egresses through a gateway, the Partition field shows the partition to which the gateway belongs. If the dial plan allows callers to use the key for speed dialing, the key goes into the database when it is used. For example, the Called Party Number field may contain a value such as.
For transferred calls, the transferred party becomes the calling party. This number designates the originally called party, after any digit translations have occurred.
For forwarded calls, this number designates the last party to receive the call. For non-forwarded calls, this field shows the original called party. For forwarded calls, this field designates the last party to redirect the call. For non-forwarded calls, this field shows the last party to redirect such as transfer and conference the call.
Cisco Unified Communications Manager Call Detail Records Administration Guide
This number identifies the partition name that is associated with the CallingPartyNumber field. This field uniquely identifies this number because the Cisco Unified Communications Manager supports multiple Cisco Unified IP Phones with the same extension number in different partitions.
For calls that ingress through a gateway, this field remains blank. For calls that egress through a gateway, this field specifies the partition name that is associated with the route pattern that pointed to the gateway. This number identifies the partition name that is associated with the FinalCalledPartyNumber field. This number identifies the partition name that is associated with the LastRedirectDn field. The calling party number outpulsed from the device.
The called party number outpulsed from the device. This value remains independent of daylight saving time changes. Unsigned bit integers represent all time values. This unsigned integer value displays from the database as a single integer. This field always gets populated.
Cisco Callmanager Maximum Number Of Meetme Connections
This field shows a zero if the call never connects. This field gets set even if the call never connects. The time gets stored as UTC. When the originating party releases the call, the OrigCause gets populated. When the terminating party releases the call, or the call is rejected, the DestCause gets populated. When unpopulated, the cause code value shows zero. Table on page lists the call clearing cause code values per ITU specification Q.
For Off Net call legs, the far-end switch determines the cause code value. To convert the signed decimal value to an IP address, first convert the value to a hex number, taking into consideration that it is really an unsigned number.
The bit hex value represents four bytes in reverse order Intel standard. To determine the IP address, reverse the order of the bytes and convert each byte to a decimal number. The resulting four bytes represent the four-byte fields of the IP address in dotted decimal notation.
Note The file displays a negative number when the low byte of the IP address has the most significant bit set. Step 1 Step 2 Step 3 Step 4 Convert the database display to a hex value. The hex value equals 0xBC12A8C0.
Reverse the order of the hex bytes, as shown below: The IP address displays in the dotted decimal format: When working with CDRs, you may want to read other tables in the CAR database to obtain information about the type of device in each CDR because the correlation between devices in the device table and the IP address that is listed in the CDR is not straightforward. You can enable or disable CDRs at any time that the system is in operation.
This chapter contains the following information: The audio quality scales up with the bit rate. Two mutually incompatible RTP payload formats are supported: This integer field contains the audio bandwidth. The system populates the bandwidth fields based on the following table: If logging calls with zero duration is enabled, the following actions occur: All calls generate a CDR. While it appears nice and simple to use and troubleshoot on the surface, this feature Meet-Me Conferencing can be a tricky thing to troubleshoot.
I've found that my ability to troubleshoot has improved as my understanding of the technology has improved. I need over a ! Other times, it is not. That doesn't tell the whole story. Necessary conference bridge resources are also required, and an understanding of how they will be allocated. Anyway, here they are - I hope that they help your understanding, or at the very least, encourage some additional study of this topic.
CUCME: How to setup hardware conference call bridge (meetme and Ad-hoc)
Meet-Me Conferencing Installation Checklist Configure the conference bridge s that will be used to facilitate the meet-me conferencing feature. This can be either software or hardware in type. Note that the initiator must have access to these conference bridge resources by nature of the MRGL assigned to the initiator.
This will be the number or range used by Meet-Me Conference initiators. Modify the Phone Template if needed so that the Meet-Me Conference button is available to only those that can initate the conference. If users will use the Join, ConfList, and RmLstC softkeys, modify either the Standard Feature or Standard User softkey template and assign the modified softkey template to the user device. Starting and Joining a Meet-Me Conference Meet-me conferences require that a range of directory numbers be allocated for exclusive use of the conference.
When a meet-me conference is set up, the conference controller chooses a directory number and advertises it to members of the group. The users call the directory number to join the conference.