| commit | 39191b2edf218df736048216315c08646ff0eaa6 | |
| author | Jakub Adam <jakub.adam@ktknet.cz> | |
| Fri, 19 Jun 2015 13:02:16 +0000 (19 15:02 +0200) | ||
| committer | Jakub Adam <jakub.adam@ktknet.cz> | |
| Mon, 29 Jun 2015 11:36:55 +0000 (29 13:36 +0200) | ||
| tree | 32dfd2ce5430422e3fbc2b6fc23120f911efcc22 | treesnapshot (tar.gz zip) |
| parent | cb94918577052bb1b74f46f162e11c995b41fddb | commitdiff |
srtp: honor encryption key ID in INVITE response
Media encryption key we offer in a response to a call invitation should
have the same ID as that 'a=crypto' line from the caller's INVITE which
we want to use for encrypting the data stream.
So far the ID was hardcoded as '1', which was causing trouble
communicating with some endpoints, namely when we were accepting a call
from the public telephone network through a PSTN gateway.
Media encryption key we offer in a response to a call invitation should
have the same ID as that 'a=crypto' line from the caller's INVITE which
we want to use for encrypting the data stream.
So far the ID was hardcoded as '1', which was causing trouble
communicating with some endpoints, namely when we were accepting a call
from the public telephone network through a PSTN gateway.
| src/core/sdpmsg.c | diffblobblamehistory | |
| src/core/sdpmsg.h | diffblobblamehistory | |
| src/core/sipe-media.c | diffblobblamehistory |