Expert Needed - Call deteriorates after 2 mins in

daschenbrener

Joined
Aug 11, 2010
Messages
35
Likes
0
Points
0
#21
Here is a small cut from the log, and if you could take a look at the sequence, does it look off?

[Sep 11 14:16:05] VERBOSE[3441] rtp.c: Got RTP packet from 64.34.49.90:14702 (type 00, seq 048608, ts 653600, len 000160)
[Sep 11 14:16:05] VERBOSE[3441] rtp.c: Sent RTP packet to 192.168.0.13:10010 (type 09, seq 029262, ts 653600, len 000160)
[Sep 11 14:16:05] VERBOSE[3441] rtp.c: Got RTP packet from 192.168.0.13:10010 (type 09, seq 011325, ts 1075222184, len 000160)
[Sep 11 14:16:05] VERBOSE[3441] rtp.c: Sent RTP packet to 64.34.49.90:14702 (type 00, seq 030858, ts 1075222184, len 000160)
[Sep 11 14:16:05] VERBOSE[3441] rtp.c: Got RTP packet from 64.34.49.90:14702 (type 00, seq 048609, ts 653760, len 000160)
[Sep 11 14:16:05] VERBOSE[3441] rtp.c: Sent RTP packet to 192.168.0.13:10010 (type 09, seq 029263, ts 653760, len 000160)
[Sep 11 14:16:05] VERBOSE[3441] rtp.c: Got RTP packet from 192.168.0.13:10010 (type 09, seq 011326, ts 1075222344, len 000160)
[Sep 11 14:16:05] VERBOSE[3441] rtp.c: Sent RTP packet to 64.34.49.90:14702 (type 00, seq 030859, ts 1075222344, len 000160)
[Sep 11 14:16:05] VERBOSE[3441] rtp.c: Got RTP packet from 64.34.49.90:14702 (type 00, seq 048610, ts 653920, len 000160)
[Sep 11 14:16:05] VERBOSE[3441] rtp.c: Sent RTP packet to 192.168.0.13:10010 (type 09, seq 029264, ts 653920, len 000160)
[Sep 11 14:16:05] VERBOSE[3441] rtp.c: Got RTP packet from 192.168.0.13:10010 (type 09, seq 011327, ts 1075222504, len 000160)
[Sep 11 14:16:05] VERBOSE[3441] rtp.c: Sent RTP packet to 64.34.49.90:14702 (type 00, seq 030860, ts 1075222504, len 000160)
[Sep 11 14:16:05] VERBOSE[3441] rtp.c: Got RTP packet from 64.34.49.90:14702 (type 00, seq 048611, ts 654080, len 000160)
[Sep 11 14:16:05] VERBOSE[3441] rtp.c: Sent RTP packet to 192.168.0.13:10010 (type 09, seq 029265, ts 654080, len 000160)
[Sep 11 14:16:05] VERBOSE[3441] rtp.c: Got RTP packet from 192.168.0.13:10010 (type 09, seq 011328, ts 1075222664, len 000160)
[Sep 11 14:16:05] VERBOSE[3441] rtp.c: Sent RTP packet to 64.34.49.90:14702 (type 00, seq 030861, ts 1075222664, len 000160)
[Sep 11 14:16:05] VERBOSE[3441] rtp.c: Got RTP packet from 64.34.49.90:14702 (type 00, seq 048612, ts 654240, len 000160)
[Sep 11 14:16:05] VERBOSE[3441] rtp.c: Sent RTP packet to 192.168.0.13:10010 (type 09, seq 029266, ts 654240, len 000160)
[Sep 11 14:16:05] VERBOSE[3441] rtp.c: Got RTP packet from 192.168.0.13:10010 (type 09, seq 011329, ts 1075222824, len 000160)
[Sep 11 14:16:05] VERBOSE[3441] rtp.c: Sent RTP packet to 64.34.49.90:14702 (type 00, seq 030862, ts 1075222824, len 000160)
[Sep 11 14:16:05] VERBOSE[3441] rtp.c: Got RTP packet from 64.34.49.90:14702 (type 00, seq 048613, ts 654400, len 000160)
[Sep 11 14:16:05] VERBOSE[3441] rtp.c: Sent RTP packet to 192.168.0.13:10010 (type 09, seq 029267, ts 654400, len 000160)
[Sep 11 14:16:05] VERBOSE[3441] rtp.c: Got RTP packet from 64.34.49.90:14702 (type 00, seq 048614, ts 654560, len 000160)
[Sep 11 14:16:05] VERBOSE[3441] rtp.c: Sent RTP packet to 192.168.0.13:10010 (type 09, seq 029268, ts 654560, len 000160)
[Sep 11 14:16:05] VERBOSE[3441] rtp.c: Got RTP packet from 64.34.49.90:14702 (type 00, seq 048615, ts 654720, len 000160)
[Sep 11 14:16:05] VERBOSE[3441] rtp.c: Sent RTP packet to 192.168.0.13:10010 (type 09, seq 029269, ts 654720, len 000160)
[Sep 11 14:16:05] VERBOSE[3441] rtp.c: Got RTP packet from 64.34.49.90:14702 (type 00, seq 048616, ts 654880, len 000160)
[Sep 11 14:16:05] VERBOSE[3441] rtp.c: Sent RTP packet to 192.168.0.13:10010 (type 09, seq 029270, ts 654880, len 000160)
[Sep 11 14:16:05] VERBOSE[3441] rtp.c: Got RTP packet from 64.34.49.90:14702 (type 00, seq 048617, ts 655040, len 000160)
[Sep 11 14:16:05] VERBOSE[3441] rtp.c: Sent RTP packet to 192.168.0.13:10010 (type 09, seq 029271, ts 655040, len 000160)
[Sep 11 14:16:05] VERBOSE[3441] rtp.c: Got RTP packet from 64.34.49.90:14702 (type 00, seq 048618, ts 655200, len 000160)
[Sep 11 14:16:05] VERBOSE[3441] rtp.c: Sent RTP packet to 192.168.0.13:10010 (type 09, seq 029272, ts 655200, len 000160)
[Sep 11 14:16:05] VERBOSE[3441] rtp.c: Got RTP packet from 64.34.49.90:14702 (type 00, seq 048619, ts 655360, len 000160)
[Sep 11 14:16:05] VERBOSE[3441] rtp.c: Sent RTP packet to 192.168.0.13:10010 (type 09, seq 029273, ts 655360, len 000160)

Thanks
 

andyshawn

Joined
Apr 3, 2009
Messages
113
Likes
0
Points
0
#22
Based on my analysis of your logs and what Dicko said earlier, you should not be experiencing bad voice quality.
All your RTP packets are being acknowledge immediately and ontime. Dicko, kindly correct me if i am wrong?

Was this log taken during the time you started experiencing poor voice quality?
 

dicko

Joined
Oct 24, 2008
Messages
4,099
Likes
0
Points
0
#23
yes, that two second snip showed normal, on two legs, leave the debug on and from bash try:-

tail -f /var/log/asterisk/full|grep 64.34.49.90 |tee -a /root/stupidisp.log

to isolate the Netfone Services Inc traffic. and isolate to a logfile for later proof.

the normal ctrl-s/ctrl-q to examine when the problem raises it's head, the seq field is just an incrementing counter, so you should be able to figure that out yourself.
 

daschenbrener

Joined
Aug 11, 2010
Messages
35
Likes
0
Points
0
#24
I am getting this in the debug

[Sep 11 21:19:59] DEBUG[6174] chan_sip.c: Target address 64.34.49.90 is not local, substituting externip
[Sep 11 21:20:29] DEBUG[2971] chan_sip.c: Target address 64.34.49.90 is not local, substituting externip
[Sep 11 21:20:29] DEBUG[2971] chan_sip.c: Allocating new SIP dialog for 61d2de332556250b4c27c6e675863267@64.34.49.90 - OPTIONS (No RTP)
 

daschenbrener

Joined
Aug 11, 2010
Messages
35
Likes
0
Points
0
#25
i truly am stumped on this one. If someone want to get paid to track this one down, please let me know and how much.
 

dicko

Joined
Oct 24, 2008
Messages
4,099
Likes
0
Points
0
#26
That is SIP signaling, it's really nothing to with audio payload (rtp) different protocol, different connection socket , if you want's to learn about SIP and how the externip etc work, then start with http://voip-info.org

(actually that isIMHO good advice if you want to learn anything about VOIP)
 

dicko

Joined
Oct 24, 2008
Messages
4,099
Likes
0
Points
0
#27
I'll do it for free, if you will just do as I ask, why is it so hard to do that?

PaloSanto have a paid support option at the top of this page.
 

daschenbrener

Joined
Aug 11, 2010
Messages
35
Likes
0
Points
0
#28
No problem. Let me know what I should do and I will do it.
 

dicko

Joined
Oct 24, 2008
Messages
4,099
Likes
0
Points
0
#29
after an event is well captured then get out of the realtim e monitoring with a ctrl-c and:

sed -n 1~2p /root/stupidisp.log|less

this will print out every other line (through less, (a pager)) , as there will normally be sent/got/sent/got/sent etc any change will generally indicate a missed or asynchronous packet or three (not two), an occasional slip can be expected, but statistics are on your side here , and find a point in time (presumably coincidental with the problem) where that is noticed, the more disruption here the better it will be indicative of when things started to "FU", when you find one of those "points in time" post it back here.
 

Members online

No members online now.

Latest posts

Forum statistics

Threads
30,981
Messages
131,060
Members
17,700
Latest member
neonakris
Top