[SIP Beyond VoIP] Debugging DTMF for conference bridge app

Saúl Ibarra Corretgé saul at ag-projects.com
Fri Dec 27 09:08:37 CET 2013


Hi Jason,

On Dec 25, 2013, at 6:41 PM, Jason Ostrom <jpo at pobox.com> wrote:

> Hi Saúl,
> 
> Hope everyone on the list and you are having Merry Christmas or Happy Holidays.
> 

Merry xmas to you too!

> Rather than try to verify the observer add correctly, I just started with troubleshooting why the 'sip-session' sample sipclients app is not receiving the DTMF with SIP Simple 1.0.0 code running on Debian Wheezy x64 using apt-get from repos.
> 
> I tried doing the debug / trace you mention below.  Here is what I found:
> 
> With --trace-notifications:
> When I dial into conference bridge and hit DTMF from another phone, nothing prints to stdout.  In the line in the code, this line should be printing a notice, to either stdout or wherever logging is happening:  " send_notice('Got DMTF %s' % notification.data.digit)"
> Question:  Does logging by default go to stdout or to a logfile?  There is a chance I'm not seeing anything on stdout because logging is going to a file that I don't know where yet.
> 

The send_notice function will print a message on the screen, stdout.

> 
> With PJSIP logging (--trace-pjsip):
> 
> Very interesting, I'm getting messages to stdout that indicate bad RTP.  Every DTMF dialed gets a lot of stdout messages, exactly like this with bad pointer?  Look at this:
> 
> 
> (5) 2013-12-25 17:38:00.201  strm0x40559c8 RTP status: badpt=-1, badssrc=0, dup=0, outorder=0, probation=0, restart=0
> (4) 2013-12-25 17:38:00.201  strm0x40559c8 Bad RTP pt 101 (expecting 0)
> (5) 2013-12-25 17:38:00.201  strm0x40559c8 RTP status: badpt=-1, badssrc=0, dup=0, outorder=0, probation=0, restart=0
> (4) 2013-12-25 17:38:00.201  strm0x40559c8 Bad RTP pt 101 (expecting 0)
> (5) 2013-12-25 17:38:00.204  strm0x40559c8 RTP status: badpt=-1, badssrc=0, dup=0, outorder=0, probation=0, restart=0
> (4) 2013-12-25 17:38:00.204  strm0x40559c8 Bad RTP pt 101 (expecting 0)
> (5) 2013-12-25 17:38:00.220  strm0x40559c8 Jitter buffer empty (prefetch=0), plc invoked
> (5) 2013-12-25 17:38:00.225  strm0x40559c8 RTP status: badpt=-1, badssrc=0, dup=0, outorder=0, probation=0, restart=0
> (4) 2013-12-25 17:38:00.225  strm0x40559c8 Bad RTP pt 101 (expecting 0)
> (5) 2013-12-25 17:38:00.244  strm0x40559c8 RTP status: badpt=-1, badssrc=0, dup=0, outorder=0, probation=0, restart=0
> (4) 2013-12-25 17:38:00.244  strm0x40559c8 Bad RTP pt 101 (expecting 0)
> (5) 2013-12-25 17:38:00.265  strm0x40559c8 RTP status: badpt=-1, badssrc=0, dup=0, outorder=0, probation=0, restart=0
> (4) 2013-12-25 17:38:00.265  strm0x40559c8 Bad RTP pt 101 (expecting 0)
> (5) 2013-12-25 17:38:00.285  strm0x40559c8 RTP status: badpt=-1, badssrc=0, dup=0, outorder=0, probation=0, restart=0
> (4) 2013-12-25 17:38:00.285  strm0x40559c8 Bad RTP pt 101 (expecting 0)
> (5) 2013-12-25 17:38:00.304  strm0x40559c8 RTP status: badpt=-1, badssrc=0, dup=0, outorder=0, probation=0, restart=0
> (4) 2013-12-25 17:38:00.304  strm0x40559c8 Bad RTP pt 101 (expecting 0)
> (5) 2013-12-25 17:38:00.324  strm0x40559c8 RTP status: badpt=-1, badssrc=0, dup=0, outorder=0, probation=0, restart=0
> (4) 2013-12-25 17:38:00.324  strm0x40559c8 Bad RTP pt 101 (expecting 0)
> (5) 2013-12-25 17:38:00.344  strm0x40559c8 RTP status: badpt=-1, badssrc=0, dup=0, outorder=0, probation=0, restart=0
> (4) 2013-12-25 17:38:00.344  strm0x40559c8 Bad RTP pt 101 (expecting 0)
> (5) 2013-12-25 17:38:00.361  strm0x40559c8 RTP status: badpt=-1, badssrc=0, dup=0, outorder=0, probation=0, restart=0
> (4) 2013-12-25 17:38:00.361  strm0x40559c8 Bad RTP pt 101 (expecting 0)
> (5) 2013-12-25 17:38:00.361  strm0x40559c8 RTP status: badpt=-1, badssrc=0, dup=0, outorder=0, probation=0, restart=0
> (4) 2013-12-25 17:38:00.361  strm0x40559c8 Bad RTP pt 101 (expecting 0)
> (5) 2013-12-25 17:38:00.361  strm0x40559c8 RTP status: badpt=-1, badssrc=0, dup=0, outorder=0, probation=0, restart=0
> (4) 2013-12-25 17:38:00.361  strm0x40559c8 Bad RTP pt 101 (expecting 0)
> 
> How should I proceed further in trying to resolve this?  Looks like a bug with PJSIP or something like that?  Please help.
> 

Hum, interesting. Looks like DTMF is received but it's not processed because it wasn't expected. Can you attach the SIP trace for that call?


Regards,

--
Saúl Ibarra Corretgé
AG Projects





More information about the SIPBeyondVoIP mailing list