diff options
| author | Terry Wilson <twilson@digium.com> | 2012-09-25 19:08:02 +0000 |
|---|---|---|
| committer | Terry Wilson <twilson@digium.com> | 2012-09-25 19:08:02 +0000 |
| commit | b7233b18ebd9ce2f8f4bad1309fbe33edaf44e44 (patch) | |
| tree | 803a5d54535cb2aa4fc5d6ca4a0b32933a29f497 /funcs/func_callerid.c | |
| parent | 0a9d89d6be870d3b55dccd150ae5202aa5e46e65 (diff) | |
Properly handle UAC/UAS roles for SIP session timers
The SIP session timer mechanism contains a mandatory 'refresher' parameter
(included in the Session-Expires header) which is used in the session timer
offer/answer signaling within a SIP Invite dialog. It looks like asterisk is
interpreting the uac resp. uas role only as the initial role of client and
server (caller is uac, callee is uas). The standard rfc 4028 however assigns
the client role to the ((RE)-Invite) requester, the server role to the
((RE)-Invite) responder.
This patch has Asterisk track the actual refresher as "us" or "them" as opposed
to relying on just the configured "uas" or "uac" properties.
(closes issue AST-922)
Reported by: Thomas Airmont
Review: https://reviewboard.asterisk.org/r/2118/
........
Merged revisions 373652 from http://svn.asterisk.org/svn/asterisk/branches/1.8
........
Merged revisions 373665 from http://svn.asterisk.org/svn/asterisk/branches/10
........
Merged revisions 373690 from http://svn.asterisk.org/svn/asterisk/branches/11
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@373691 65c4cc65-6c06-0410-ace0-fbb531ad65f3
Diffstat (limited to 'funcs/func_callerid.c')
0 files changed, 0 insertions, 0 deletions