SIP interface configuration task list
376
SmartWare Software Configuration Guide
32 • SIP interface configuration
The
address-translation
commands map as shown in the following two examples.
Example 1:
Address-translation incoming-call <call-control header>
ß
mapping <SIP-header>
Example 2:
Address-translation outgoing-call <SIP-header>
ß
mapping <call-control header>
In two more examples, the first line maps the to-header contents of the inbound call to the called-e164 prop-
erty of the call control, while the second line maps the request header contents to the called-name property of
the call-control.
address-translation incoming-call called-e164 to-header
address-translation incoming-call called-name request-uri
Configuring ISDN Redirecting Number Tunneling Over SIP
A SIP interface can be configured to tunnel the ISDN Redirecting E.164 Number and Redirecting Reason.
This is implemented per the IETF draft standard method according to draft-jennings-sip-voicemail-uri-05.
The figure below shows a call that is redirected in the PSTN network and reaches the device over an ISDN
interface. The incoming ISDN SETUP message contains additional information elements for the Redirecting
Party Number (B) and the Redirecting Reason (Call-Forwarding-Unconditional, for example). When the
Redirecting Number Tunneling over SIP has been enabled, the Request-URI of the outgoing SIP INVITE
message has additional parameters for the redirected number (target) and the redirecting reason (cause).
Normally, the Redirecting Number Tunneling over SIP is disabled. However, you can manually enable this fea-
ture for each SIP interface separately using the following commands. Note that transmission and reception of
the target and cause parameters must be configured separately
SIP
ISDN
A
C
B (CFU to C)
1. SETUP(CdPN=B
CnPN=A)
2. SETUP(CdPN=C
CnPN=A
RedirPN=B
RedirReason=cfu)
3. INVITE C;target=B;cause=486
To: C
From: A
