CloudPBX Version: 7.5.x

Issue Description:

• Adding function key or dial plan sections to the UAD invalidates or corrupts XML file.

• Any XML tag that requires 'idx="0"' or similar fields fails to be passed through to handset and is therefore invalid.

Work Around:

• None

Reported To Vendor: Yes

Resolved in Version: Awaiting update from vendor

CloudPBX Version: 7.5.x

Issue Description:

• When attempting to access the internal directory from Yealink AX83H wifi handset results in "Cannot download remote phone book" error

Work Around:

• None

Reported To Vendor: Yes

Resolved in Version: Awaiting update from vendor

CloudPBX Version: 7.5.x

Issue Description:

• When renaming an ERG all group members will be deleted and they will need to be added back in

Work Around:

• None

Reported To Vendor: Yes

Resolved in Version: 7.6

CloudPBX Version: 7.5.0.3

Call Flow Setup:

• DID is routed to and ERG (enhanced ring group)

• ERG has a single member (x1000)

• Disable Member Enhanced Services = No

• That member has a call forward immediate (CFA) to another extension (x1001)

Issue Description:

• An external party calls the DID, the call is routed to x1001 as expected.

• If x1001 ends the call, there is no issue

• If the external party ends the call, any further calls to the ERG will 'sit' in the ERG and will not be routed. If x1000 (member with CFA) makes a call, calls will start routing again. x1001 making a call has no affect.

Work Around:

• Use another method of diverting the calls to the second extension.

Some possible methods

• Add the second extension as a member of the ERG

• Configure Operation Times on the ERG, then use either BLF keys or dial codes to toggle the op times. See Operations Times for more information

Reported To Vendor: Yes

Resolved in Version: Awaiting update from vendor

CloudPBX Version: 7.5.0.x possibly other versions

Call Flow Setup:

• DID is routed to and ERG (enhanced ring group)

• ERG has 'Wake up Mobile Devices' turned on

• ERG Member is also logged into Communicator GO

Issue Description:

• When answering a call in Communicator a incoming call will appear from members own extension and immediately be report as a missed call

Work Around:

• None

Reported To Vendor: Yes

Resolved in Version: 7.6

Android Communicator GO Version: 7.5.7-build 428

Issue Description:

• When attempting to make a call using Communicator GO whilst using Telstra Mobile Internet (or resellers) the call will fail with error "There was an error with the call: (488)"

Work Around:

• Connect devices to WiFi

Reported To Vendor: Yes

Resolved: Yes