IP-AA does not register after TAPS was installed, JTAPI stays PARTIAL-SERVI

[LESTERCAM]

On the CCM v3.2 the TAPS/BAT was first installed and works fine eventhough the JTAPI service is showing PARTIAL_SERVICE and all looks ok qua config.

When I added AA following the guidelines (standard 1 CTI-RP and 4 CTI phones & the user + the app in the end) the AA would not register i.e. the AA-CTI-RP I created for AA stayed in a status 'not found' while the RP-TAPS shows nicely registered to the CCM.

TASP is still working fine but calling the AA route point gets a busy tone.

The CTI follow (taps 5010-5011 and AA 5012 till 5015), CTI-RP's are 5001 for TAPS and resp. 5002 for AA.

Hope some help from outer space...

[LESTERCAM]

Hip Hip, I found it by chance.

The "user" for AA and TAPS must be the same so that in the Device Assocoations fo rthat user you get TAPS and AA CTI-ports and CTI-RP's all together. And ... for AA the 'No primary Extension' must be set which is not required for TAPS.

Easy when you know it.

Leo Jo Estercam