During some test reviews , I have encountered the following issue . I was dealing with one UCCX script which must call agent in different location and I was receiving some beeps before to jump in the default script ‘Sorry we are experiencing ….’ .
It was happening only when agents were logged. After looking more deeply , it was impossible to set up an agent in a ready mode at the remote location , they were in a reserved mode.
After some investiguations, I saw that I have forgotten to remove the location bandwidth restriction to test the AAR functionality . So I was hitting the fact that my ICD applications can’t dial any remote agents due to a lack of bandwidth. Removing this restriction of bandwidth has resolved the issue.
But my question was then to see how we can correct this as AAR was configured on my agent phones and you can also specify AAR group under your CTI configurations.
The result is there even if you have the opportunity to configure AAR under your CTI ports . It will not succeed as it is a limitation of UCCX.
So don’t rely on AAR to save your call center script for remote agents!!!
Apparently Cisco has decided today to remove the OEQs for the IE Voice track and R&S.
This is the big discussion about it on every blog/forums . Now we must see what they will bring for the troubleshooting section …. hmmmm… wait and see
It was a while that I haven’t post something, but the reason is simple. I’m doing my lab and try to practise and practise , doing practise as much as possible.
Until now (1 month), I have already taken into account an amount of 170 hours of labbing. Still need to practise to grow up this count .
Will try to follow up more 🙂
Sometimes , when you defined your mgcp config and before to activate it with the CUCM config. You can experience issue where you can not send or receive calls on this gateway only because your link is not up.
This is caused because the binding between the MGCP gateway and the CUCM is not properly set up. So in order to fix this issue under your serial interface , remove the command isdn bind-l3 ccm-manager and put it again just after. The result is direct and your PSTN will go up .
Even if now you can edit and save directly your script in the right depository on the server ( a big advantage). It is still MANDATORY to refresh the script under the appadmin page.