Everyone keeps talking about "call disconnection" issues, but I have a bit of a call connection issue.
I have a CISCO 2811 with a 4 port FXO card and this is connected to a Windows server running FreeSWITCH PBX. I wrote a program which triggers FreeSWITCH to make an outgoing call to my desk phone. My phone rings, but as soon as I pick up the CISCO does not "see" that I picked up. Here is the strange thing:
as soon as I make a loud noise (whisle or snap my fingers) into the receiver it suddenly connects and the FreeSWITCH IVR starts playing.
In other words the "200 OK" sip message is not sent to FreeSWITCH until it "hears" a noise coming through the line...
My question is ... what the hell? lol
My voice port is configured as shown:
supervisory disconnect dualtone pre-connect
supervisory answer dualtone
output attenuation -3
timeouts call-disconnect 5
timeouts wait-release 5
I tried battery reversal, but that doesn't work. What happens if I use "battery-reversal answer" is is that the CISCO sends a "200 OK" message right away and does not even wait for me to pick up my ringing phone.
Please see link below where I was trying to solve the problem.
I can try to play with it, but why should it matter if someone skeaks or not?? That's what I don't get...
The problem is that because it's an automated IVR outgoing call, if someone sees the number on their phone/mobile they will just listen and not say anything so there may not be any user voice and the call won't get answered. I mean I can tell them: "If you see this number, make sure you say hi to the nice text-to-speech lady, otherwise she won't talk." Not exactly a neat solution...
Is this by design or why does there need to be audio down the line before the CISCO tells FreeSWITCH that the phone has been picked up?
I've just read things about grounding the chassis properly and polariy all those sorts of things, so I'll go to site tomorrow and have a look, but I don't know if that's related to this problem.
Besides tweaking output attenuation on port, did you try tweaking " input gain " values ? Increasing it might result in amplification of user voice & serve the purpose ( which is done by your whistle now ).
Using FXO, the only mean to know if a phone is being answered or not, is by tone monitoring, because telco does not sent signalling information on analog lines. Better said, they could using "battery-reversal", but few if any telco of the world actually support that.
So, the only way to detect if a phone has been answered or not, isusing some sort tone detection, that apparently the router is doing. In addition, the router also need to detect if a max or modem has answered the call, to switch to appropriate fax or modem relay modes.
You can try disabling fax relay, but the only reliable way to have answer confirmation, is using ISDN or SIP trunks, not FXO.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.