Linksys Mediatrix 440 Configuration manual

Download

SPA9 0 0 0/M ediatrix® 4 40 x ISDN Gatew ay Conf iguration Guide

Corporat e Headqu arters

Linksys 121 Theory Drive Irvine, CA 92617 USA http://www.linksys.com Tel: 949 823-1200

800 546-5797

Fax: 949 823-1100

SPA9000/Mediatrix® 440x ISDN Gateway Configuration Guide

Copyright ©2007 Cisco Systems, Inc. All rights reserved.Specifications are subject to change without notice. Linksys is a registered trademark or trademark of Cisco Systems, Inc. and/or its affiliates in the U.S. and certain other countries. Other brands and product names are trademarks or registered trademarks of their respective holders.

Use of Proprietary Information and Copyright Notice:

This release note document contains proprietary information that is to be used only by Sipura Technology customers. Any unauthorized disclosure, copying, distribution, or use of this information is prohibited. This restriction includes ALL Internet based discussion forums, e.g. DSLreports

Compliance and Safety Information

This equipment has been tested and found to comply with the limits for a Class B digital device in accordance with the specifications in part 15 of the FCC rules. This product bears the CE Marking indicating compliance with the 89/336/EEC directive. Standards to which conformity is Declared: EN 61000-4-2:1995, EN 61000-4-3:1997, EN 61000-4-4:1995, EN 61000-4-5:1995, EN 61000-4-6:1996, EN 61000-4-8:1994, EN 61000-4-11:1994, EN 61000-3-2:2001, EN 61000-3-3:1995 & EN 55022:1998

Class B Modifications to this product not authorized by Linksys could void FCC approval, thereby terminating end user authority to use this product. For indoor use only. Read installation instructions before connecting to a power source. The electric plug and socket must be accessible at all times as this is the main method to disconnect power from the device.

Shock Hazard: Do not operate near water or similar fluid. Do not work with this device during periods of lightning activity. Do not touch wires at the end of cables or within sockets.

Disclaimer – Please Read:

This document contains implementation examples and techniques using Sipura Technology, Inc. and, in some instances, other company’s technology and products and is a recommendation only and does not constitute any legal arrangement between Sipura Technology, Inc. and the reader, either written or implied. The conclusions reached and recommendations and statements made are based on generic network, service and application requirements and should be regarded as a guide to assist you in forming your own opinions and decision regarding your particular situation. As well, Sipura Technology reserves the right to change the features and functionalities for products described in this document at any time. These changes may involve changes to the described solutions over time.

Mediatrix® is a registered trademark of Mediatrix Telecom.

Network Setup and Physical Installation 2

Configuring the Mediatrix 440x Gatew ay 3

Logging into the M ediatrix 440x Gatew ay W eb Interface 3

Configuring the Network Address 4

Configuring the SIP Port 5

Restarting the Mediatrix 440x Gateway 6

Configuring Communication to the SIP Proxy Server 8

Configuring ISDN Connectivity 9

Configuring Call Routing 10

Configuring DTMF Transport 14

CONTENTS

Configuring the SPA9000 15

Appendix A— SIP Traces of Various Scenarios 17

Incoming ISDN Call to the SPA9000 17

Outgoing ISDN Call from the SPA9000 Internal Endpoint 26

Appendix B— References 32

SPA9000/M ediatrix 440X ISDN Gatew ay

iii

Contents

SPA9000/M ediatrix 440X ISDN Gatew ay

SPA9000/M ediatrix® 440x ISDN Gatew ay Configuration Guide

This document helps the Linksys Voice System (LVS) administrator configure the Mediatrix® 440x ISDN digital gateway for providing ISDN-BRI connectivity. The recommended configuration lets small businesses use existing ISDN lines to initiate and receive calls using LVS devices. This document includes the following sections:

Network Setup and Physical Installation, page 2

•

• Configuring the Mediatrix 440x Gateway, page 3

• Configuring the SPA9000, page 15

• Appendix A—SIP Traces of Various Scenarios, page 17

• Appendix B—References, page 32

121 Theory Drive Ir vin e, CA 92617 USA http://w w w.l inksy s.com Tel: 949 823-1200 800 546-5797 Fax: 949 823-1100

Network Setup and Physical Installation

Netw ork Setup and Physical Installation

To initiate installation of the Mediatrix 440x gateway, connect the power supply to the power input port and connect the Ethernet network port to the LAN. The DHCP option on the ISDN gateway is active by default, so the gateway automatically gets its IP address from the network DHCP server, if available.

Configuring the Network Address, page 4 describes the network connectivity options recommended.

It is assumed that the SPA9000, SPA9xx phones, and the Mediatrix gateway are in the same local network and in the same VLAN.

Figure 1 Typical Netw ork Setup

Figure 1 shows the typical network setup.

SOHO or Small Business

Legacy

Telecom

Network

(ISDN)

Broadband

Phone Service

Broadband

Service

Mediatrix 4400

SPA400

Wireless

Router

BB Modem

SPA942

SPA9000

SPA941

Local Area

Network

Fax Machine

SPA921

SPA400

SPA9000/M ediatrix® 440x ISDN Gatew ay Configuration Guide

Configuring the M ediatrix 440x Gatew ay

This section describes how to configure the Mediatrix 440x gateway for use in an LVS network. It includes the following topics:

•

Logging into the Mediatrix 440x Gateway Web Interface, page 3

• Configuring the Network Address, page 4

• Configuring the SIP Port, page 5

• Restarting the Mediatrix 440x Gateway, page 6

• Configuring Communication to the SIP Proxy Server, page 8

• Configuring ISDN Connectivity, page 9

• Configuring Call Routing, page 10

• Configuring DTMF Transport, page 14

Note This document describes manual configuration, although the Mediatrix 440x gateway series supports

remote provisioning. For more information about that feature, contact Mediatrix.

Configuring the Mediatrix 440x Gatew ay

Logging into the M ediatrix 440x Gatew ay Web Interface

To access the Mediatrix 440x gateway web interface, complete the following steps:

Note Note that the PC you are using should be able to access the LVS network.

Step 1 In the web browser address field, enter the Mediatrix 440x gateway IP address. In this example, the IP

address is 192.168.1.75.

The login screen appears. (See

Figure 2 Login Screen

Figure 2.)

Step 2 In the User Name field, enter a user name. (See

The default username is public. Leave the Password field empty unless this has been previously set.

Figure 3.)

SPA9000/M ediatrix® 440x ISDN Gateway Configuration Guide

Configuring the Mediatrix 440x Gate way

Figure 3 Entering User Name and Password

Step 3 Click the Login button.

The main configuration screen appears. (See

Figure 4 M ain Configuration Screen

Figure 4.)

Configuring the Netw ork Address

Although the Mediatrix 440x gateway supports DHCP, it is recommended to use a static IP address. This helps ensure that the gateway is always reachable by LVS devices even if the DHCP server is restarted and new network addresses are assigned to the DHCP clients. This recommendation to use static IP addressing also applies to the SPA9000 and the SPA400.

Note For information on configuring static IP addresses for the SPA9000 and SPA400, refer to the SPA9000

Administration Guide.

To set a static IP address on the Mediatrix 440x gateway, complete the following steps:

Step 1 In the main configuration screen (see Figure 4), click Network, and then click Interfaces.

The Interfaces screen appears. (See

SPA9000/M ediatrix® 440x ISDN Gatew ay Configuration Guide

Figure 5.)

Configuring the Mediatrix 440x Gatew ay

Figure 5 Sett ing a Stat ic IP Address

Step 2 From the Uplink Interface drop-down list, select netwrk; and from the Connection Type drop-down list,

select Static, as shown in Figure 5.

Step 3 In the Static IP Address field, type the static IP address and network mask. (See

Figure 6 Entering the Static IP Address and Network Mask

Figure 6.)

This example uses 192.168.1.75 as the static IP address, and 255.255.255.0 (/24) for the network mask.

Step 4 To complete the configuration, click Submit.

Note After clicking Submit, the unit is reconfigured with the new IP address and your web browser will be

disconnected. To recover access, type the new IP address into the Internet browser address field.

Configuring the SIP Port

Perform the following procedure to specify the gateway SIP port and the SIP proxy server (the SPA9000) address to which the Mediatrix 440x gateway will route incoming ISDN calls and from which it will receive outgoing call requests. The SIP port specified should match the configuration on the SPA9000.

Step 1 In the main configuration screen (see Figure 4), click SIP, and then click Gateways.

The Gateways screen appears (see

Figure 7).

SPA9000/M ediatrix® 440x ISDN Gateway Configuration Guide

Configuring the Mediatrix 440x Gate way

Figure 7 Gatew ay Screen

Step 2 In the SIP Port field, type the SIP port number.

This example uses the default, which is 5060.

Note Verify that the specified port is being used in the SPA9000 when you define the proxy address (see

Configuring the SPA9000, page 15)

Step 3 Click Submit.

Restarting the M ediatrix 440x Gatew ay

You need to restart the affected services on the Mediatrix 440x gateway after configuration changes occur. (See

Figure 8.)

SPA9000/M ediatrix® 440x ISDN Gatew ay Configuration Guide

Configuring the Mediatrix 440x Gatew ay

Figure 8 Restart ing Services

To restart the Mediatrix 440x gateway services after making configuration changes, complete the following steps:

Step 1 On the Systems screen (see Figure 8), click Services.

The Services screen appears. (See

Figure 9 Services Screen

Figure 9.)

Step 2 For services marked with an asterisk (*), select Restart from the Action drop-down list.

SPA9000/M ediatrix® 440x ISDN Gateway Configuration Guide

Configuring the Mediatrix 440x Gate way

In this example, the affected service is the SIP Endpoint service (SIPEP).

After restarting the service, the correct SIP port appears in the Gateway option. (See

Figure 10 Confirming the Correct SIP Port

Figure 10.)

Configuring Communication to the SIP Proxy Server

The next step is to configure communication to the SIP proxy server that the 440x will use to route VoIP calls (the SPA9000).

In this example, the Mediatrix 440x gateway is configured with the IP address of the SPA9000. The SIP port used is the port assigned to the Line on the SPA9000 that is configured as the SIP trunk to the ISDN gateway. In this example, that is Line 3 and the SIP port assigned to Line 3 is 5062.

To configure these settings, complete the following steps:

Step 1 In the main configuration screen (see Figure 4), click SIP, and then click Servers.

The Servers screen appears. (See

Figure 11.)

SPA9000/M ediatrix® 440x ISDN Gatew ay Configuration Guide

Configuring the Mediatrix 440x Gatew ay

Figure 11 Servers Screen

Step 2 In the Proxy Host field, enter the correct SPA9000 IP address and SIP port.

Step 3 Click Submit.

Configuring ISDN Connectivity

After the ISDN line is connected to the BRI1 port (and the BRI2 port, if applicable), complete the following steps to configure ISDN settings:

Step 1 In the main configuration screen (see Figure 4), click ISDN, and then click Basic Rate Interface.

The Basic Rate Interface screen appears. (See

Figure 12.)

SPA9000/M ediatrix® 440x ISDN Gateway Configuration Guide

Configuring the Mediatrix 440x Gate way

Figure 12 Basic Rate Interface Screen

Step 2 From the Endpoint Type drop-down list, select TE (to emulate a terminal).

Step 3 From the Connection Type drop-down list, select Point to Multipoint.

Step 4 Click Submit.

Step 5 Restart the ISDN service from the Services page.

Configuring Call Routing

This section describes how to define the gateway function. In the example used in this guide, the Mediatrix 440x gateway routes all incoming ISDN calls from the BRI ports to the SPA9000, and directs call requests from the SPA9000 to ISDN.

This section also describes how to define a hunt group that groups the BRI1 and BRI2 ports on the Mediatrix 4402 gateway.

Note There is no need to define a hunt group if the Mediatrix 4401 gateway is used because it has only one

BRI port.

SPA9000/M ediatrix® 440x ISDN Gatew ay Configuration Guide

Configuring the Mediatrix 440x Gatew ay

To configure call routing, complete the following steps:

Step 1 In the main configuration screen (see Figure 4), click Telephony, and then click Call Routing Config.

The Call Routing Config screen appears. (See

Figure 13 Call Routing Config Screen

Figure 13).

Note Go to Step 7 if configuring a Mediatrix 4401 gateway.

Step 2 Click the icon at the bottom right of the Hunt section.

The Configure Hunt End screen appears. (See

Figure 14.)

SPA9000/M ediatrix® 440x ISDN Gateway Configuration Guide

Configuring the Mediatrix 440x Gate way

Figure 14 Configure Hunt End Screen

Step 3 In the Name field, enter the name of the hunt group. In this example, the name is hunt_isdn.

Step 4 In the Destination field, select ISDN-BRI1 and ISDN-BRI2 from the Suggestion drop-down list. (See

Figure 15.)

Figure 15

Step 5 Submit the changes.

Next, configure the gateway routing criteria. The Mediatrix 440x gateway will route incoming ISDN calls from the specified BRI port to the VoIP interface, and direct outgoing calls to the BRI port.

Step 6 In the Call Routing Config screen (see

section.

The Configure Route End screen appears. (See

SPA9000/M ediatrix® 440x ISDN Gatew ay Configuration Guide

Figure 13), click the icon at the bottom right of the Route

Figure 16.)

Configuring the Mediatrix 440x Gatew ay

Figure 16 Configure Route End Screen

Step 7 To create a route from SIP (sip-default) to one or more ISDN lines (for example, isdn-Bri1 or hunt_isdn),

do the following:

a. In the Source field, enter sip-default.

b. In the Destination field, enter hunt-hunt_isdn if using a hunt group, or isdn-Bri1 if using the

Mediatrix 4401.

Figure 17 shows these selections.

Figure 17 Configuring Source and Destination

Step 8 Click Submit

Step 9 Click Apply in the main Call Routing Config screen.

SPA9000/M ediatrix® 440x ISDN Gateway Configuration Guide

Configuring the Mediatrix 440x Gate way

Step 10 If necessary, restart the affected services, which are marked with an asterisk (*) on the System–Service

screen.

Configuring DTM F Transport

You must configure DTMF transport in the Mediatrix 440x gateway to guarantee that DTMF tones are properly sent to the SPA9000 so that services such as auto-attendant and voice mail work properly. To accomplish this, DTMF is sent through RTP using the out-of-band method.

To configure DTMF transport, complete the following steps:

Step 1 In the main configuration screen (see Figure 4), click Telephony, and then click CODECS.

Step 2 In the Misc section, under DTMF Transport, select Out-of-Band using RTP from the Transport Method

drop-down list. (See

Figure 18 Selecting DTM F Transport Met hod

Figure 18.)

Step 3 Click Submit.

SPA9000/M ediatrix® 440x ISDN Gatew ay Configuration Guide

Configuring the SPA9000

In the typical recommended configuration, the SPA9000 uses Line 1 to connect to the Internet telephone service provider (ITSP), Line 2 to connect to the SPA400, and Line 3 to connect to the Mediatrix 440x ISDN gateway.

To complete this configuration, perform the following steps:

Step 1 To define the Line 3 parameters, open the Voice tab of the SPA9000 configuration screen, enable

Admin–Advanced mode, select the Line 3 tab, and scroll down to the Proxy and Registration section.

Step 2 In the Proxy field, enter the Mediatrix 440x gateway IP address and the SIP port that was configured

previously for the Mediatrix 440x gateway.

In the current example, the address is 192.168.1.75 and the port number is 5060. (See

Figure 19 Identifying t he M ediatrix 440x Gatew ay

Configuring the SPA9000

Figure 19.)

Step 3 Select no from the Register drop-down list.

There is no need to register because this is defined as a peer-to-peer SIP trunk between the SPA9000 and the Mediatrix 440x gateway.

Step 4 Select yes from the Make Call Without Reg selection list.

Step 5 Select yes from the Ans Call Without Reg selection list.

Step 6 To set a SIP User ID to identify the Line internally, scroll to the Subscriber Information section and type

a name in the User ID field. (See

This example uses 1946.

Figure 20.)

SPA9000/M ediatrix® 440x ISDN Gateway Configuration Guide

Configuring the SPA9000

Step 7 In the SIP tab, scroll to the PBX Parameters section and type the dial-out criteria for this line in the Call

Figure 20 Sett ing User ID

Routing Rule field. (See Figure 21.)

This example specifies that when the SIP endpoint connected to a SPA9000 dials a number, different numbers cause the call to be routed as follows:

• 8—Routed through ISDN (Line 3–Mediatrix 440x gateway)

• 0—Routed to VoIP ITSP (Line 1)

• 9—Routed to the PSTN (Line 2–PSTN)

Figure 21 Setting the Call Routing Rule

Step 8 Again in the Line 3 tab, scroll to the Dial Plan section and update the dial plan of the Line in the Dial

Plan field to remove the “8” before sending the number out. (See

Figure 22 Configuring the Dial Plan

Step 9 Submit the changes.

Figure 22.)

Now, when any SPA9000 SIP endpoint dials “8” as a prefix before the external number, SPA9000 automatically routes the call through the Mediatrix 440x gateway to ISDN.

Note Make sure that the dial plan of your phone allows you to dial “8” (or whatever the number defined) as a

prefix to route the calls through the ISDN gateway.

SPA9000/M ediatrix® 440x ISDN Gatew ay Configuration Guide

Configuring the SPA9000

From this point, the system is considered configured. It should be able to receive and originate calls from/to ISDN. For reviewing the status of network connectivity and ISDN lines, and of the Mediatrix 440x gateway, check the Network and ISDN Status pages, respectively.

SPA9000/M ediatrix® 440x ISDN Gateway Configuration Guide

Appendix A— SIP Trace s of Various Scenarios

Appendix A— SIP Traces of Various Scenarios

This appendix provides SIP traces for the following scenarios:

•

Incoming ISDN Call to the SPA9000, page 17

• Outgoing ISDN Call from the SPA9000 Internal Endpoint, page 26

Incoming ISDN Call to the SPA9000

[4]<<192.168.1.75:5060(847) [4]<<192.168.1.75:5060(847) INVITE sip:914841622@192.168.1.10:5062 SIP/2.0 Via: SIP/2.0/UDP 192.168.1.75:5060;branch=z9hG4bKb332447a3 Content-Length: 297 To: sip:914841622@192.168.1.10:5062 From: sip:916611146@192.168.1.10:5062;tag=61348d706bce16c Call-ID: 8a9c309d9d1e3eed7e1bb0a641cc361f@192.168.1.10 CSeq: 101589334 INVITE Supported: timer Min-SE: 1800 Session-Expires: 3600 Allow: INVITE, ACK, BYE, CANCEL, REFER, NOTIFY Content-Type: application/sdp Contact: sip:916611146@192.168.1.75:5060 Supported: replaces User-Agent: MxSipApp/v1.1.3.19 MxSF/v3.2.1.2 v=0 o=MxSIP 1032267399288319200 1987802900286410546 IN IP4 192.168.1.75 s=c=IN IP4 192.168.1.75 t=0 0 a=sendrecv m=audio 5004 RTP/AVP 0 18 4 8 96 13 a=rtpmap:0 PCMU/8000 a=rtpmap:18 G729/8000 a=rtpmap:4 G723/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:96 telephone-event/8000 a=fmtp:96 0-15

[4]->192.168.1.75:5060(360) [4]->192.168.1.75:5060(360) SIP/2.0 100 Trying To: sip:914841622@192.168.1.10:5062 From: sip:916611146@192.168.1.10:5062;tag=61348d706bce16c Call-ID: 8a9c309d9d1e3eed7e1bb0a641cc361f@192.168.1.10 CSeq: 101589334 INVITE Via: SIP/2.0/UDP 192.168.1.75:5060;branch=z9hG4bKb332447a3 Server: Linksys/SPA9000-5.1.6(a) Allow-Events: talk, hold, conference, x-spa-cti Content-Length: 0

[pxy]->192.168.1.10:5083(956) [pxy]->192.168.1.10:5083(956) INVITE sip:aa@192.168.1.10:5083 SIP/2.0 Via: SIP/2.0/UDP 192.168.1.10:6060;branch=z9hG4bK-f79922d6 From: <sip:916611146@192.168.1.10:5062>;tag=40b28831d70d554eo4 To: <sip:aa@192.168.1.10:6060> Remote-Party-ID: <sip:916611146@192.168.1.10:5062>;screen=yes;party=calling

SPA9000/M ediatrix® 440x ISDN Gatew ay Configuration Guide

Appendix A— SIP Traces of Various Scenarios

Call-ID: adb9f02d-1cbead82@192.168.1.10 CSeq: 101 INVITE Max-Forwards: 70 Contact: "Mediatrix" <sip:916611146@192.168.1.10:6060> Expires: 240 User-Agent: Linksys/SPA9000-5.1.6(a) Allow-Events: talk, hold, conference, x-spa-cti Content-Length: 298 Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER Supported: x-sipura, replaces Content-Type: application/sdp v=0 o=proxy 1032267399288319200 1987802900286410546 IN IP4 192.168.1.75 s=c=IN IP4 192.168.1.10 t=0 0 a=sendrecv m=audio 16390 RTP/AVP 0 18 4 8 96 13 a=rtpmap:0 PCMU/8000 a=rtpmap:18 G729/8000 a=rtpmap:4 G723/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:96 telephone-event/8000 a=fmtp:96 0-15

[AA]: aa 1 auto answer delay = 5 [7:0]AAA ALLOC CALL (port=16394) [7:0]AAA:RTP Rx Up [pxy]<<127.0.0.1:5083(339) [pxy]<<127.0.0.1:5083(339) SIP/2.0 100 Trying To: <sip:aa@192.168.1.10:6060> From: <sip:916611146@192.168.1.10:5062>;tag=40b28831d70d554eo4 Call-ID: adb9f02d-1cbead82@192.168.1.10 CSeq: 101 INVITE Via: SIP/2.0/UDP 192.168.1.10:6060;branch=z9hG4bK-f79922d6 Server: Linksys/SPA9000-5.1.6(a) Allow-Events: talk, hold, conference, x-spa-cti Content-Length: 0

[pxy]<<127.0.0.1:5083(447) [pxy]<<127.0.0.1:5083(447) SIP/2.0 180 Ringing To: <sip:aa@192.168.1.10:6060>;tag=aca72a2bbbcb8b9ei7 From: <sip:916611146@192.168.1.10:5062>;tag=40b28831d70d554eo4 Call-ID: adb9f02d-1cbead82@192.168.1.10 CSeq: 101 INVITE Via: SIP/2.0/UDP 192.168.1.10:6060;branch=z9hG4bK-f79922d6 Server: Linksys/SPA9000-5.1.6(a) Remote-Party-ID: Auto Attendant <sip:aa@192.168.1.10:6060>;screen=yes;party=called Allow-Events: talk, hold, conference, x-spa-cti Content-Length: 0

pri--180-->BCC--180-->pub pri--180-->BCC--180-->pub [4]->192.168.1.75:5060(467) [4]->192.168.1.75:5060(467) SIP/2.0 180 Ringing To: sip:914841622@192.168.1.10:5062;tag=346072efc18339aai4 From: sip:916611146@192.168.1.10:5062;tag=61348d706bce16c Call-ID: 8a9c309d9d1e3eed7e1bb0a641cc361f@192.168.1.10 CSeq: 101589334 INVITE Via: SIP/2.0/UDP 192.168.1.75:5060;branch=z9hG4bKb332447a3 Server: Linksys/SPA9000-5.1.6(a)

SPA9000/M ediatrix® 440x ISDN Gateway Configuration Guide

Appendix A— SIP Trace s of Various Scenarios

Remote-Party-ID: "Mediatrix"<sip:1946@192.168.1.75:5060>;screen=yes;party=called Allow-Events: talk, hold, conference, x-spa-cti Content-Length: 0

[pxy]<<127.0.0.1:5083(869) [pxy]<<127.0.0.1:5083(869) SIP/2.0 200 OK To: <sip:aa@192.168.1.10:6060>;tag=aca72a2bbbcb8b9ei7 From: <sip:916611146@192.168.1.10:5062>;tag=40b28831d70d554eo4 Call-ID: adb9f02d-1cbead82@192.168.1.10 CSeq: 101 INVITE Via: SIP/2.0/UDP 192.168.1.10:6060;branch=z9hG4bK-f79922d6 Contact: Auto Attendant <sip:aa@192.168.1.10:5083> Server: Linksys/SPA9000-5.1.6(a) Remote-Party-ID: Auto Attendant <sip:aa@192.168.1.10:6060>;screen=yes;party=called Allow-Events: talk, hold, conference, x-spa-cti Content-Length: 248 Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER Supported: x-sipura, replaces Content-Type: application/sdp v=0 o=- 62798 62798 IN IP4 192.168.1.10 s=c=IN IP4 192.168.1.10 t=0 0 m=audio 16394 RTP/AVP 0 100 96 a=rtpmap:0 PCMU/8000 a=rtpmap:100 NSE/8000 a=fmtp:100 192-193 a=rtpmap:96 telephone-event/8000 a=fmtp:96 0-15 a=ptime:30 a=sendrecv

[pxy]->192.168.1.10:5083(455) [pxy]->192.168.1.10:5083(455) ACK sip:aa@192.168.1.10:5083 SIP/2.0 Via: SIP/2.0/UDP 192.168.1.10:6060;branch=z9hG4bK-ee709ed9 From: <sip:916611146@192.168.1.10:5062>;tag=40b28831d70d554eo4 To: <sip:aa@192.168.1.10:6060>;tag=aca72a2bbbcb8b9ei7 Call-ID: adb9f02d-1cbead82@192.168.1.10 CSeq: 101 ACK Max-Forwards: 70 Contact: "Mediatrix" <sip:916611146@192.168.1.10:6060> User-Agent: Linksys/SPA9000-5.1.6(a) Allow-Events: talk, hold, conference, x-spa-cti Content-Length: 0

CC:Connected [7:0]AAA:Create AA Object [7:0]AAA:RTP Tx Up (pt=0->c0a8010a:16390) [4]->192.168.1.75:5060(902) [4]->192.168.1.75:5060(902) SIP/2.0 200 OK To: sip:914841622@192.168.1.10:5062;tag=346072efc18339aai4;ref=aa From: sip:916611146@192.168.1.10:5062;tag=61348d706bce16c Call-ID: 8a9c309d9d1e3eed7e1bb0a641cc361f@192.168.1.10 CSeq: 101589334 INVITE Via: SIP/2.0/UDP 192.168.1.75:5060;branch=z9hG4bKb332447a3 Contact: "Mediatrix" <sip:914841622@192.168.1.10:5062> Server: Linksys/SPA9000-5.1.6(a) Remote-Party-ID: "Mediatrix" <sip:1946@192.168.1.75:5060>;screen=yes;party=called Allow-Events: talk, hold, conference, x-spa-cti Content-Length: 248

SPA9000/M ediatrix® 440x ISDN Gatew ay Configuration Guide

Appendix A— SIP Traces of Various Scenarios

Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER Supported: x-sipura, replaces Content-Type: application/sdp v=0 o=- 62798 62798 IN IP4 192.168.1.10 s=c=IN IP4 192.168.1.10 t=0 0 m=audio 16388 RTP/AVP 0 100 96 a=rtpmap:0 PCMU/8000 a=rtpmap:100 NSE/8000 a=fmtp:100 192-193 a=rtpmap:96 telephone-event/8000 a=fmtp:96 0-15 a=ptime:30a=sendrecv

[0:0]RTP Rx 1st PKT @16394(3) [4]<<192.168.1.75:5060(410) [4]<<192.168.1.75:5060(410) ACK sip:914841622@192.168.1.10:5062 SIP/2.0 Via: SIP/2.0/UDP 192.168.1.75:5060;branch=z9hG4bK1eb32ba63 Content-Length: 0 To: sip:914841622@192.168.1.10:5062;tag=346072efc18339aai4 From: sip:916611146@192.168.1.10:5062;tag=61348d706bce16c Call-ID: 8a9c309d9d1e3eed7e1bb0a641cc361f@192.168.1.10 CSeq: 101589334 ACK Contact: sip:916611146@192.168.1.75:5060 User-Agent: MxSipApp/v1.1.3.19 MxSF/v3.2.1.2

[2]RegOK. NextReg in 28 (1) AVT Rx Start Tone: 1 AVT Rx End Tone AVT Rx Start Tone: 1 AVT Rx End Tone AVT Rx Start Tone: 0 AVT Rx End Tone AVT Rx Start Tone: 11 AVT Rx End Tone [AA]: xfer to target=110 CC:BlndXferTgt:110 Calling:110@192.168.1.10:6060 [7:0]AAA Rel Call [7:0]AAA:Destory SAA OBJ [pxy]<<127.0.0.1:5083(556) [pxy]<<127.0.0.1:5083(556) REFER sip:916611146@192.168.1.10:6060 SIP/2.0 Via: SIP/2.0/UDP 192.168.1.10:5083;branch=z9hG4bK-2bd7f3b From: <sip:aa@192.168.1.10:6060>;tag=aca72a2bbbcb8b9ei7 To: <sip:916611146@192.168.1.10:5062>;tag=40b28831d70d554eo4 Referred-By: Auto Attendant <sip:aa@192.168.1.10:6060> Call-ID: adb9f02d-1cbead82@192.168.1.10 CSeq: 101 REFER Max-Forwards: 70 Contact: Auto Attendant <sip:aa@192.168.1.10:5083> Refer-To: <sip:110@192.168.1.10:6060> User-Agent: Linksys/SPA9000-5.1.6(a) Allow-Events: talk, hold, conference, x-spa-cti Content-Length: 0

pri--REFER-->BCC:target=110@192.168.1.10:6060 pri--REFER-->BCC:target=110@192.168.1.10:6060 [pxy]->192.168.1.169:5060(1037) [pxy]->192.168.1.169:5060(1037) INVITE sip:110@192.168.1.169:5060 SIP/2.0

SPA9000/M ediatrix® 440x ISDN Gateway Configuration Guide

Appendix A— SIP Trace s of Various Scenarios

Via: SIP/2.0/UDP 192.168.1.10:6060;branch=z9hG4bK-135623b9 From: <sip:916611146@192.168.1.10:5062>;tag=29306e71561ea8abo4 To: <sip:110@192.168.1.10:6060> Remote-Party-ID: <sip:916611146@192.168.1.10:5062>;screen=yes;party=calling Alert-Info: ringback Call-ID: a0dabe69-b49bd913@192.168.1.10 CSeq: 101 INVITE Max-Forwards: 70 Contact: "Mediatrix" <sip:916611146@192.168.1.10:6060> Expires: 240 Referred-By: Auto Attendant <sip:aa@192.168.1.10:6060> User-Agent: Linksys/SPA9000-5.1.6(a) Allow-Events: talk, hold, conference, x-spa-cti Content-Length: 298 Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER Supported: x-sipura, replaces Content-Type: application/sdp v=0 o=proxy 1032267399288319200 1987802900286410546 IN IP4 192.168.1.75 s=c=IN IP4 192.168.1.10 t=0 0 a=sendrecv m=audio 16390 RTP/AVP 0 18 4 8 96 13 a=rtpmap:0 PCMU/8000 a=rtpmap:18 G729/8000 a=rtpmap:4 G723/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:96 telephone-event/8000 a=fmtp:96 0-15

[pxy]->127.0.0.1:5083(427) [pxy]->127.0.0.1:5083(427) SIP/2.0 202 Accepted To: <sip:916611146@192.168.1.10:5062>;tag=40b28831d70d554eo4 From: <sip:aa@192.168.1.10:6060>;tag=aca72a2bbbcb8b9ei7 Call-ID: adb9f02d-1cbead82@192.168.1.10 CSeq: 101 REFER Via: SIP/2.0/UDP 192.168.1.10:5083;branch=z9hG4bK-2bd7f3b Contact: "Mediatrix" <sip:1946@192.168.1.10:6060;transport=udp> Server: Linksys/SPA9000-5.1.6(a) Allow-Events: talk, hold, conference, x-spa-cti Content-Length: 0

[pxy]<<192.168.1.169:5060(288) [pxy]<<192.168.1.169:5060(288) SIP/2.0 100 Trying To: <sip:110@192.168.1.10:6060> From: <sip:916611146@192.168.1.10:5062>;tag=29306e71561ea8abo4 Call-ID: a0dabe69-b49bd913@192.168.1.10 CSeq: 101 INVITE Via: SIP/2.0/UDP 192.168.1.10:6060;branch=z9hG4bK-135623b9 Server: Linksys/SPA942-5.1.10 Content-Length: 0

[pxy]<<192.168.1.169:5060(412) [pxy]<<192.168.1.169:5060(412) SIP/2.0 183 Session Progress To: <sip:110@192.168.1.10:6060>;tag=aacea16d26d547ci0 From: <sip:916611146@192.168.1.10:5062>;tag=29306e71561ea8abo4 Call-ID: a0dabe69-b49bd913@192.168.1.10 CSeq: 101 INVITE Via: SIP/2.0/UDP 192.168.1.10:6060;branch=z9hG4bK-135623b9 Server: Linksys/SPA942-5.1.10

SPA9000/M ediatrix® 440x ISDN Gatew ay Configuration Guide

Appendix A— SIP Traces of Various Scenarios

Remote-Party-ID: <sip:110@192.168.1.10:6060>;screen=yes;party=called Content-Length: 0 Allow-Events: dialog

pri--18x-->BCC(conn) pri--18x-->BCC(conn) [pxy]<<192.168.1.169:5060(768) [pxy]<<192.168.1.169:5060(768) SIP/2.0 200 OK To: <sip:110@192.168.1.10:6060>;tag=aacea16d26d547ci0 From: <sip:916611146@192.168.1.10:5062>;tag=29306e71561ea8abo4 Call-ID: a0dabe69-b49bd913@192.168.1.10 CSeq: 101 INVITE Via: SIP/2.0/UDP 192.168.1.10:6060;branch=z9hG4bK-135623b9 Contact: <sip:110@192.168.1.169:5060> Server: Linksys/SPA942-5.1.10 Remote-Party-ID: <sip:110@192.168.1.10:6060>;screen=yes;party=called Content-Length: 203 Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER, SUBSCRIBE Allow-Events: dialog Supported: replaces Content-Type: application/sdp v=0 o=- 62747 62747 IN IP4 192.168.1.169 s=c=IN IP4 192.168.1.169 t=0 0 m=audio 16480 RTP/AVP 0 96 a=rtpmap:0 PCMU/8000 a=rtpmap:96 telephone-event/8000 a=fmtp:96 0-15 a=ptime:30 a=sendrecv

[pxy]->192.168.1.169:5060(457) [pxy]->192.168.1.169:5060(457) ACK sip:110@192.168.1.169:5060 SIP/2.0 Via: SIP/2.0/UDP 192.168.1.10:6060;branch=z9hG4bK-f39d492f From: <sip:916611146@192.168.1.10:5062>;tag=29306e71561ea8abo4 To: <sip:110@192.168.1.10:6060>;tag=aacea16d26d547ci0 Call-ID: a0dabe69-b49bd913@192.168.1.10 CSeq: 101 ACK Max-Forwards: 70 Contact: "Mediatrix" <sip:916611146@192.168.1.10:6060> User-Agent: Linksys/SPA9000-5.1.6(a) Allow-Events: talk, hold, conference, x-spa-cti Content-Length: 0

ReferTarget answers BCC INVITE ReferTarget answers BCC INVITE pri(ReferTarget)--200-->BCC--reINVITE-->pub pri(ReferTarget)--200-->BCC--reINVITE-->pub [4]->192.168.1.75:5060(827) [4]->192.168.1.75:5060(827) INVITE sip:916611146@192.168.1.75:5060 SIP/2.0 Via: SIP/2.0/UDP 192.168.1.10:5062;branch=z9hG4bK-7625e35 From: <sip:914841622@192.168.1.10:5062>;tag=346072efc18339aai4;ref=110 To: <sip:916611146@192.168.1.10:5062>;tag=61348d706bce16c Remote-Party-ID: "Mediatrix" <sip:1946@192.168.1.75:5060>;screen=yes;party=called Call-ID: 8a9c309d9d1e3eed7e1bb0a641cc361f@192.168.1.10 CSeq: 101 INVITE Max-Forwards: 70 Contact: "Mediatrix" <sip:914841622@192.168.1.10:5062> Expires: 30

SPA9000/M ediatrix® 440x ISDN Gateway Configuration Guide

Appendix A— SIP Trace s of Various Scenarios

User-Agent: Linksys/SPA9000-5.1.6(a) Allow-Events: talk, hold, conference, x-spa-cti Content-Length: 202 Content-Type: application/sdp v=0 o=- 62747 62747 IN IP4 192.168.1.169 s=c=IN IP4 192.168.1.10 t=0 0 m=audio 16388 RTP/AVP 0 96 a=rtpmap:0 PCMU/8000 a=rtpmap:96 telephone-event/8000 a=fmtp:96 0-15 a=ptime:30 a=sendrecv

[4]<<192.168.1.75:5060(351) [4]<<192.168.1.75:5060(351) SIP/2.0 100 Trying Call-ID: 8a9c309d9d1e3eed7e1bb0a641cc361f@192.168.1.10 CSeq: 101 INVITE From: <sip:914841622@192.168.1.10:5062>;tag=346072efc18339aai4;ref=110 To: <sip:916611146@192.168.1.10:5062>;tag=61348d706bce16c Via: SIP/2.0/UDP 192.168.1.10:5062;branch=z9hG4bK-7625e35 Content-Length: 0 User-Agent: MxSipApp/v1.1.3.19 MxSF/v3.2.1.2

[4]<<192.168.1.75:5060(748) [4]<<192.168.1.75:5060(748) SIP/2.0 200 OK Call-ID: 8a9c309d9d1e3eed7e1bb0a641cc361f@192.168.1.10 CSeq: 101 INVITE From: <sip:914841622@192.168.1.10:5062>;tag=346072efc18339aai4;ref=110 To: <sip:916611146@192.168.1.10:5062>;tag=61348d706bce16c Via: SIP/2.0/UDP 192.168.1.10:5062;branch=z9hG4bK-7625e35 Content-Length: 220 Session-Expires: 3600;refresher=uas Allow: INVITE, ACK, BYE, CANCEL, REFER, NOTIFY Content-Type: application/sdp Supported: replaces Contact: sip:916611146@192.168.1.75:5060 User-Agent: MxSipApp/v1.1.3.19 MxSF/v3.2.1.2 v=0 o=MxSIP 1032267399288319200 1987802900286410547 IN IP4 192.168.1.75 s=c=IN IP4 192.168.1.75 t=0 0 a=sendrecvm=audio 5004 RTP/AVP 0 96 a=rtpmap:0 PCMU/8000 a=rtpmap:96 telephone-event/8000 a=fmtp:96 0-15

[4]->192.168.1.75:5060(489) [4]->192.168.1.75:5060(489) ACK sip:916611146@192.168.1.75:5060 SIP/2.0 Via: SIP/2.0/UDP 192.168.1.10:5062;branch=z9hG4bK-27dddced From: <sip:914841622@192.168.1.10:5062>;tag=346072efc18339aai4;ref=110 To: <sip:916611146@192.168.1.10:5062>;tag=61348d706bce16c Call-ID: 8a9c309d9d1e3eed7e1bb0a641cc361f@192.168.1.10 CSeq: 101 ACK Max-Forwards: 70 Contact: "Mediatrix" <sip:914841622@192.168.1.10:5062> User-Agent: Linksys/SPA9000-5.1.6(a) Allow-Events: talk, hold, conference, x-spa-cti

SPA9000/M ediatrix® 440x ISDN Gatew ay Configuration Guide

Appendix A— SIP Traces of Various Scenarios

Content-Length: 0 [pxy]->192.168.1.169:5060(809) [pxy]->192.168.1.169:5060(809) INVITE sip:110@192.168.1.169:5060 SIP/2.0 Via: SIP/2.0/UDP 192.168.1.10:6060;branch=z9hG4bK-a1bdad95 From: <sip:916611146@192.168.1.10:5062>;tag=29306e71561ea8abo4 To: <sip:110@192.168.1.10:6060>;tag=aacea16d26d547ci0 Remote-Party-ID: <sip:916611146@192.168.1.10:5062>;screen=yes;party=calling Call-ID: a0dabe69-b49bd913@192.168.1.10 CSeq: 102 INVITE Max-Forwards: 70 Contact: "Mediatrix" <sip:916611146@192.168.1.10:6060> Expires: 30 User-Agent: Linksys/SPA9000-5.1.6(a) Allow-Events: talk, hold, conference, x-spa-cti Content-Length: 221 Content-Type: application/sdp v=0 o=proxy 1032267399288319200 1987802900286410547 IN IP4 192.168.1.75 s=c=IN IP4 192.168.1.10 t=0 0 a=sendrecv m=audio 16390 RTP/AVP 0 96 a=rtpmap:0 PCMU/8000 a=rtpmap:96 telephone-event/8000 a=fmtp:96 0-15

[pxy]<<192.168.1.169:5060(581) [pxy]<<192.168.1.169:5060(581) SIP/2.0 200 OK To: <sip:110@192.168.1.10:6060>;tag=aacea16d26d547ci0 From: <sip:916611146@192.168.1.10:5062>;tag=29306e71561ea8abo4 Call-ID: a0dabe69-b49bd913@192.168.1.10 CSeq: 102 INVITE Via: SIP/2.0/UDP 192.168.1.10:6060;branch=z9hG4bK-a1bdad95 Contact: <sip:110@192.168.1.169:5060> Server: Linksys/SPA942-5.1.10 Content-Length: 203 Content-Type: application/sdp v=0 o=- 63056 63056 IN IP4 192.168.1.169 s=c=IN IP4 192.168.1.169 t=0 0 m=audio 16480 RTP/AVP 0 96 a=rtpmap:0 PCMU/8000 a=rtpmap:96 telephone-event/8000 a=fmtp:96 0-15 a=ptime:30 a=sendrecv

[pxy]->192.168.1.169:5060(457) [pxy]->192.168.1.169:5060(457) ACK sip:110@192.168.1.169:5060 SIP/2.0 Via: SIP/2.0/UDP 192.168.1.10:6060;branch=z9hG4bK-ad7bd510 From: <sip:916611146@192.168.1.10:5062>;tag=29306e71561ea8abo4 To: <sip:110@192.168.1.10:6060>;tag=aacea16d26d547ci0 Call-ID: a0dabe69-b49bd913@192.168.1.10 CSeq: 102 ACK Max-Forwards: 70 Contact: "Mediatrix" <sip:916611146@192.168.1.10:6060> User-Agent: Linksys/SPA9000-5.1.6(a) Allow-Events: talk, hold, conference, x-spa-cti

SPA9000/M ediatrix® 440x ISDN Gateway Configuration Guide

Appendix A— SIP Trace s of Various Scenarios

Content-Length: 0

ReferTarget answers BCC INVITE ReferTarget answers BCC INVITE pri(ReferTarget)--200-->BCC--reINVITE-->pub (done) pri(ReferTarget)--200-->BCC--reINVITE-->pub (done) [pxy]<<127.0.0.1:5083(406) [pxy]<<127.0.0.1:5083(406) BYE sip:916611146@192.168.1.10:6060 SIP/2.0 Via: SIP/2.0/UDP 192.168.1.10:5083;branch=z9hG4bK-4c6ddc2e From: <sip:aa@192.168.1.10:6060>;tag=aca72a2bbbcb8b9ei7 To: <sip:916611146@192.168.1.10:5062>;tag=40b28831d70d554eo4 Call-ID: adb9f02d-1cbead82@192.168.1.10 CSeq: 102 BYE Max-Forwards: 70 User-Agent: Linksys/SPA9000-5.1.6(a) Allow-Events: talk, hold, conference, x-spa-cti Content-Length: 0

[pxy]->127.0.0.1:5083(355) [pxy]->127.0.0.1:5083(355) SIP/2.0 200 OK To: <sip:916611146@192.168.1.10:5062>;tag=40b28831d70d554eo4 From: <sip:aa@192.168.1.10:6060>;tag=aca72a2bbbcb8b9ei7 Call-ID: adb9f02d-1cbead82@192.168.1.10 CSeq: 102 BYE Via: SIP/2.0/UDP 192.168.1.10:5083;branch=z9hG4bK-4c6ddc2e Server: Linksys/SPA9000-5.1.6(a) Allow-Events: talk, hold, conference, x-spa-cti Content-Length: 0

[pxy]<<192.168.1.169:5060(355) [pxy]<<192.168.1.169:5060(355) BYE sip:916611146@192.168.1.10:6060 SIP/2.0 Via: SIP/2.0/UDP 192.168.1.169:5060;branch=z9hG4bK-a5a0daf6 From: <sip:110@192.168.1.10:6060>;tag=aacea16d26d547ci0 To: <sip:916611146@192.168.1.10:5062>;tag=29306e71561ea8abo4 Call-ID: a0dabe69-b49bd913@192.168.1.10 CSeq: 101 BYE Max-Forwards: 70 User-Agent: Linksys/SPA942-5.1.10 Content-Length: 0

private side ends the call private side ends the call [pxy]->192.168.1.169:5060(356) [pxy]->192.168.1.169:5060(356) SIP/2.0 200 OK To: <sip:916611146@192.168.1.10:5062>;tag=29306e71561ea8abo4 From: <sip:110@192.168.1.10:6060>;tag=aacea16d26d547ci0 Call-ID: a0dabe69-b49bd913@192.168.1.10 CSeq: 101 BYE Via: SIP/2.0/UDP 192.168.1.169:5060;branch=z9hG4bK-a5a0daf6 Server: Linksys/SPA9000-5.1.6(a) Allow-Events: talk, hold, conference, x-spa-cti Content-Length: 0

BCC:Ended [4]->192.168.1.75:5060(432) [4]->192.168.1.75:5060(432) BYE sip:916611146@192.168.1.75:5060 SIP/2.0 Via: SIP/2.0/UDP 192.168.1.10:5062;branch=z9hG4bK-967510e From: <sip:914841622@192.168.1.10:5062>;tag=346072efc18339aai4;ref=110 To: <sip:916611146@192.168.1.10:5062>;tag=61348d706bce16c

SPA9000/M ediatrix® 440x ISDN Gatew ay Configuration Guide

Appendix A— SIP Traces of Various Scenarios

Call-ID: 8a9c309d9d1e3eed7e1bb0a641cc361f@192.168.1.10 CSeq: 102 BYE Max-Forwards: 70 User-Agent: Linksys/SPA9000-5.1.6(a) Allow-Events: talk, hold, conference, x-spa-cti Content-Length: 0

[4]<<192.168.1.75:5060(365) [4]<<192.168.1.75:5060(365) SIP/2.0 200 OKCall-ID: 8a9c309d9d1e3eed7e1bb0a641cc361f@192.168.1.10CSeq: 102 BYE From: <sip:914841622@192.168.1.10:5062>;tag=346072efc18339aai4;ref=110 To: <sip:916611146@192.168.1.10:5062>;tag=61348d706bce16c Via: SIP/2.0/UDP 192.168.1.10:5062;branch=z9hG4bK-967510e Content-Length: 0 Supported: replaces User-Agent: MxSipApp/v1.1.3.19 MxSF/v3.2.1.2

Outgoing ISDN Call from the SPA9000 Internal Endpoint

[pxy]<<192.168.1.169:5060(1070) [pxy]<<192.168.1.169:5060(1070) INVITE sip:8648204822@192.168.1.10:6060 SIP/2.0 Via: SIP/2.0/UDP 192.168.1.169:5060;branch=z9hG4bK-a9b5b9f7 From: <sip:110@192.168.1.10:6060>;tag=22878a81540c2767o0 To: <sip:8648204822@192.168.1.10:6060> Remote-Party-ID: <sip:110@192.168.1.10:6060>;screen=yes;party=calling Call-ID: b7719409-afaa6b7f@192.168.1.169 CSeq: 101 INVITE Max-Forwards: 70 Contact: <sip:110@192.168.1.169:5060>;+sip.instance="<00000000-0000-0000-0000-000E08DAFB1F>" Expires: 240 User-Agent: Linksys/SPA942-5.1.10 Content-Length: 395 Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER, SUBSCRIBE Allow-Events: dialog Supported: replaces Content-Type: application/sdp v=0 o=- 91509 91509 IN IP4 192.168.1.169 s=c=IN IP4 192.168.1.169 t=0 0 m=audio 16482 RTP/AVP 0 2 4 8 18 96 97 98 101 a=rtpmap:0 PCMU/8000 a=rtpmap:2 G726-32/8000 a=rtpmap:4 G723/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:18 G729a/8000 a=rtpmap:96 G726-40/8000 a=rtpmap:97 G726-24/8000 a=rtpmap:98 G726-16/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=ptime:30 a=sendrecv

[BCC]CallRoute:L38648204822 [BCC]CallRoute:L38648204822 [pxy]->192.168.1.169:5060(345) [pxy]->192.168.1.169:5060(345) SIP/2.0 100 Trying

SPA9000/M ediatrix® 440x ISDN Gateway Configuration Guide

Appendix A— SIP Trace s of Various Scenarios

To: <sip:8648204822@192.168.1.10:6060> From: <sip:110@192.168.1.10:6060>;tag=22878a81540c2767o0 Call-ID: b7719409-afaa6b7f@192.168.1.169 CSeq: 101 INVITE Via: SIP/2.0/UDP 192.168.1.169:5060;branch=z9hG4bK-a9b5b9f7 Server: Linksys/SPA9000-5.1.6(a) Allow-Events: talk, hold, conference, x-spa-cti Content-Length: 0

pri-->INVITE-->pub pri-->INVITE-->pub Calling:648204822@192.168.1.75:5060 [4]->192.168.1.75:5060(1083) [4]->192.168.1.75:5060(1083) INVITE sip:648204822@192.168.1.75:5060 SIP/2.0 Via: SIP/2.0/UDP 192.168.1.10:5062;branch=z9hG4bK-302d0544 From: "Mediatrix" <sip:1946@192.168.1.75:5060>;tag=1be50f305ef95759o4;ref=110 To: <sip:648204822@192.168.1.75:5060> Remote-Party-ID: "Mediatrix" <sip:1946@192.168.1.75:5060>;screen=yes;party=calling Call-ID: 24a3813c-5308acbd@192.168.1.10 CSeq: 101 INVITE Max-Forwards: 70 Contact: "Mediatrix" <sip:1946@192.168.1.10:5062> Expires: 240 User-Agent: Linksys/SPA9000-5.1.6(a) Allow-Events: talk, hold, conference, x-spa-cti Content-Length: 394 Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER Supported: x-sipura, replaces Content-Type: application/sdp v=0 o=- 91509 91509 IN IP4 192.168.1.169 s=c=IN IP4 192.168.1.10 t=0 0 m=audio 16396 RTP/AVP 0 2 4 8 18 96 97 98 101 a=rtpmap:0 PCMU/8000 a=rtpmap:2 G726-32/8000 a=rtpmap:4 G723/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:18 G729a/8000 a=rtpmap:96 G726-40/8000 a=rtpmap:97 G726-24/8000 a=rtpmap:98 G726-16/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=ptime:30 a=sendrecv

[4]<<192.168.1.75:5060(344) [4]<<192.168.1.75:5060(344) SIP/2.0 100 Trying Call-ID: 24a3813c-5308acbd@192.168.1.10 CSeq: 101 INVITE From: "Mediatrix" <sip:1946@192.168.1.75:5060>;tag=1be50f305ef95759o4;ref=110 To: <sip:648204822@192.168.1.75:5060>;tag=c1f2604c716fd1e Via: SIP/2.0/UDP 192.168.1.10:5062;branch=z9hG4bK-302d0544 Content-Length: 0 User-Agent: MxSipApp/v1.1.3.19 MxSF/v3.2.1.2

[4]<<192.168.1.75:5060(725) [4]<<192.168.1.75:5060(725) SIP/2.0 183 Session Progress Call-ID: 24a3813c-5308acbd@192.168.1.10

SPA9000/M ediatrix® 440x ISDN Gatew ay Configuration Guide

Appendix A— SIP Traces of Various Scenarios

CSeq: 101 INVITE From: "Mediatrix" <sip:1946@192.168.1.75:5060>;tag=1be50f305ef95759o4;ref=110 To: <sip:648204822@192.168.1.75:5060>;tag=c1f2604c716fd1e Via: SIP/2.0/UDP 192.168.1.10:5062;branch=z9hG4bK-302d0544 Content-Length: 296 Content-Type: application/sdp Contact: sip:648204822@192.168.1.75:5060 User-Agent: MxSipApp/v1.1.3.19 MxSF/v3.2.1.2 v=0 o=MxSIP 1256160840606035694 47734327189664372 IN IP4 192.168.1.75 s=c=IN IP4 192.168.1.75 t=0 0 a=sendrecvm=audio 5004 RTP/AVP 0 18 4 8 101 a=rtpmap:0 PCMU/8000 a=rtpmap:18 G729a/8000 a=rtpmap:4 G723/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15

BCC:Ringback/CallProgress 5 [pxy]->192.168.1.169:5060(883) [pxy]->192.168.1.169:5060(883) SIP/2.0 183 Session ProgressTo: <sip:8648204822@192.168.1.10:6060>;tag=2cce67a3fd752181i4 From: <sip:110@192.168.1.10:6060>;tag=22878a81540c2767o0 Call-ID: b7719409-afaa6b7f@192.168.1.169 CSeq: 101 INVITE Via: SIP/2.0/UDP 192.168.1.169:5060;branch=z9hG4bK-a9b5b9f7 Server: Linksys/SPA9000-5.1.6(a) Remote-Party-ID: <sip:8648204822@192.168.1.10:6060>;screen=yes;party=called Allow-Events: talk, hold, conference, x-spa-cti Content-Length: 297 Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER Supported: x-sipura, replaces Content-Type: application/sdp v=0 o=proxy 1256160840606035694 47734327189664372 IN IP4 192.168.1.75 s=c=IN IP4 192.168.1.10 t=0 0 a=sendrecv m=audio 16398 RTP/AVP 0 18 4 8 101 a=rtpmap:0 PCMU/8000 a=rtpmap:18 G729a/8000 a=rtpmap:4 G723/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15

[4]<<192.168.1.75:5060(716) [4]<<192.168.1.75:5060(716) SIP/2.0 180 Ringing Call-ID: 24a3813c-5308acbd@192.168.1.10 CSeq: 101 INVITE From: "Mediatrix" <sip:1946@192.168.1.75:5060>;tag=1be50f305ef95759o4;ref=110 To: <sip:648204822@192.168.1.75:5060>;tag=c1f2604c716fd1e Via: SIP/2.0/UDP 192.168.1.10:5062;branch=z9hG4bK-302d0544 Content-Length: 296 Content-Type: application/sdp Contact: sip:648204822@192.168.1.75:5060 User-Agent: MxSipApp/v1.1.3.19 MxSF/v3.2.1.2 v=0 o=MxSIP 1256160840606035694 47734327189664372 IN IP4 192.168.1.75

SPA9000/M ediatrix® 440x ISDN Gateway Configuration Guide

Appendix A— SIP Trace s of Various Scenarios

s=c=IN IP4 192.168.1.75 t=0 0 a=sendrecv m=audio 5004 RTP/AVP 0 18 4 8 101 a=rtpmap:0 PCMU/8000 a=rtpmap:18 G729a/8000 a=rtpmap:4 G723/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15

BCC:Ringback/CallProgress 5 [pxy]->192.168.1.169:5060(883) [pxy]->192.168.1.169:5060(883) SIP/2.0 183 Session Progress To: <sip:8648204822@192.168.1.10:6060>;tag=2cce67a3fd752181i4 From: <sip:110@192.168.1.10:6060>;tag=22878a81540c2767o0 Call-ID: b7719409-afaa6b7f@192.168.1.169 CSeq: 101 INVITE Via: SIP/2.0/UDP 192.168.1.169:5060;branch=z9hG4bK-a9b5b9f7 Server: Linksys/SPA9000-5.1.6(a) Remote-Party-ID: <sip:8648204822@192.168.1.10:6060>;screen=yes;party=called Allow-Events: talk, hold, conference, x-spa-cti Content-Length: 297 Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER Supported: x-sipura, replaces Content-Type: application/sdp v=0 o=proxy 1256160840606035694 47734327189664372 IN IP4 192.168.1.75 s=c=IN IP4 192.168.1.10 t=0 0 a=sendrecv m=audio 16398 RTP/AVP 0 18 4 8 101 a=rtpmap:0 PCMU/8000 a=rtpmap:18 G729a/8000 a=rtpmap:4 G723/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15

[4]<<192.168.1.75:5060(817) [4]<<192.168.1.75:5060(817) SIP/2.0 200 OK Call-ID: 24a3813c-5308acbd@192.168.1.10 CSeq: 101 INVITE From: "Mediatrix" <sip:1946@192.168.1.75:5060>;tag=1be50f305ef95759o4;ref=110 To: <sip:648204822@192.168.1.75:5060>;tag=c1f2604c716fd1e Via: SIP/2.0/UDP 192.168.1.10:5062;branch=z9hG4bK-302d0544 Content-Length: 296 Session-Expires: 3600;refresher=uas Allow: INVITE, ACK, BYE, CANCEL, REFER, NOTIFY Content-Type: application/sdpSupported: replaces Contact: sip:648204822@192.168.1.75:5060 User-Agent: MxSipApp/v1.1.3.19 MxSF/v3.2.1.2 v=0 o=MxSIP 1256160840606035694 47734327189664372 IN IP4 192.168.1.75 s=c=IN IP4 192.168.1.75 t=0 0 a=sendrecv m=audio 5004 RTP/AVP 0 18 4 8 101 a=rtpmap:0 PCMU/8000

SPA9000/M ediatrix® 440x ISDN Gatew ay Configuration Guide

Appendix A— SIP Traces of Various Scenarios

a=rtpmap:18 G729a/8000 a=rtpmap:4 G723/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15

[4]->192.168.1.75:5060(476) [4]->192.168.1.75:5060(476) ACK sip:648204822@192.168.1.75:5060 SIP/2.0 Via: SIP/2.0/UDP 192.168.1.10:5062;branch=z9hG4bK-acc9ba86 From: "Mediatrix" <sip:1946@192.168.1.75:5060>;tag=1be50f305ef95759o4;ref=110 To: <sip:648204822@192.168.1.75:5060>;tag=c1f2604c716fd1e Call-ID: 24a3813c-5308acbd@192.168.1.10 CSeq: 101 ACK Max-Forwards: 70 Contact: "Mediatrix" <sip:1946@192.168.1.10:5062> User-Agent: Linksys/SPA9000-5.1.6(a) Allow-Events: talk, hold, conference, x-spa-cti Content-Length: 0

pub--200-->BCC--200-->pri(from calling) pub--200-->BCC--200-->pri(from calling) [pxy]->192.168.1.169:5060(925) [pxy]->192.168.1.169:5060(925) SIP/2.0 200 OK To: <sip:8648204822@192.168.1.10:6060>;tag=2cce67a3fd752181i4 From: <sip:110@192.168.1.10:6060>;tag=22878a81540c2767o0 Call-ID: b7719409-afaa6b7f@192.168.1.169 CSeq: 101 INVITE Via: SIP/2.0/UDP 192.168.1.169:5060;branch=z9hG4bK-a9b5b9f7 Contact: "Mediatrix" <sip:648204822@192.168.1.10:6060> Server: Linksys/SPA9000-5.1.6(a) Remote-Party-ID: <sip:8648204822@192.168.1.10:6060>;screen=yes;party=called Allow-Events: talk, hold, conference, x-spa-cti Content-Length: 297 Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER Supported: x-sipura, replaces Content-Type: application/sdp v=0 o=proxy 1256160840606035694 47734327189664372 IN IP4 192.168.1.75 s=c=IN IP4 192.168.1.10 t=0 0 a=sendrecv m=audio 16398 RTP/AVP 0 18 4 8 101 a=rtpmap:0 PCMU/8000 a=rtpmap:18 G729a/8000 a=rtpmap:4 G723/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15

[pxy]<<192.168.1.169:5060(476) [pxy]<<192.168.1.169:5060(476) ACK sip:648204822@192.168.1.10:6060 SIP/2.0 Via: SIP/2.0/UDP 192.168.1.169:5060;branch=z9hG4bK-f8b3d09f From: <sip:110@192.168.1.10:6060>;tag=22878a81540c2767o0 To: <sip:8648204822@192.168.1.10:6060>;tag=2cce67a3fd752181i4 Call-ID: b7719409-afaa6b7f@192.168.1.169 CSeq: 101 ACK Max-Forwards: 70 Contact: <sip:110@192.168.1.169:5060>;+sip.instance="<00000000-0000-0000-0000-00E08DAFB1F>" User-Agent: Linksys/SPA942-5.1.10

SPA9000/M ediatrix® 440x ISDN Gateway Configuration Guide

Appendix A— SIP Trace s of Various Scenarios

Content-Length: 0 Allow-Events: dialog

[pxy]<<192.168.1.169:5060(360) [pxy]<<192.168.1.169:5060(360) BYE sip:648204822@192.168.1.10:6060 SIP/2.0 Via: SIP/2.0/UDP 192.168.1.169:5060;branch=z9hG4bK-ed786d21 From: <sip:110@192.168.1.10:6060>;tag=22878a81540c2767o0 To: <sip:8648204822@192.168.1.10:6060>;tag=2cce67a3fd752181i4 Call-ID: b7719409-afaa6b7f@192.168.1.169 CSeq: 102 BYE Max-Forwards: 70 User-Agent: Linksys/SPA942-5.1.10 Content-Length: 0

private side ends the call private side ends the call [pxy]->192.168.1.169:5060(361) [pxy]->192.168.1.169:5060(361) SIP/2.0 200 OK To: <sip:8648204822@192.168.1.10:6060>;tag=2cce67a3fd752181i4 From: <sip:110@192.168.1.10:6060>;tag=22878a81540c2767o0 Call-ID: b7719409-afaa6b7f@192.168.1.169 CSeq: 102 BYE Via: SIP/2.0/UDP 192.168.1.169:5060;branch=z9hG4bK-ed786d21 Server: Linksys/SPA9000-5.1.6(a) Allow-Events: talk, hold, conference, x-spa-cti Content-Length: 0

BCC:Ended [4]->192.168.1.75:5060(425) [4]->192.168.1.75:5060(425) BYE sip:648204822@192.168.1.75:5060 SIP/2.0 Via: SIP/2.0/UDP 192.168.1.10:5062;branch=z9hG4bK-3d89b93a From: "Mediatrix" <sip:1946@192.168.1.75:5060>;tag=1be50f305ef95759o4;ref=110 To: <sip:648204822@192.168.1.75:5060>;tag=c1f2604c716fd1e Call-ID: 24a3813c-5308acbd@192.168.1.10 CSeq: 102 BYE Max-Forwards: 70 User-Agent: Linksys/SPA9000-5.1.6(a) Allow-Events: talk, hold, conference, x-spa-cti Content-Length: 0

[4]<<192.168.1.75:5060(358) [4]<<192.168.1.75:5060(358) SIP/2.0 200 OK Call-ID: 24a3813c-5308acbd@192.168.1.10 CSeq: 102 BYE From: "Mediatrix" <sip:1946@192.168.1.75:5060>;tag=1be50f305ef95759o4;ref=110 To: <sip:648204822@192.168.1.75:5060>;tag=c1f2604c716fd1e Via: SIP/2.0/UDP 192.168.1.10:5062;branch=z9hG4bK-3d89b93a Content-Length: 0 Supported: replaces User-Agent: MxSipApp/v1.1.3.19 MxSF/v3.2.1.2

SPA9000/M ediatrix® 440x ISDN Gatew ay Configuration Guide

Appendix B— References

• Configuration Notes 0245 Mediatrix 4400 VoIP Gateway PSTN Scenario

• Mediatrix 4401/4402/4404 (BRI) Software Configuration Guide

• Mediatrix 4400 Product Brochure

• SPA9000 Administration Guide

Appendix B— References

SPA9000/M ediatrix® 440x ISDN Gateway Configuration Guide

Appendix B— References

SPA9000/M ediatrix® 440x ISDN Gatew ay Configuration Guide

Linksys Mediatrix 440 Configuration manual

Specifications and Main Features

Frequently Asked Questions

User Manual