Guest

Cisco Outbound Option

SIP Outbound Dialer Uses a Different Caller ID for Each Campaign Configuration Example

Document ID: 116526

Updated: Oct 03, 2013

Contributed by Kristof Van Coillie, Cisco TAC Engineer.

   Print

Introduction

This document describes how to configure a different calling number for each campaign when you use the outbound Session Initiation Protocol (SIP) Dialer. This allows your customers to see a different calling number based on the campaign that is used.

Prerequisites

Requirements

Your service provider must accept the calling number configured. Some providers only accept a calling number in the range of your Direct Inward Dialing (DID) numbers.

Note: This document assumes that the SIP Dialer is configured and works properly. More information on how to configure the SIP Dialer and other involved components is available in Outbound Option installation: SIP Dialer.

Components Used

This document is not restricted to specific software and hardware versions.

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.

Configure

In the Configuration Manager, navigate to the Outbound Option Campaign. In order to configure the Caller ID (CLID), enter the number in the Campaign prefix digits field.

The SIP Dialer adds this number to the outgoing INVITE in the Remote-Party-ID header. Enter this command on the gateway (GW) in order for the GW to send this number to the provider:

Router(config-sip-ua)#remote-party-id

If a Remote-Party-ID header is present in the incoming INVITE message, the calling name and number extracted from the Remote-Party-ID header are sent as the calling name and number in the outgoing setup message.

Verify

In order to verify this process, collect these logs on the GW:

  • debug ccsip messages
  • debug isdn q931

Note: Refer to How to properly and safely collect debugs on an IOS router for more information.

You should see the Remote-Party-ID header with the value configured in the Campaign:

Received:
INVITE sip:6611112@10.48.79.33 SIP/2.0
Via: SIP/2.0/UDP 10.48.54.193:58800;branch=z9hG4bK-d8754z-585af41448265640-1---
d8754z-;rport
Max-Forwards: 70
Require: 100rel
Contact: <sip:8201@10.48.54.193:58800>
To: <sip:6611112@10.48.79.33>
From: <sip:8201@10.48.54.193>;tag=bd636c31
Call-ID: 8a2d8e03-1e41060e-003a973b-2026e015
CSeq: 1 INVITE
Session-Expires: 1800
Min-SE: 90
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, UPDATE, NOTIFY, PRACK, REFER, NOTIFY,
OPTIONS
Content-Type: Multipart/mixed;boundary=uniqueBoundary
Supported: timer, resource-priority, replaces
User-Agent: Cisco-SIPDialer/UCCE8.0
Content-Length: 530
Remote-Party-ID: <sip:123456789@10.48.79.33>;party=calling;screen=no;privacy=off

This is what is sent to the provider in the outgoing setup message:

Sep 16 13:00:55.204: ISDN Se0/1/0:15 Q931: TX -> SETUP pd = 8  callref = 0x0083
Bearer Capability i = 0x8090A3
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA9839F
Exclusive, Channel 31
Calling Party Number i = 0x2180, '123456789'
Plan:ISDN, Type:National
Called Party Number i = 0xA1, '6611112'
Plan:ISDN, Type:National

Troubleshoot

There is currently no specific troubleshooting information available for this configuration.

Updated: Oct 03, 2013
Document ID: 116526