You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

This page contains a simple example to demonstrate the manipulation of the ext= and phone-context= tags of the SIP URI for calls to and from Teams/Skype clients. The

Unable to show "metadata-from": No such page "_space_variables"
SBC 1000/2000 system will send calls to a Teams/Skype client with ext and phone-context configured properly, and when received, the Teams/Skype client will appropriately set the calling number based on the phone-context value:

Call Route Table

We create a call routing table with the following 3 call routing entries in it. Two of the entries point to Transformation tables for calls that originate from SIP and PSTN devices to a Teams/Skype client, and the third call routing entry points to a Transformation table for a call that originates from a Teams/Skype client to a PSTN device:

Row

Transformation Table

Destination Type

Signaling Group

Media Selection

Media Transcoding

Call Control Profile

Fork

1

SIP URI Manipulation#Local SIP Phone to Teams/Skype

normal

registra

G.711

Enabled

None

No

2

SIP URI Manipulation#PSTN to Teams/Skype

normal

ISDN

G.711

Enabled

None

No

3

SIP URI Manipulation#Teams/Skype to PSTN

normal

Teams/Skype

G.711

Enabled

None

No

(tick) Click each Transformation table link above to view its summarized behavior.

Transformation Tables

Local SIP Phone to Teams/Skype

Summarized transformation behavior:

  • All Called Number of 4-digit whose number does not begin with '2' and Calling Number of 4-digit beginning with '2' will be sent to the Teams/Skype client.
    Unable to show "metadata-from": No such page "_space_variables"
    SBC 1000/2000 will set phone-context to fremont.example.com and ext to the Calling Number.

Row

Input Field

Match Field/ Field Value

Output Field/ Replaced by Field

Field Value

Match Type

1

Called Address/Number

([^2]\d{3}$)

Called Extension

\1

Mandatory

2

Calling Address/Number

(2\d{3}$)

Calling Extension

\1

Mandatory

3

Calling Address/Number

(2\d{3}$)

Calling Phone Context

fremont.example.com

Mandatory

Mmessage Flow:


Local SIP Phone to Teams/Skype


PSTN to Teams/Skype

Summarized transformation behavior:

  • Calls with Called Number of 14085551000 will be sent to Teams/Skype with phone-context set to san_jose.example.com
  • Calls with Called Number of 14155553000 will be sent to Teams/Skype with phone-context set to san_francisco.example.com

Row

Input Field

Match Field/ Field Value

Output Field/ Replaced by Field

Field Value

Match Type

1

Called Address/Number

14085551000

Calling phone context

san_jose.example.com

Optional

2

Called Address/Number

14155553000

Calling phone context

san_francisco.example.com

Optional

Message Flow:


PSTN to Teams/Skype


Teams/Skype to PSTN

Summarized transformation behavior:

  • Calls with Called Number of 1 plus ten digits and phone-context of san_jose.example.com will be sent to the PSTN with Calling Number set to 14085551000
  • Calls with Called Number of 1 plus ten digits and phone-context of san_francisco.example.com will be sent to the PSTN with Calling Number set to 14155553000

Row

Input Field

Match Field/ Field Value

Output Field/ Replaced by Field

Field Value

Match Type

1

Called Address/Number

(1\d{10}$)

Called Extension

\1

Mandatory

2

Calling phone context

san_jose.example.com

Calling Address/Number

14085551000

Optional

3

Calling phone context

san_francisco.example.com

Calling Address/Number

14155553000

Optional

Message Flow:


Teams/Skype to PSTN



Note: SIP message sent by the

Unable to show "metadata-from": No such page "_space_variables"
SBC 1000/2000 system should have the From and To headers as follows:

From: 5551234<sip:5551234;ext=1234;phone-context=example.com@192.168.1.10>
To: tel:2222<sip:2222;ext=2222;phone-context=example.com@192.168.1.20>
  • No labels