Displaying 20 results from an estimated 5000 matches similar to: "ast_rtp_read: Unknown RTP codec 72 received"
2004 Jul 26
0
rtp.c:487 ast_rtp_read: Unknown RTP codec 72 received
After just having update to the latest CVS I am getting the following
message when I call VoicemailMain():
-- Executing VoiceMailMain("SIP/2302-1a12", "") in new stack
-- Playing 'vm-login' (language 'en')
-- Playing 'vm-password' (language 'en')
-- Playing 'vm-youhave' (language 'en')
-- Playing
2004 Jun 02
0
ast_rtp_read: Unknown RTP codec
Any one see these? Are they benign, or is some system tuning required
to remove them?
Can't seem to find a resolution in the archives. If you have a link, it
would be appreciated.
Jun 2 10:58:58 NOTICE[163044272]: rtp.c:470 ast_rtp_read: Unknown RTP
codec 19 received
Jun 2 10:58:59 NOTICE[163044272]: rtp.c:470 ast_rtp_read: Unknown RTP
codec 72 received
Jun 2 10:59:00 NOTICE[163044272]:
2003 Nov 03
0
NOTICE[16401]: File rtp.c, Line 417 (ast_rtp_read): Unknown RTP codec 72 received
the above-message keep popping up every second during a conversation
between a
zap(fxs) channel and sip channel.
* eventually hung after a long while
we can talk to each other and we can ring one another without any problem.
i've had x-lite and x-pro register with * without this problem.
furthermore, i have ask my friend to turn off all codec expect
g.711MLAW; that did not help
i then
2005 Jun 29
0
ast_rtp_read: Unknown RTP codec 100 received21 when receiving fax
I'm testing NVBackgroundDetect with Sipura-300 and I get this error:
rtp.c:505 ast_rtp_read: Unknown RTP codec 100 received21
Does anybody know what is it?
--
#Joseph
2004 Sep 13
4
Unknown RTP codec 72 received
Hi all,
I get "Unknown RTP codec 72 received" message in console when call in
progress, but all seems OK. Calls is from X-Lite SIP softphone to PSTN
over voicepulse connect (IAX) and to FWD echo test (SIP). But this
message only with one SIP client, others (X-Lite too) not giving this
message. All X-Lite settings are identical. Asterisk is last cvs version
This what I see in console
2003 Apr 17
1
Unknown RTP codec 101 received
I updated to the latest CVS tonight and now DTMF
detection does not appear to work on my Cisco 7960 sip
phones (can't check voice mail etc). The asterisk
console is displaying these messages over and over
again any time a DTMF tone is sent:
NOTICE[15376]: File rtp.c, Line 292 (ast_rtp_read):
Unknown RTP codec 101 received
Downgraded to a known working CVS of about three weeks
ago, and
2006 Feb 25
2
Unknown RTP codec 100 received
Hi all!
I am frustrated.
I am new to asterisk. My system is ASTLINUX
if receive a Fax on my sipura spa2000
i get this: Feb 25 07:41:00 NOTICE[1708]: rtp.c:564 ast_rtp_read: Unknown RTP codec 100 received
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20060225/ca251876/attachment.htm
2003 Jul 31
1
RTP codec 13 received - Cisco incompatibility?
Hello,
In our SIP network, Asterisk is the central PBX, and it routes calls to the
PSTN thru a Cisco Router - IOS 12.2(11)T9.
If a client softphone calls directly via Cisco to the PSTN, the call works
successfully.
If the client softphone calls via Asterisk to other SIP internal extension,
it work fine too.
The problem is when a client calls an Asterisk extension, and Asterisk
transfers
2006 Jun 03
1
Asterisk 1.2.8 - WARNING[28769]: rtp.c:500 ast_rtp_read: Forcing Marker bit, because SSRC has changed
While sending calls to a SIP provider, the following warning generates:
-- Executing Dial("SIP/1000-c317",
"SIP/13057671523@209.120.202.94:5060|55|o") in new stack
-- Called 13057671523@209.120.202.94:5060
-- SIP/209.120.202.94:5060-0533 is making progress passing it to
SIP/1000-c317
-- SIP/209.120.202.94:5060-0533 answered SIP/1000-c317
-- Attempting
2003 Jul 31
1
RTP codec 13 received - Cisco incompatibilit y?
I have a similar setup to you and get the same message regularly. I don't
think it's the cause of your problem. I did some research on it a while ago:
IIRC the cisco uses codec 13 for "silence suppression" whereas asterisk
(correctly) uses codec 19. The router can be configured to use 19 also, but
I didn't bother. I'm sure somebody will correct me if I'm wrong about
2009 Jul 14
1
unknown RTP codec 126 ??
could anyone help explaining what does this error mean?
i get this error when make a video/ audio call from X-lite to Bria prof. phone
rtp.c:1739 ast_rtp_read: Unknown RTP codec 126 received from '10.0.0.26'
Gres
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
2004 Jan 22
0
Rtp WARNING Messages on the Cli in safe_asterisk
Hello All,
Has anyone ever seen this before. This only happens when i'm on phone
call
-- Zap/2-1 is ringing
-- SIP/2203-c48d is ringing
-- SIP/2202-f2ad is ringing
-- SIP/2204-11cd is ringing
-- SIP/2205-ce62 is ringing
-- Zap/2-1 is ringing
-- Zap/2-1 is ringing
-- Zap/2-1 is ringing
-- SIP/2205-ce62 answered Zap/1-1
-- Hungup 'Zap/2-1'
Jan
2003 Jun 04
5
RTP codec error???
When I make a call using sip, I get the line
NOTICE[327696]: File rtp.c, Line 292 (ast_rtp_read): Unknown RTP codec
19 received
Repeated many times on the console
; SIP Configuration for Asterisk
;
[general]
port = 5060 ; Port to bind to
;bindaddr = 0.0.0.0 ; Address to bind to
context = outgoing ; Default for incoming calls
allow=gsm
allow=ulaw
2004 Jul 09
1
RE: ATA 186, firmware SIP 3.1 and codec g.726 + now SIPURA SPA-2000
To me it's a error if I can't complete calls using the ATA configured to use
the g726 codec.
I just tried it usign a sipura SPA-2000 (preferred codec: G726-32) and I
received NOTICES and WARNINGS, but I can't complete a call.
On a zap channel:
-- Executing Dial("SIP/2007-e4d8", "Zap/1/2217008") in new stack
-- Called 1/2217008
-- Zap/1-1 answered
2007 Apr 23
1
app_rxfax produces "RTP: Received packet with bad UDP checksum"
I have tried to set up app_rxfax to receive faxes over IP. I realise
there are mixed stories about how reliable this is at the best of times,
but at this point all I'm after is some guidance in interpreting the log
below. What does "RTP: Received packet with bad UDP checksum" suggest?
Here is the full log:
-- Executing SetVar("SIP/0892130888-b27c",
2004 Aug 19
1
Received packet with bad UDP checksum
I was just on 70minute call (IAX2 -> Internet -> IAX2) and during that
time I heard several "pops", or "clicks". Each time it happened, I saw
the following message:
Aug 19 15:36:36 NOTICE[1173711792]: rtp.c:429 ast_rtp_read: RTP:
Received packet with bad UDP checksum
Any ideas what causes these, and why they turn in to a "pop", instead of
just silence, or a
2005 May 05
1
unknown RTP codec 72
can anyone tell what is the "unknown RTP codec 72" means and how to fix it.
I'm using xlite to call PSTN line and the message just pop up on my console but the call can be connected. What am I going to do?
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
-------------- next
2011 Dec 01
1
Hlink node data for 570645 already has path ...
When syncing one backup system (running dirvish, but that's not really
relevant) to a second long-term backup system which uses btrfs
snapshots, I get the following output:
rsync: link "/parasite.oob.telegraaf.net/vservers-var-www/tree/elo/var/www/lokaalx/openx-htdocs/etc/xmlcache/.svn/prop-base/cache_etc-changes_schema-tables-core-12934.bin.svn-base" (in backup-aquagirl) =>
2007 Mar 12
2
Parasite and camping_generator 0.2.0
Announcing the the 0.2.0 release of parasite and the camping_generator.
Parasite (from the project page -- http://parasite.rubyforge.org/):
Camping app developers no longer have any reason to envy their Ruby on
Rails friends: Parasite brings generators, environments, and other
Rails-y goodness to the world of Camping app development.
Parasite is currently at version 0.2. The Parasite package is
2010 Oct 07
1
RTP Read too short
Hi All
In the console I am seeing warring rtp.c:1635 ast_rtp_read: RTP Read too
short
I get these all of the time things seem to be working fine but I am trying
to figure out if there is a way to resolve these Warnings.
I am running asterisk 1.6.2.13
Any direction is appreciated.
Thanks
Bryant
-------------- next part --------------
An HTML attachment was scrubbed...
URL: