Has this been reported upstream?

no, because my usptream is fedora and if i report every problem in every piece of software on my system upstream and register an account before i have a fulltime job with bugreporting and the feodra-bugzilla could be closed

in my opinion this is one of the jobs of a package maintainer since he maintains few packages and has hopefully and upstream bugzilla-account, the user has installed more than 1.000 packages

(In reply to comment #2)
> no, because my usptream is fedora and if i report every problem in every piece
> of software on my system upstream and register an account before i have a
> fulltime job with bugreporting and the feodra-bugzilla could be closed
> 
> in my opinion this is one of the jobs of a package maintainer since he
> maintains few packages and has hopefully and upstream bugzilla-account, the
> user has installed more than 1.000 packages

Yes, but (especially in this case) the bug may depend on specific hardware (Cisco phones with SIP images) and/or your particular configuration none of which I have access to.

And just because I only have a few packages to maintain that doesn't mean that I have all day to sit around and debug people's problems, or act as a messenger between the person experiencing the bug and the real upstream developers, especially ones in packages as complex as Asterisk.  I'm not paid by Red Hat to maintain these packages, in fact I'm not paid by anyone to maintain these packages.

You'd probably have a case if this was a package that was provided by Red Hat as an officially supported part of RHEL, but it's not.

you do not (want?) understand me

i receive 20 maling-lists, have 10 upstream-bugzilla accounts and 3 fulltime-jobs
so i have not the time to register me upstream on every bugzilla in this world
accept it or not

it told you that this package is broken
not more, not less
do what you want with this iformation 

i am able do blacklist it if you decide push it to stable and try the next one since the SIP port is only open to the upstream ISP and internal all phones are in a seperated physical net

BTW: 

the reason is that all newer releases are defaultig to "nat=yes"
if you specify "nat=no" for each peer it starts to work as before

This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping