<html>
<head>
<base href="https://wiki.asterisk.org/wiki">
<link rel="stylesheet" href="/wiki/s/en/2171/18/9/_/styles/combined.css?spaceKey=TOP&forWysiwyg=true" type="text/css">
</head>
<body style="background: white;" bgcolor="white" class="email-body">
<div id="pageContent">
<div id="notificationFormat">
<div class="wiki-content">
<div class="email">
<h2><a href="https://wiki.asterisk.org/wiki/display/TOP/Call+Setup+Sequence+Diagram">Call Setup Sequence Diagram</a></h2>
<h4>Comment <b>removed</b> by <a href="https://wiki.asterisk.org/wiki/display/~beagles">Brent Eagles</a>
</h4>
<br/>
<div class="notificationGreySide">
<p>The CallManager lives wherever... we could have a default implementation somewhere or it could simply be a null proxy. In the case of a null, the bridge would place its own call manager implementation that whose behavior would be according to configuration. One way to look at the CallManager is that it is "object-oriented-way" to do something that might otherwise be accomplished with hooks. At any rate, I put this in here because I felt that call lifecycle management should not be the responsibility of the bridge instance itself.</p>
<p>I agree that I'm iffy about the bridge initiating the call (of course it would only initiate the call if that leg was not already setup). There's a gray area here for me... I'm not sure why we <b>would not</b> want to do this. Once an endpoint has been located via the router, I cannot see the benefit of driving that aspect of the call setup outside of the context of a bridge.. all protocol specific stuff happens in the respective channel service and the initiator does not care about the format's etc.. A counter-example might be helpful here.</p>
</div>
<div id="commentsSection" class="wiki-content pageSection">
<div style="float: right;" class="grey">
<a href="https://wiki.asterisk.org/wiki/users/removespacenotification.action?spaceKey=TOP">Stop watching space</a>
<span style="padding: 0px 5px;">|</span>
<a href="https://wiki.asterisk.org/wiki/users/editmyemailsettings.action">Change email notification preferences</a>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>