[asterisk-bugs] [Asterisk 0011532]: sip_poke_noanswer; peer in now unreachable

[noreply at bugs.digium.com]

The following issue has been RESOLVED. 
====================================================================== 
http://bugs.digium.com/view.php?id=11532 
====================================================================== 
Reported By:                vision_admin
Assigned To:                qwell
====================================================================== 
Project:                    Asterisk
Issue ID:                   11532
Category:                   . I did not set the category correctly.
Reproducibility:            always
Severity:                   crash
Priority:                   normal
Status:                     resolved
Asterisk Version:            1.4.14  
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
Resolution:                 fixed
Fixed in Version:           
====================================================================== 
Date Submitted:             12-12-2007 16:14 CST
Last Modified:              12-12-2007 16:22 CST
====================================================================== 
Summary:                    sip_poke_noanswer; peer in now unreachable
Description: 
The Asterisk Server, grandstream budgetone, analog phone and x-lite is all
behind NAT.  The extensions.conf and sip.conf were altered to accept the
new changes and intially it all worked.  

Rebooted the server and received the following:

sip_poke_noanswer peer in now unreachable.  

Changed quality and it is still not working.  This is a direct sip to sip
phone call.

Any suggestions would greatly be appreciated


====================================================================== 

---------------------------------------------------------------------- 
 qwell - 12-12-07 16:22  
---------------------------------------------------------------------- 
This is not a configuration help forum.  Any changes that were made
recently are clearly causing this problem.

If you are able to show that this is in fact a bug, please reopen this
report and show us the configuration options that are causing incorrect
behavior. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
12-12-07 16:22  qwell          Status                   new => resolved     
12-12-07 16:22  qwell          Resolution               open => fixed       
12-12-07 16:22  qwell          Assigned To               => qwell           
12-12-07 16:22  qwell          Note Added: 0075310                          
======================================================================