[Spce-user] Remove SDP media-level attribute - direction
Andreas Granig
agranig at sipwise.com
Fri Nov 9 06:45:49 EST 2012
Hi Imanol,
Oh, right, it's added by the proxy then after mediaproxy is engaged. So
the best place would be the load-balancer config at
/etc/ngcp-config/templates/etc/kamailio/lb/kamailio.cfg.customtt.tt2.
Andreas
On 11/09/2012 11:49 AM, Imanol Pardavila wrote:
> Hi Andreas,
> Looking at my traces I'm sure that endpoints aren't sending this
> attribute; I've just filtered the first packet with this line on SDP
> body and it's been sent by CE.
>
> * SDP sent from our SBC to CE:
>
> Session Description Protocol
> Session Description Protocol Version (v): 0
> Owner/Creator, Session Id (o): Sonus_UAC IN IP4 10.34.241.67
> Session Name (s): SIP Media Capabilities
> Connection Information (c): IN IP4 10.34.240.60
> Time Description, active time (t): 0 0
> Media Description, name and address (m): audio 1552 RTP/AVP
> 0 8 101
> Media Attribute (a): rtpmap:0 PCMU/8000
> Media Attribute (a): rtpmap:8 PCMA/8000
> Media Attribute (a): rtpmap:101 telephone-event/8000
> Media Attribute (a): fmtp:101 0-15
> Media Attribute (a): sendrecv
> Media Attribute (a): ptime:20
>
> * SDP sent from CE to our SBC (following packet in the sequence):
>
> Session Description Protocol
> Session Description Protocol Version (v): 0
> Owner/Creator, Session Id (o): Sonus_UAC IN IP4 10.34.242.11
> Session Name (s): SIP Media Capabilities
> Connection Information (c): IN IP4 10.34.242.11
> Time Description, active time (t): 0 0
> Media Description, name and address (m): audio 30132 RTP/AVP
> 0 8 101
> Media Attribute (a): rtpmap:0 PCMU/8000
> Media Attribute (a): rtpmap:8 PCMA/8000
> Media Attribute (a): rtpmap:101 telephone-event/8000
> Media Attribute (a): fmtp:101 0-15
> Media Attribute (a): sendrecv
> Media Attribute (a): ptime:20
> *Media Attribute (a): direction:active**
> ** Media Attribute (a): oldmediaip:10.34.240.60**
> ** Media Attribute (a): nortpproxy:yes*
>
> Flow diagram:
>
> |endpoint A| ------------- |SBC| ------------- |CE| ------------- |SBC|
> ------------- |endpoint B|
>
> SBC: 10.34.240.60, 10.34.241.67
> CE: 10.34.242.11
>
> Any ideas?
> Thanks
> Best regards
> Imanol
>
> El 08/11/2012 20:22, Andreas Granig escribió:
>> Hi,
>>
>> On 11/08/2012 05:25 PM, Imanol Pardavila wrote:
>>> I'm not sure about who builds SDP? lb, proxy, sems? I guess that the
>> The SDP is created by the endpoints, not by the CE.
>>
>>> idea is create my customtt.tt2 file and use replace_body_all () function
>>> something like:
>>>
>>> # remove direction attribute
>>> replace_body_all(" a=directmedia:active ", "");
>>>
>>> Is it correct?
>> Not sure about the whitespaces, you might need to leave them out I guess.
>>
>> Andreas
>>
>>
>>
>> _______________________________________________
>> Spce-user mailing list
>> Spce-user at lists.sipwise.com
>> http://lists.sipwise.com/listinfo/spce-user
>>
>>
>> -----
>> No se encontraron virus en este mensaje.
>> Comprobado por AVG - www.avg.com
>> Version: 2012.0.2221 / Base de datos de virus: 2441/5382 - Fecha de publicacion: 11/08/12
>
>
>
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> http://lists.sipwise.com/listinfo/spce-user
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 897 bytes
Desc: OpenPGP digital signature
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20121109/f4569b9b/attachment-0001.asc>
More information about the Spce-user
mailing list