-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Anyone know how to make sense of this? I'm pretty dumb when it comes to the rtp protocol. If someone can confirm this is a bug, we can put it into bugs.digium.com...
Pete - -----Original Message----- From: Robin Raymond [mailto:[EMAIL PROTECTED] Sent: Friday, August 22, 2003 6:48 PM To: Peter Grace Subject: RE: Payload numbers Hi Peter, Well, from what I understand by this user, Asterisk is not examining the RTP payload number for speex or iLBC that X-Lite is using. In the INVITE request, I tell Asterisk which codec payload numbers I'm using, which is different that what Asterisk sends back. Asterisk reports back it's payload numbers. I send my RTP using your speex/iLBC payload numbers that you expect from your SDP, and I expect RTP to come back with my speex/iLBC payload numbers that I provided in my SDP. Now I'm not 100% sure I'm doing that right, so perhaps I have a bug. v=0 o=21186 21339250 21339250 IN IP4 64.180.128.147 s=X-PRO c=IN IP4 64.180.128.147 t=0 0 m=audio 8000 RTP/AVP 0 8 3 98 97 101 a=rtpmap:0 pcmu/8000 a=rtpmap:8 pcma/8000 a=rtpmap:3 gsm/8000 a=rtpmap:98 iLBC/8000 <-- this is my mapping a=rtpmap:97 speex/8000 <-- this is my mapping a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 As what I understand, calling w/ speex/iLBC simply doesn't work between X-Lite and Asterisk. Not sure why. No I didn't receive the e-mail about the PPC. Feel free to CC me on stuff like that :) Any ideas? - -Rob -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 7.0.3 for non-commercial use <http://www.pgp.com> iQA/AwUBP0at7NW8rcEEsO4aEQLKpwCeOBIZ3pogL2JQ6EL9p50EBW/PYZ8An063 ereE1and4UKs7/uFcF45iu0M =r3uu -----END PGP SIGNATURE----- _______________________________________________ Asterisk-Dev mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-dev
