[asterisk-bugs] [Asterisk 0012994]: Spamming CLI / logs with 'Remote host can't match request BYE to call...'

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12994 
====================================================================== 
Reported By:                pabelanger
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   12994
Category:                   Channels/chan_sip/General
Reproducibility:            random
Severity:                   minor
Priority:                   normal
Status:                     new
Asterisk Version:           1.6.0-beta9 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             07-04-2008 11:33 CDT
Last Modified:              07-04-2008 13:29 CDT
====================================================================== 
Summary:                    Spamming CLI / logs with 'Remote host can't match
request BYE to call...'
Description: 
Every 6/7 seconds, our cli is getting spammed (see below).

sip show channel 05b6e9a07669fa0c0a4d88a663b4a2bd at 192.168.20.2
---
  * SIP Call
  Curr. trans. direction:  Outgoing
  Call-ID:                05b6e9a07669fa0c0a4d88a663b4a2bd at 192.168.20.2
  Owner channel ID:       <none>
  Our Codec Capability:   6
  Non-Codec Capability (DTMF):   1
  Their Codec Capability:   4
  Joint Codec Capability:   4
  Format:                 0x0 (nothing)
  T.38 support            No
  Video support           No
  MaxCallBR:              384 kbps
  Theoretical Address:    192.168.20.3:5070
  Received Address:       192.168.20.4:5070
  SIP Transfer mode:      open
  NAT Support:            RFC3581
  Audio IP:               192.168.20.2 (local)
  Our Tag:                as643fb95e
  Their Tag:              as643fb95e
  SIP User agent:         RTCC/3.0.0.0
  Peername:               sv0071iv
  Original uri:           sip:sv0071iv.internal.xxx.on.ca:5070
  Need Destroy:           No
  Last Message:           Tx: BYE
  Promiscuous Redir:      No
  Route:                 
sip:sv0071iv.internal.xxx.on.ca:5070;transport=Tcp;maddr=192.168.20.3
  DTMF Mode:              rfc2833
  SIP Options:            (none)
  Session-Timer:          Inactive

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

---------------------------------------------------------------------- 
 pabelanger - 07-04-08 13:29  
---------------------------------------------------------------------- 
Some additional information around this bug.  It seems after I enabled sip
debug for the trace, then disabled it.  Some sip traces are still send to
the cli.

---
> sip set debug off
SIP Debugging Disabled
BYE sip:sv0071iv.xxx.veridian.on.ca:5070;transport=Tcp;maddr=192.168.20.3
SIP/2.0
Via: SIP/2.0/TCP 192.168.20.2:5060;branch=z9hG4bK0ebfa37b;rport
Max-Forwards: 70
From: <sip:sv0071iv.voice:5070>;epid=72981C2AB9;tag=a85ee012d6
To: <sip:asterisk at 192.168.20.2>;tag=as643fb95e
Call-ID: 05b6e9a07669fa0c0a4d88a663b4a2bd at 192.168.20.2
CSeq: 26848 BYE
User-Agent: Asterisk PBX 1.6.0-beta9
Content-Length: 0
---

We're now getting in the log files too:
---
WARNING[5484] chan_sip.c: sip_xmit of 0x48b7e5c (len 415) to
192.168.20.3:5070 returned -1 : Invalid argument

and

WARNING[5484] chan_sip.c: sip_xmit of 0x48b7e5c (len 415) to
192.168.20.3:5070 returned -2 : Bad file descriptor 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
07-04-08 13:29  pabelanger     Note Added: 0089755                          
======================================================================