Patton electronic SmartNode 4110 Series manual Table in table-name, And/or, Specified direction

SmartWare Software Configuration Guide 33 • CS interface configuration

to another user agent having a different URI than the called one. This new URI as well as the derived E.164 number cannot be manipulated using the call router before presenting it to the other party.

To circumvent this limitation, you can use mapping tables directly on an interface. In that case the mapping tables can be thought as input or output filters, which manipulate call properties at any stage of a call.

As with the SIP transfer example, differentiating called from calling party properties does not make sense for these manipulations, because the calling as well as the called party can be transferred in a SIP call. Therefore, mapping tables that are used on an interface manipulate both at the same time, called and calling party proper- ties!

You can chose different mapping tables for filtering parameters in each direction, input and output. While an input mapping table is applied to all properties that are received by the port or gateway that is bound to the interface before sending them to the peer interface in the CS context, an output mapping table is applied to all properties before sending them to the bound port or gateway.

Refer to the chapter 40, “Call router configuration” on page 456 for more information about how to create and configure mapping tables.

Procedure: To use mapping tables to filter properties on an CS interface

Mode: Context CS

Step	Command	Purpose
1	node(ctx-cs)[switch]#interface if-type if-	Enters CS Interface Configuration Mode and config-
	name	ure interface if-typewith name if-name
2	node(if-type)[if-name]#use mapping-	Specifies an input and/or an output mapping table
	table in table-name	that shall be applied to all call properties in the
	and/or	specified direction.
	node(if-type)[if-name]#use mapping-
	table out table-name

Example: Use interface mapping tables for dialing plan conversion

The following example shows how to configure a dialing plan conversion on an interface. In this case, you can plan your call-routing tables to deal only with international numbers while converting private numbers on the CS interface that interfaces the private network.

node(ctx-cs)[switch]#mapping-table e164 to e164 PRIV-TO-GLOB node(map-tab)[PRIV-TO~]#map (..) to 00419988825\1 node(map-tab)[PRIV-TO~]#exit node(ctx-cs)[switch]#mapping-table e164 to e164 GLOB-TO-PRIV node(map-tab)[GLOB-TO~]#map 00419988825(..) to \1 node(map-tab)[GLOB-TO~]#exit node(ctx-cs)[switch]#interface isdn IF-PHONES node(if-isdn)[IF-PHON~]#route dest-table TAB-CALLED-NUMBER node(if-isdn)[IF-PHON~]#use mapping-table in PRIV-TO-GLOB node(if-isdn)[IF-PHON~]#use mapping-table out GLOB-TO-PRIV node(if-isdn)[IF-PHON~]#exit

node(ctx-cs)[switch]#

Configuring the interface mapping tables 386