Page Comparison

<div id="fb-root"></div>
<script>(function(d, s, id) {
  var js, fjs = d.getElementsByTagName(s)[0];
  if (d.getElementById(id)) return;
  js = d.createElement(s); js.id = id;
  js.src = 'https://connect.facebook.net/en_US/sdk.js#xfbml=1&version=v2.11';
  fjs.parentNode.insertBefore(js, fjs);
}(document, 'script', 'facebook-jssdk'));</script>

<div class="fb-like" data-href="https://confluence.wildix.com/x/h4BtB" data-layout="button_count" data-action="recommend" data-size="large" data-show-faces="true" data-share="true"></div>

 <div class="lang-box-pdf">
	<div>
		<div class="google-lang">
			<div id="google_translate_element">
			</div>
			<script type="text/javascript">
					function googleTranslateElementInit() {
						new google.translate.TranslateElement({pageLanguage: 'en', includedLanguages: 'de,es,fr,it,nl', autoDisplay: false}, 'google_translate_element');
						}
			</script>
			<script type="text/javascript" src="//translate.google.com/translate_a/element.js?cb=googleTranslateElementInit"></script>
		</div>
		
		<div class="pdf-button">
			<a href="https://confluence.wildix.com/spaces/flyingpdf/pdfpageexport.action?pageId=74285191" alt="Convert to .pdf" title="Convert to .pdf"><img src="https://confluence.wildix.com/download/attachments/14549012/pdf-button-download-wildix-documentation.png"></a>
		</div>
	</div>
</div>

Use case

...

Assuming people from different sites of the deployment have separate Dialplans, in each Dialplan, create an entry where all parked calls will go based on the park extensions’ naming pattern. In the example below we added park extensions 201 & 202:

Image Added

Thus, Dialplan entry 20X of the Diaplan SiteA is where all calls transferred to park extensions 201 and 202 from the users of Site A will be routed to. There, using the Set -> Caller name -> SiteA (caller name) application, we will add the flag “SiteA” to the caller name to identify these calls and route them correspondingly later on. 

In our example we only have 2 separate sites, A & B, but this is of course scalable and you can have as many dial plans as required by replicating SiteA dial plan with minor changes. 

Image Added

Step 2

Create a new Dialplan and name it “receptionist”. This is where all calls returning from park extensions after timeout go. You do not need to configure this, the system does this automatically. And this is also where we will be routing those calls based on the marker added earlier. 

Using the Verify caller -> SiteA & Verify caller -> SiteB logical checks, route calls returning from park locations after timeout as shown in the example below. You don’t need to route calls to entries in “receptionist” Dialplan, it can be any other Dialplan or rule depending on the setup. 

Image Added

...

Park call timeout can be set in WMS -> Dialplan -> General Settings:

...

Image Added