Breadcrumbs

Release Notes


Release

1.0.0

Release date

 

Release Summary

This is the first release of the CUCM Connector.

Features

Following are the business feature we support in our CUCM Connector. 

Register

Check if the required SIP Phone is registered, then the user will successfully log in via JTAPI User

Accept Call

User Can accept the Incoming Call 

Dial Outbound Call

Users can dial the Outbound Call via Dialpad

Blind Transfer

A user can blind transfer the call to the other user's extension 

Conference Call

A User can add another user to the Conference Room 

Transfer Consult Call

A user can consult the call on another user's extension before transferring the call.

Release Call

A User can release the ongoing call.

Release Test Highlights

Tested with:

  • This Release was tested with the CUCM 12.5.1 and also supports CUCM Cluster HA.

  • This Release is available in High availability.

Hard refresh is required to get the user back alive, when both CUCM connectors come up after the complete blackout.

Browser Compatibility Matrix

Browser

Version

Compatibility

Google Chrome 

106.0.5249.119 (64-bit)

Compatible

Firefox

109.0 (64-bit)

Compatible

Limitations

Issue

Use Case

Comment

Work Around

GetState Event 

  • Agent dials customer Number

  • Agent phone goes in Dialing & Customer goes in Ringing state

  • Call getState, agent state should dialing

GetState command will always return talking State whether it is in dialing or talking if the receiver phone is other than CUCM's Phone!

The use of getState is only in case of a refresh scenario,
So, this limitation will only affect the application in case of an outage or Re-Login!

System Limitations

Summary

Description

Related Feature

After Failover, User A start showing the dialing state when on consult call.

When failover happened during a consult call, the User who initiated the consult call started showing the Dialing state instead of the call controls div.

Failover

User unable to perform any action when any connector comes up after the complete blackout.

When any connector comes after both went down, User is unable to perform any action on the interface.

Failover