[cisco-voip] Call not connecting, but it's connected

[Ryan Ratliff]

I reproduced this on our internal build of the Jabber Mac client and CSCue09571 ended up being filed.   It appears CUCM cut through the audio with a 183 Progress then sent a Subscribe to Jabber for kpml.  It doesn't look like Jabber ever responded to that Subscribe, my guess is because it didn't think the call was connected.

I think a TAC SR is a good place to start, getting customer cases attached to a bug (or even seeing if a separate bug is required for Jabber Windows) will help with getting the fix prioritized.

-Ryan

On Jan 21, 2013, at 1:59 PM, Eric Pedersen <PedersenE at bennettjones.com> wrote:

We call a different  company's toll-free number that does the same thing. In our case DTMF wasn't working at all, but that was with a SIP gateway. I did a bit of digging, and the remote end played their IVR and expected input after an ISDN PROGRESS, without ISDN CONNECT. From what I read ISDN PROGRESS is only for the other party to play a recording, not receive any audio, so the GW didn't consider the call set up and wouldn't send DTMF.  I got the DTMF working by changing the relay mechanism, but I just tried with Jabber and I experience the same problem as you do. 
 
Let me know if you get a bug ID and I'll open an SR on it so that it gets another hit.  IMO, it's the IVR that isn't configured properly but if it works calling from a cell phone, it should work from a Cisco device also.
 
I was wondering why they would start their IVR that way… you're probably right about it being toll avoidance.
 
Eric
 
From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of c3voip
Sent: 16 January 2013 7:53 AM
To: cisco-voip at puck.nether.net
Subject: [cisco-voip] Call not connecting, but it's connected
 
Hi,
 
So when we try to call McAfee Gold Support line at 1-800-937-2237, our call is immediately answered by an auto-attendant, but the PRI channel does not show as connected, so my phone does not show that the call is connected.  This is obviously some type of toll-charge avoidance.  I have tried calling from my cellphone and the behavior is the same…phone still displays “calling” even though the AA is connected.
 
My problem is with trying to use Jabber either to control a hard phone or using it as a soft phone, it cannot generate touch-tones to navigate the auto-attendant. In the case of the soft phone, the keypad never becomes available in the GUI and numbers on the keyboard do nothing.
 
Has anyone ever seen this and is there any way to get Jabber to work with these calls?
 
Thanks,
-Chase
The contents of this message may contain confidential and/or privileged
subject matter. If this message has been received in error, please contact
the sender and delete all copies. Like other forms of communication,
e-mail communications may be vulnerable to interception by unauthorized
parties. If you do not wish us to communicate with you by e-mail, please
notify us at your earliest convenience. In the absence of such
notification, your consent is assumed. Should you choose to allow us to
communicate by e-mail, we will not take any additional security measures
(such as encryption) unless specifically requested.

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20130122/141f813b/attachment.html>