Adds peer to CEL report on CEL_BRIDGE_START and CEL_BRIDGE_END

(closes issue ASTERISK-17940)
Reporter: Nic Colledge
Patches:
	features_18.patch uploaded by Nic Colledge (license 6245)


git-svn-id: https://origsvn.digium.com/svn/asterisk/branches/1.8@350501 65c4cc65-6c06-0410-ace0-fbb531ad65f3
certified/1.8.11
Jonathan Rose 14 years ago
parent 929c8c3cb7
commit f22392dbdc

@ -4003,7 +4003,7 @@ int ast_bridge_call(struct ast_channel *chan, struct ast_channel *peer, struct a
* present. */
ast_clear_flag(bridge_cdr, AST_CDR_FLAG_DIALED);
}
ast_cel_report_event(chan, AST_CEL_BRIDGE_START, NULL, NULL, NULL);
ast_cel_report_event(chan, AST_CEL_BRIDGE_START, NULL, NULL, peer);
/* If we are bridging a call, stop worrying about forwarding loops. We presume that if
* a call is being bridged, that the humans in charge know what they're doing. If they
@ -4243,7 +4243,7 @@ int ast_bridge_call(struct ast_channel *chan, struct ast_channel *peer, struct a
if (f)
ast_frfree(f);
}
ast_cel_report_event(chan, AST_CEL_BRIDGE_END, NULL, NULL, NULL);
ast_cel_report_event(chan, AST_CEL_BRIDGE_END, NULL, NULL, peer);
before_you_go:
/* Just in case something weird happened and we didn't clean up the silence generator... */

Loading…
Cancel
Save