[Spce-user] rtpengine a=crypto problem

[Nikita Stashkov]

This is a common way to set call on hold. May be there are different RFCs, but this method is used.
Can I switch off this feature? Can not find this in source.

Regards,
Nikita Stashkov
24 июня 2014 г., в 16:02, Richard Fuchs <rfuchs at sipwise.com> написал(а):

> On 06/24/14 09:29, Nikita Stashkov wrote:
>> Hello, I am using the latest version of rtpengine  - 3.3.0.0+0~mr3.4.0.0.
>> 
>> Below you can see two offers:
> ...
>> In the first case a=crypto is returned to proxy. The second - no. What
>> is the difference?
>> Also the second case a=sendonly is set, and a=inactive is returned.
> 
> The difference is that in the second SDP, the IP address was zeroed out:
> 
> c=IN IP4 0.0.0.0
> 
> Rtpengine understood this to disable all media. Perhaps misunderstood,
> as the client obviously wanted to put the media into sendonly state.
> I'll have to check the RFCs to see if there's a bug here.
> 
> cheers
> 
> _______________________________________________
> 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: smime.p7s
Type: application/pkcs7-signature
Size: 3903 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140624/5eff484e/attachment-0001.p7s>