Table of Contents
Advertisement
SmartWare Software Configuration Guide
•
Configure early call connect / disconnect (Optional)
•
Configure a phone context (Optional)
•
Mapping call-control properties to SIP headers
•
Enabling support for SIP remote-party-id headers
•
Configuring ISDN redirecting number tunneling over SIP (optional)
•
Enabling SIP RFC Privacy, Asserted-identity, & Preferred-identity headers (RFC 3323/3325)
•
SIP REFER transmission (& ISDN explicit call transfer support)
Binding the interface to a SIP gateway
Every SIP interface must be explicitly bound to a SIP gateway instance.
Procedure: To bind a SIP interface to a SIP gateway.
Mode: Interface SIP
Step
1
node (if-sip)[ if-name ]#bind gateway gw-
name
Examples: Bind the SIP interfaces to a SIP gateway instance
The following example shows how to bind a SIP interface named MySipIf to a SIP gateway instance named
sip.
node>enable
node#configure
node(cfg)#context cs
node(ctx-cs)[switch]#interface sip MySipIf
node(if-sip)[MySipIf]#bind gateway sip
Configure a remote host
You can define a remote host within the SIP interface. All calls forwarded to the SIP gateway through this SIP
interface will be sent to that host unless the SIP gateway has a default server configured. In that case the remote
host specified here will only be used for the request-URI and the to-header, but the request will be sent to the
default server.
The remote host parameter may contain either an IP address or a DNS hostname.
Usually, you only need to set this parameter, if you do not have a default server configured on the SIP gateway.
This is the case, if you either do not use a SIP server for call routing, or if the server you use for call routing is a
SIP redirect server.
Procedure: To specify the remote SIP entities IP address or DNS hostname in the SIP interface
SIP interface configuration task list
Command
32 • SIP interface configuration
Purpose
Binds the gateway to a SIP gateway.
372
Advertisement
Table of Contents
Troubleshooting
