[asterisk-users] Answered call not bridged

2010-07-28 Thread Ishfaq Malik
Hi I've suddenly started encountering a strange issue. Sometimes, when a call is made into our system, an extension answered the phone but I can see no mention of it being bridged in the console. Also, the server does not seem to think that it is answered and then goes to voicemail. We are

Re: [asterisk-users] Answered call not bridged

2010-07-28 Thread Gareth Blades
If you run a sip debug at the same time you will get some more usefull logs. What sip client are you using? Ishfaq Malik wrote: Hi I've suddenly started encountering a strange issue. Sometimes, when a call is made into our system, an extension answered the phone but I can see no mention

Re: [asterisk-users] Answered call not bridged

2010-07-28 Thread Zeeshan Zakaria
On receiving a call, try using the 'Answer()' command before anything else. I once had some issues, though not similar, which were solved by this command, as it sends back a SIP acknowledgement to the calling party which is otherwise not sent. Zeeshan A Zakaria -- www.ilovetovoip.com On

Re: [asterisk-users] Answered call not bridged

2010-07-28 Thread Ishfaq Malik
Hi The problem is that this is a production server with usually about 10 concurrent calls going on and also that if I just run a sip debug on the customers peer, I still don't know when it's either this issue or if it genuinely went to voicemail. That's why I'm trying to consistently

Re: [asterisk-users] Answered call not bridged

2010-07-28 Thread Ishfaq Malik
Hi Unfortunately this isn't an option as we allow customers to forward incoming calls back out to POTS or mobile. If we use an explicit Answer() all forwarded calls show as answered even if they weren't by the POTS or mobile end point. Ish On 28/07/10 11:48, Zeeshan Zakaria wrote: On

Re: [asterisk-users] Answered call not bridged

2010-07-28 Thread Philipp von Klitzing
Hi! - upgrade to a current 1.4 version, 1.4.17 is very old (you probably run this because of the zaptel -- dahdi change, but still) - do you have a SIP proxy or any SIP-aware hardware in your network that might play tricks on you, e.g. a SIP ALG (application layer gateway) on your Internet