diff options
| author | dvossel <dvossel@f38db490-d61c-443f-a65b-d21fe96a405b> | 2009-10-21 22:02:01 +0000 |
|---|---|---|
| committer | dvossel <dvossel@f38db490-d61c-443f-a65b-d21fe96a405b> | 2009-10-21 22:02:01 +0000 |
| commit | 6a858d35cc15d74cd74bd123151018d30f3b4f7f (patch) | |
| tree | 7b316d61c7afcf64a2712f5ee42d317b396bb0f6 /include | |
| parent | 4884019de5a71670116137354145f0c7661df513 (diff) | |
Merged revisions 225307 via svnmerge from
https://origsvn.digium.com/svn/asterisk/trunk
................
r225307 | dvossel | 2009-10-21 16:58:46 -0500 (Wed, 21 Oct 2009) | 20 lines
Merged revisions 225243 via svnmerge from
https://origsvn.digium.com/svn/asterisk/branches/1.4
........
r225243 | dvossel | 2009-10-21 15:58:08 -0500 (Wed, 21 Oct 2009) | 13 lines
IAX2: VNAK loop caused by signaling frames with no destination call number
It is possible for the PBX thread to queue up signaling frames before
a destination call number is received. This can result in signaling
frames being sent out with no destination call number. Since recent
versions of Asterisk require accurate destination callnumbers for all
Full Frames, this can cause a VNAK loop to occur. To resolve this
no signaling frames are sent until a destination callnumber is received,
and destination call numbers are now only required for iax_pvt matching
when the frame is an ACK.
Review: https://reviewboard.asterisk.org/r/413/
........
................
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.6.1@225309 f38db490-d61c-443f-a65b-d21fe96a405b
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions