[Home]

Summary:ASTERISK-02653: rtp.c error - unknown RTP codec 127 received
Reporter:duanecox (duanecox)Labels:
Date Opened:2004-10-22 09:57:33Date Closed:2011-06-07 14:10:17
Priority:MinorRegression?No
Status:Closed/CompleteComponents:Core/General
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:I'm not really sure what this is about.  I am using ULAW as me codec and SIP as the channel.

I get this error at every SIP hangup.

****** ADDITIONAL INFORMATION ******

   -- Zap/1-1 is ringing
   -- Zap/1-1 answered SIP/3790612-9ee2
We're at 192.168.228.202 port 11950
Answering with preferred capability 0x4(ULAW)
Reliably Transmitting (no NAT):
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.240.2:5060;branch=z9hG4bK24586
From: <sip:3790612@192.168.228.202>;tag=194800060d0f4fc7
To: <sip:3391040@192.168.228.202>;tag=as354b454b
Call-ID: 719300060d0f4fc7@192.168.240.2
CSeq: 20 INVITE
User-Agent: Asterisk PBX
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER
Contact: <sip:3391040@192.168.228.202>
Content-Type: application/sdp
Content-Length: 164

v=0
o=root 14809 14809 IN IP4 192.168.228.202
s=session
c=IN IP4 192.168.228.202
t=0 0
m=audio 11950 RTP/AVP 0
a=rtpmap:0 PCMU/8000
a=silenceSupp:off - - - -

to 192.168.240.2:5060
pbx1*CLI>

Sip read:
ACK sip:3391040@192.168.228.202 SIP/2.0
Via: SIP/2.0/UDP 192.168.240.2:5060;branch=z9hG4bK27185
From: <sip:3790612@192.168.228.202>;tag=194800060d0f4fc7
To: <sip:3391040@192.168.228.202>;tag=as354b454b
Call-ID: 719300060d0f4fc7@192.168.240.2
CSeq: 20 ACK
Max-Forwards: 70
User-Agent: Wave7-LMGR release(0.1)
Content-Length: 0


9 headers, 0 lines
   -- Registered to '69.73.19.178', who sees us as 192.168.228.202:4569
Oct 22 09:24:07 NOTICE[770065]: rtp.c:493 ast_rtp_read: Unknown RTP codec 127 received
Oct 22 09:24:07 NOTICE[770065]: rtp.c:493 ast_rtp_read: Unknown RTP codec 127 received
Oct 22 09:24:07 NOTICE[770065]: rtp.c:493 ast_rtp_read: Unknown RTP codec 127 received
Oct 22 09:24:07 NOTICE[770065]: rtp.c:493 ast_rtp_read: Unknown RTP codec 127 received
Oct 22 09:24:07 NOTICE[770065]: rtp.c:493 ast_rtp_read: Unknown RTP codec 127 received
Oct 22 09:24:07 NOTICE[770065]: rtp.c:493 ast_rtp_read: Unknown RTP codec 127 received
Oct 22 09:24:07 NOTICE[770065]: rtp.c:493 ast_rtp_read: Unknown RTP codec 127 received
Oct 22 09:24:07 NOTICE[770065]: rtp.c:493 ast_rtp_read: Unknown RTP codec 127 received
Oct 22 09:24:07 NOTICE[770065]: rtp.c:493 ast_rtp_read: Unknown RTP codec 127 received
Oct 22 09:24:07 NOTICE[770065]: rtp.c:493 ast_rtp_read: Unknown RTP codec 127 received
Oct 22 09:24:07 NOTICE[770065]: rtp.c:493 ast_rtp_read: Unknown RTP codec 127 received
Oct 22 09:24:07 NOTICE[770065]: rtp.c:493 ast_rtp_read: Unknown RTP codec 127 received
Oct 22 09:24:07 NOTICE[770065]: rtp.c:493 ast_rtp_read: Unknown RTP codec 127 received
Oct 22 09:24:07 NOTICE[770065]: rtp.c:493 ast_rtp_read: Unknown RTP codec 127 received
Oct 22 09:24:07 NOTICE[770065]: rtp.c:493 ast_rtp_read: Unknown RTP codec 127 received
Oct 22 09:24:07 NOTICE[770065]: rtp.c:493 ast_rtp_read: Unknown RTP codec 127 received
pbx1*CLI>

Sip read:
BYE sip:3391040@192.168.228.202 SIP/2.0
Via: SIP/2.0/UDP 192.168.240.2:5060;branch=z9hG4bK24159
From: <sip:3790612@192.168.228.202>;tag=194800060d0f4fc7
To: <sip:3391040@192.168.228.202>;tag=as354b454b
Call-ID: 719300060d0f4fc7@192.168.240.2
CSeq: 21 BYE
Max-Forwards: 70
User-Agent: Wave7-LMGR release(0.1)
Content-Length: 0


9 headers, 0 lines
Sending to 192.168.240.2 : 5060 (non-NAT)
Transmitting (no NAT):
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.240.2:5060;branch=z9hG4bK24159
From: <sip:3790612@192.168.228.202>;tag=194800060d0f4fc7
To: <sip:3391040@192.168.228.202>;tag=as354b454b
Call-ID: 719300060d0f4fc7@192.168.240.2
CSeq: 21 BYE
User-Agent: Asterisk PBX
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER
Contact: <sip:3391040@192.168.228.202>
Content-Length: 0


to 192.168.240.2:5060
   -- Hungup 'Zap/1-1'
 == Spawn extension (main, 3391040, 1) exited non-zero on 'SIP/3790612-9ee2'
Destroying call '719300060d0f4fc7@192.168.240.2'
Comments:By: duanecox (duanecox) 2004-10-22 10:07:13

loaded up the rtp debug patch from another post.

turned on rtp debug:

Got RTP packet from 192.168.240.2:10002 (type 127, seq 46830, ts -130207039, len 4)
Oct 22 10:04:39 NOTICE[278545]: rtp.c:510 ast_rtp_read: Unknown RTP codec 127 received

Should have guessed, my device is sending this to asterisk on hangup.  Asterisk is just reporting "Unknown ..."

This only happens on hangup.  Normal RTP communication is as follows:

Sent RTP packet to 192.168.240.2:10002 (type 0, seq 25257, ts 18720, len 160)
Got RTP packet from 192.168.240.2:10002 (type 0, seq 47859, ts -119739279, len 80)
Got RTP packet from 192.168.240.2:10002 (type 0, seq 47860, ts -119739199, len 80)
Got RTP packet from 192.168.240.2:10002 (type 0, seq 47861, ts -119739119, len 80)
Sent RTP packet to 192.168.240.2:10002 (type 0, seq 25258, ts 18880, len 160)
Got RTP packet from 192.168.240.2:10002 (type 0, seq 47862, ts -119739039, len 80)

edited on: 10-22-04 10:29
By: Mark Spencer (markster) 2004-10-22 13:19:09

Codec 127 would be in the range of codecs which must be negotiated.  Ergo, the device sending it is incorrect in doing so (unless you can find some other sort of standard to explain it) and thus this is not an Asterisk bug.