Hello,
I have a SIP trunk configured from CUCM to talk to a 3rd party service providing and IVR. When calls are placed across the SIP trunk I hear a double ring tone. I only get this when calling internally across the trunk, external calls I don'...
Hello,
Is there a way I can remove some of the Icons on the left hand side of the Jabber window. We are only using Jabber for phone only now and would like to remove the chat icon. I've had a look at the jabber config file but I can't see where i...
Hi,
Can anyone assist with this question please.
Currently all of our inbound calls are delivered over SIP trunk to CUBE using G711Mulaw. We have however recently installed a 3rd party IVR system that can only use g711Alaw.
Internally a call ...
When using Jabber to dial mobile numbers using prefix +447 the calls are failing. For example a call to +447742xxxxxx. A route pattern of \+44.! is used to dicard predot and add 90 to the number, to make the call route externally (907742xxxxxx) Wh...
Hi,
Does anyone know of an SQL query I can use that will show me agent states for a particular time and date? For example. I have an issue where a supervisor is saying callers are sat in the queue at a certain time queueing but all agents were lo...
To Clarify.Users were asked to make their windows AD account passwords more secure. In doing this some users used certain characters not recognised by Jabber. I believe the extended ASCII table characters were causing the problem (£, $ etc). Once u...
Hi,
No route pattern does not have the "provide outside dial tone" checked. The other side of the trunk is an IVR server. So the call flow is.
IP Phone ==> CUCM SIP trunk ===>3rd party server ===>Script DN. The DN in this case is 8272 which is ...
Hi,
I ran the following to run it in phone_only mode
msiexec.exe /i CiscoJabberSetup.msi CLEAR=1 PRODUCT_MODE=Phone_Mode TFTP=1.2.3.4 LANGUAGE=1033 /quiet
However even though it says in the jabber-bootstrap that it is in phone_only mode I still s...
Yes I did manage to find the reason after lots of googling! It was the AppDialRules.xml file located in the CUPC directory. There was an entry in there causing the problem!
<DialRule BeginsWith="+447" NumDigits="13" DigitsToRemove="2" PrefixWith="90...