[asterisk-bugs] [Asterisk 0018129]: [patch] Oneway audio from SIP phone to FXS port after FXS port gets a CallWaiting pip

Asterisk Bug Tracker noreply at bugs.digium.com
Tue Oct 19 05:25:18 CDT 2010


A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=18129 
====================================================================== 
Reported By:                alecdavis
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   18129
Category:                   Channels/General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           SVN 
JIRA:                       SWP-2367 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!): 290865 
Request Review:              
====================================================================== 
Date Submitted:             2010-10-13 04:31 CDT
Last Modified:              2010-10-19 05:25 CDT
====================================================================== 
Summary:                    [patch] Oneway audio from SIP phone to FXS port
after FXS port gets a CallWaiting pip
Description: 
Internal SIP phone initiates a call with FXS port on TDM800P.

External call comes in on FXO port, and attempts to ring FXS ports.
Call waiting beep is heard at FXS port, also no outbound audio to SIP
phone.

Then FXS port hook flashes, the FXO port is then connected to FXS as
expected.
But SIP device should hear MOH, but has dead air.

If the FXS port hook flashes to the SIP device, the FXO call then does
hear MOH.
Hook flash again back to FXO call, SIP hears nothing.  
====================================================================== 

---------------------------------------------------------------------- 
 (0128189) alecdavis (manager) - 2010-10-19 05:25
 https://issues.asterisk.org/view.php?id=18129#c128189 
---------------------------------------------------------------------- 
Example console output: with rtp debug on

Got  RTP packet from    192.168.124.250:35010 (type 00, seq 001895, ts
3309220, len 000160)
Sent RTP packet to      192.168.124.250:35010 (type 00, seq 043324, ts
080480, len 000160)
Got  RTP packet from    192.168.124.250:35010 (type 00, seq 001896, ts
3309380, len 000160)
Sent RTP packet to      192.168.124.250:35010 (type 00, seq 043325, ts
080640, len 000160)
asterix*CLI> console dial 89 at phones
[2010-10-19 23:21:47.024338] WARNING[21102]: chan_oss.c:486 setformat:
Unable to re-open DSP device /dev/dsp: No such file or directory
[2010-10-19 23:21:47.024949] NOTICE[21102]: console_video.c:133
console_video_start: voice only, console video support not present
    -- Executing [89 at phones:1] Dial("Console/dsp", "DAHDI/35,60") in new
stack
Got  RTP packet from    192.168.124.250:35010 (type 00, seq 001897, ts
3309540, len 000160)
    -- Called 35
Got  RTP packet from    192.168.124.250:35010 (type 00, seq 001898, ts
3309700, len 000160)
    -- DAHDI/35-2 is ringing
Sent RTP packet to      192.168.124.250:35010 (type 00, seq 043326, ts
080800, len 000160)
Got  RTP packet from    192.168.124.250:35010 (type 00, seq 001899, ts
3309860, len 000160)
...
Sent RTP packet to      192.168.124.250:35010 (type 00, seq 043347, ts
084160, len 000160)
Got  RTP packet from    192.168.124.250:35010 (type 00, seq 001920, ts
3313220, len 000160)
Sent RTP packet to      192.168.124.250:35010 (type 00, seq 043348, ts
084320, len 000160)
Got  RTP packet from    192.168.124.250:35010 (type 00, seq 001921, ts
3313380, len 000160)
<B>Sent RTP DTMF packet to 192.168.124.250:35010 (type 101, seq 043349, ts
084480, len 000004)
Sent RTP DTMF packet to 192.168.124.250:35010 (type 101, seq 043350, ts
084480, len 000004)
Sent RTP DTMF packet to 192.168.124.250:35010 (type 101, seq 043351, ts
084480, len 000004)
Got  RTP packet from    192.168.124.250:35010 (type 00, seq 001922, ts
3313540, len 000160)
Sent RTP DTMF packet to 192.168.124.250:35010 (type 101, seq 043352, ts
084480, len 000004)
Got  RTP packet from    192.168.124.250:35010 (type 00, seq 001923, ts
3313700, len 000160)
Sent RTP DTMF packet to 192.168.124.250:35010 (type 101, seq 043353, ts
084480, len 000004)
Got  RTP packet from    192.168.124.250:35010 (type 00, seq 001924, ts
3313860, len 000160)
Sent RTP DTMF packet to 192.168.124.250:35010 (type 101, seq 043354, ts
084480, len 000004)
Got  RTP packet from    192.168.124.250:35010 (type 00, seq 001925, ts
3314020, len 000160)
    -- CPE supports Call Waiting Caller*ID.  Sending '/'
Sent RTP DTMF packet to 192.168.124.250:35010 (type 101, seq 043355, ts
084480, len 000004)
Got  RTP packet from    192.168.124.250:35010 (type 00, seq 001926, ts
3314180, len 000160)
Sent RTP DTMF packet to 192.168.124.250:35010 (type 101, seq 043356, ts
084480, len 000004)
Got  RTP packet from    192.168.124.250:35010 (type 00, seq 001927, ts
3314340, len 000160)
Sent RTP DTMF packet to 192.168.124.250:35010 (type 101, seq 043357, ts
084480, len 000004)
Got  RTP packet from    192.168.124.250:35010 (type 00, seq 001928, ts
3314500, len 000160)
Sent RTP DTMF packet to 192.168.124.250:35010 (type 101, seq 043358, ts
084480, len 000004)
Got  RTP packet from    192.168.124.250:35010 (type 00, seq 001929, ts
3314660, len 000160)
Sent RTP DTMF packet to 192.168.124.250:35010 (type 101, seq 043359, ts
084480, len 000004)</B> 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-10-19 05:25 alecdavis      Note Added: 0128189                          
======================================================================




More information about the asterisk-bugs mailing list