diff options
| author | Kevin Harwell <kharwell@digium.com> | 2015-01-30 17:38:10 +0000 |
|---|---|---|
| committer | Kevin Harwell <kharwell@digium.com> | 2015-01-30 17:38:10 +0000 |
| commit | 6583b4de98dfa8ba1964dc4e685b02d260a749ed (patch) | |
| tree | 51fe24200a636693e80789b9f2afd0859641eedd /main | |
| parent | 112d23c73e0a81f5870ba9f58aa588b89ae31c44 (diff) | |
res_pjsip_outbound_publish: eventually crashes when no response is ever received
When Asterisk attempts to send SIP outbound publish information and no response
is ever received (no 200 okay, 412, 423) the system eventually crashes. A
response is never received because the system Asterisk is attempting to send
publish information to is not available. The underlying pjsip framework attempts
to send publish information. After several attempts it calls back into the
Asterisk outbound publish code. At this point if the "client->queue" is empty
Asterisk attempts to schedule a refresh which utilizes "rdata" and since no
response was received the given "rdata" struture is NULL. Attempting to
dereference a NULL object of course results in a crash.
The fix here removes the dependency on rdata for schedule_publish_refresh.
Instead param->expiration is now passed to it as this is set to -1 if no
response is received. Also added a notification when no response is received.
ASTERISK-24635 #close
Reported by: Marco Paland
Review: https://reviewboard.asterisk.org/r/4384/
git-svn-id: https://origsvn.digium.com/svn/asterisk/branches/13@431490 65c4cc65-6c06-0410-ace0-fbb531ad65f3
Diffstat (limited to 'main')
0 files changed, 0 insertions, 0 deletions