[asterisk-users] No reply to our critical packet

Lincoln King-Cliby lincoln at controlworks.com
Fri Mar 13 13:15:59 CDT 2009


I had this issue with SIP Phones (Cisco 7961) to local voicemail; the issue was resolved by adding a 

Ringing() followed by 
Wait(1) 

before the VoicemailMain() in the dial plan... it seems like there should be a better way, and I feel it's rather crude to force the user to listen to a second of ringback before launching into voicemail, but it solved the problem for me (and yes, I did try just Ringing() with no wait with no such luck)  -- maybe it would work in your case with a SIP call as well? 

HTH,

Lincoln 

-- 
Lincoln King-Cliby, CTS
Applications Engineer 
ControlWorks Consulting, LLC
V: 440.729.4640 x1107 | F: 440.729.0884 | I:http://www.thecontrolworks.com/ 
Crestron Authorized Independent Progammers

-----Original Message-----
From: asterisk-users-bounces at lists.digium.com [mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Roman Odaisky
Sent: Friday, March 13, 2009 11:38 AM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [asterisk-users] No reply to our critical packet

Hi,

thanks for the quick reply.

> 1. Do you have the incoming 10000-20000 holes in your firewall so the
> remote server can get it's reply back to *?

This was what I checked first. Both firewalls let everything through.

> 2. If #1 is ok, try putting an Answer command in front of your Dial
> Command.

Doesn't help, alas. Also, it works the same (disconnect after 20 seconds) both 
for Dial and Echo, regardless of presence of Answer.

-- 
TIA
Roman.



More information about the asterisk-users mailing list