[Spce-user] rtpengine a=crypto problem

[Nikita Stashkov]

Thank you, Richard,

Commenting two lines 1907 and 1908 helps.
May be it will be other issues? Let me know, if possible.

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

> On 06/24/14 10:23, Nikita Stashkov wrote:
>> 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.
> 
> Reading up on it, RFC 3264 states in 8.4 that setting the c= address to
> zero is an obsolete method of putting media on hold and is no longer
> recommended. As such, rtpengine should probably still support it. I'll
> see if I can get a working patch in. In the meantime, if you wish to
> manually patch it out yourself, look in line 1902 of call.c.
> 
> cheers

-------------- 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/5d6614e0/attachment-0001.p7s>