On 01.03.2012, at 02:27, Juha Heinanen wrote:

> when sems sbc (master branch) receives invite with this kind of sdp:
> 
>    Message Body
>        Session Description Protocol
>            Session Description Protocol Version (v): 0
>            Owner/Creator, Session Id (o): - 3084861429 1172237394 IN IP4 
> 124.6.198.60
>            Session Name (s): -
>            Connection Information (c): IN IP4 124.6.198.60
>            Time Description, active time (t): 0 0
>            Session Attribute (a): tool:baresip 0.4.0
>            Media Description, name and address (m): audio 39674 RTP/AVP 96 97 
> 98 99 9 8 0 101
>            Bandwidth Information (b): AS:125
>            Media Attribute (a): rtpmap:96 opus/48000
>            Media Attribute (a): rtpmap:97 CELT/32000
>            Media Attribute (a): rtpmap:98 speex/16000
>            Media Attribute (a): fmtp:98 mode="7";vbr=off;cng=on
>            Media Attribute (a): rtpmap:99 speex/8000
>            Media Attribute (a): fmtp:99 mode="7";vbr=off;cng=on
>            Media Attribute (a): rtpmap:9 G722/8000
>            Media Attribute (a): rtpmap:8 PCMA/8000
>            Media Attribute (a): rtpmap:0 PCMU/8000
>            Media Attribute (a): rtpmap:101 telephone-event/8000
>            Media Attribute (a): fmtp:101 0-15
>            Media Attribute (a): sendrecv
>            Media Attribute (a): label:1
>            Media Attribute (a): ptime:20
>            Media Description, name and address (m): video 13966 RTP/AVP 96 34 
> 97
>            Bandwidth Information (b): AS:875
>            Media Attribute (a): rtpmap:96 H264/90000
>            Media Attribute (a): fmtp:96 
> packetization-mode=0;profile-level-id=42800c
>            Media Attribute (a): rtpmap:34 H263/90000
>            Media Attribute (a): fmtp:34 F=1;CIF=1;CIF4=1
>            Media Attribute (a): rtpmap:97 MP4V-ES/90000
>            Media Attribute (a): fmtp:97 profile-level-id=3
>            Media Attribute (a): sendrecv
>            Media Attribute (a): label:2
>            Media Attribute (a): framerate:25
>            Media Attribute (a): rtcp-fb:* nack pli
>            Media Attribute (a): content:main
> 
> it replies in 200 ok with this kind of sdp:
> 
>        Session Description Protocol
>            Session Description Protocol Version (v): 0
>            Owner/Creator, Session Id (o): sems 1 1 IN IP4 192.98.102.13
>            Session Name (s): sems
>            Connection Information (c): IN IP4 192.98.102.13
>            Time Description, active time (t): 0 0
>            Media Description, name and address (m): audio 40004 RTP/AVP 102 9 
> 8 0 96
>            Media Attribute (a): rtpmap:102 speex/8000
>            Media Attribute (a): rtpmap:9 g722/8000
>            Media Attribute (a): rtpmap:8 PCMA/8000
>            Media Attribute (a): rtpmap:0 PCMU/8000
>            Media Attribute (a): rtpmap:96 telephone-event/8000
>            Media Attribute (a): sendrecv
>            Media Description, name and address (m): video 0 RTP/AVP 96
>            Media Attribute (a): inactive
> 
> when sems then sends session timer re-invite, its sdp looks like this:
> 
>        Session Description Protocol
>            Session Description Protocol Version (v): 0
>            Owner/Creator, Session Id (o): sems 1 1 IN IP4 192.98.102.13
>            Session Name (s): sems
>            Connection Information (c): IN IP4 192.98.102.13
>            Time Description, active time (t): 0 0
>            Media Description, name and address (m): audio 40004 RTP/AVP 102 9 
> 8 0 96
>            Media Attribute (a): rtpmap:102 speex/8000
>            Media Attribute (a): rtpmap:9 g722/8000
>            Media Attribute (a): rtpmap:8 PCMA/8000
>            Media Attribute (a): rtpmap:0 PCMU/8000
>            Media Attribute (a): rtpmap:96 telephone-event/8000
>            Media Attribute (a): sendrecv
>            Media Description, name and address (m): audio 40004 RTP/AVP 101 
> 102 8 0 3 2 9 96 97 98 99 100
>            Media Attribute (a): rtpmap:101 iLBC/8000
>            Media Attribute (a): rtpmap:102 speex/8000
>            Media Attribute (a): rtpmap:8 PCMA/8000
>            Media Attribute (a): rtpmap:0 PCMU/8000
>            Media Attribute (a): rtpmap:3 GSM/8000
>            Media Attribute (a): rtpmap:2 G721/8000
>            Media Attribute (a): rtpmap:9 g722/8000
>            Media Attribute (a): rtpmap:96 telephone-event/8000
>            Media Attribute (a): rtpmap:97 G726-32/8000
>            Media Attribute (a): rtpmap:98 G726-24/8000
>            Media Attribute (a): rtpmap:99 G726-40/8000
>            Media Attribute (a): rtpmap:100 G726-16/8000
>            Media Attribute (a): sendrecv
> 
> why does sems include two audio sections with overlapping codecs?
> 

Obviously a bug ;-) Could you please file it on bugtracker.iptel.org?

-Raphael.

> -- juha
> _______________________________________________
> Semsdev mailing list
> [email protected]
> http://lists.iptel.org/mailman/listinfo/semsdev

_______________________________________________
Semsdev mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/semsdev

Reply via email to