Accepted Solutions
A region when created can be setup to have mappings to multiple regions, for instance "test" looks something like this:
The relationship section is important (note the regions not displayed use system default, which is determined by a service parameters for inter region codec default and intra region codec default). No matter how many regions are listed in the region relationship mapping section when a call is placed from your ICT, the call will be routed based on the number dialed. Depending on the number dialed it will route to where it should, say for instance phone A was dialed. Call Manager looks at the device pool of phone A, to fine the region that is set. If phone A is in region Boston, call manager looks up the mapping (Region Relationship) between what is set on the device pool > region setting, and the phone. For this example we'll say the ICT is in the test region shown above because of the device pool region setting. Call Manager looks up the region of the calling device which is the ICT and finds region test, then locates the called phone in region Boston. Then to manually map out what Call Manager does, go to System > Region, find the ICT's region, in this case test, find the called phone's region, Boston, and the audio codec to the right is what is used. In the case it's g.711. If nothing was listed we would use the system default. The default is set as a service parameter and usually calls within the same region, a device in the Boston region to another Boston region device would use g711 and default between regions will use g729.
In the same scenario, a call to a phone in region Default from the same ICT, would use g729 because the ICT is still in the test region, and the called party is in Default so the above image shows for Default (while looking at the Test region's setting) audio codec g.729.
To complicate things a little, the region mapping isn't strict but rather a maximum bandwidth that can be used. If a call based on the region mapping above shows g.711 the call can setup as anything below the bandwidth of g.711 (64Kbps) so it could still be setup as g.729 if one or both devices ony support g.729. You can ignore this part though for now.
Let me know if that's any clearer.
A region when created can be setup to have mappings to multiple regions, for instance "test" looks something like this:
The relationship section is important (note the regions not displayed use system default, which is determined by a service parameters for inter region codec default and intra region codec default). No matter how many regions are listed in the region relationship mapping section when a call is placed from your ICT, the call will be routed based on the number dialed. Depending on the number dialed it will route to where it should, say for instance phone A was dialed. Call Manager looks at the device pool of phone A, to fine the region that is set. If phone A is in region Boston, call manager looks up the mapping (Region Relationship) between what is set on the device pool > region setting, and the phone. For this example we'll say the ICT is in the test region shown above because of the device pool region setting. Call Manager looks up the region of the calling device which is the ICT and finds region test, then locates the called phone in region Boston. Then to manually map out what Call Manager does, go to System > Region, find the ICT's region, in this case test, find the called phone's region, Boston, and the audio codec to the right is what is used. In the case it's g.711. If nothing was listed we would use the system default. The default is set as a service parameter and usually calls within the same region, a device in the Boston region to another Boston region device would use g711 and default between regions will use g729.
In the same scenario, a call to a phone in region Default from the same ICT, would use g729 because the ICT is still in the test region, and the called party is in Default so the above image shows for Default (while looking at the Test region's setting) audio codec g.729.
To complicate things a little, the region mapping isn't strict but rather a maximum bandwidth that can be used. If a call based on the region mapping above shows g.711 the call can setup as anything below the bandwidth of g.711 (64Kbps) so it could still be setup as g.729 if one or both devices ony support g.729. You can ignore this part though for now.
Let me know if that's any clearer.
