====== How to Implement Devices Connecting Each Other between Different Servers in LAN ====== <note important> System Overview：There are two AsterCC servers in a LAN，named A and B：A(192.168.1.175) has five devices：5001-5100，they are belong to "astercc5" team，at the same time，the B(192.168.1.226) has five devices：6000-6100，they belong to "astercc6" team。 </note> ===== Add Trunks ===== <note tip> Adding trunks on A and b respectively，to implement connectivity between them. </note> For example，we will illustrate it on server A，click [PBX]->[Trunks]->[Add]，we can open trunk management page，as following： {{:en:real_case_guidance:create_trunk_01.png?700|}} ===== Binding the Trunk to Team ===== <note tip> We should bind the new trunk above to devices's team. If team's trunk has existed，we usually bind two(or more) trunks into a trunk group first，and then bind this trunk group to the team. </note> Binding the trunk to team to dial out. Click [User]->[Teams]，double-click the data，click [confirm] after we choose the trunk group，as following： {{:en:real_case_guidance:trunk_to_team01.png?700|}} If team's trunk has existed，we usually bind two(or more) trunks into a trunk group first，then bind this trunk group to the team，and edit rule at last。Click [Advanced]->[Trunk Groups]->[Add]，open the trunk group management page，click [Save] after edit，as following： {{:en:real_case_guidance:trunk_to_team02.png?700|}} Click [Edit Rule]，edit "Trunk Name"、"Status"、"Match Type"、"Ori.Prefix" and "Ori.Length"，click [OK]，you can see the rule new below，as following： {{:en:real_case_guidance:trunk_to_team03.png?700|}} Last，binding the trunk groups to team，as following： {{:en:real_case_guidance:trunk_to_team04.png?700|}} ===== Site the Inbound Routes ===== <note tip> We site the inbound routes，Trunk Match to "Trunk" which we new above，Transfer to "Device" and Actionid to "Auto Match"。 </note> Click [Advanced]->[Inbound Routes]->[Add]，open inbound route management page，as following： {{:en:real_case_guidance:site_inbound_routes01.png?700|}} <note warning> We must do the same settings on the AsterCC system in server B. </note>