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

[c3voip]

This is not a DTMF issue, this is a problem with Jabber where it doesn't
enable the keypad until it sees that the call is connected.

 

 

From: Kenneth Hayes [mailto:kennethwhayes at gmail.com] 
Sent: Wednesday, January 16, 2013 10:47 AM
To: c3voip
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Call not connecting, but it's connected

 

Sounds like a DTMF...check your profile and make sure your sending the right
audio codec to the telco.

Sent from my iPad


On Jan 16, 2013, at 10:33 AM, c3voip <c3voip at nc.rr.com> wrote:

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

_______________________________________________
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/20130116/8d17938b/attachment.html>