Bitswap

WTF is OOD Refer ?

Posted by Andy on May 6, 2009

According go SIP System Administration Guide:

Out-of-dialog REFER (OOD-R) enables remote applications to establish calls by sending a REFER message to Cisco Unified SRST without an initial INVITE. After the REFER is sent, the remainder of the call setup is independent of the application and the media stream does not flow through the application. The application using OOD-R triggers a call setup request that specifies the Referee address in the Request-URI and the Refer-Target in the Refer-To header. The SIP messaging used to communicate with Cisco Unified SRST is independent of the end-user device protocol, which can be H.323, POTS, SCCP, or SIP. Click-to-dial is an example of an application that can be created using OOD-R.

A click-to-dial application enables users to combine multiple steps into one click for a call setup. For example, a user can click a web-based directory application from his or her PC to look up a telephone number, off-hook the desktop phone, and dial the called number. The application initiates the call setup without the user having to out-dial from his or her own phone. The directory application sends a REFER message to Cisco Unified SRST, which sets up the call between both parties based on this REFER.

Figure 3 shows an example of OOD-R being used by a click-to-dial application. In this scenario, the following events occur (refer to the event numbers in the illustration):

1. Remote user clicks to dial.

2. Application sends out-of-dialog REFER to Cisco Unified SRST.

3. Cisco Unified SRST 1 connects to SIP phone 1 (Referee).

4. Cisco Unified SRST 1 sends INVITE to SRST 2.

5. Cisco Unified SRST 2 sends INVITE to SIP phone 2 (Refer-Target) and the call is accepted.

6. Voice path is created between the two SIP phones.

Note The connectivity to Cisco Unified Communications Manager has been lost and, therefore, IP phone 1 and IP phone 2 have registered to SRST routers.

Figure 3 Click-to-Dial Application using Out-of-Dialog REFER

via Cisco Unified SIP SRST System Administrator Guide – 4.1 Features  [Cisco Unified Survivable Remote Site Telephony] – Cisco Systems.

Posted in 2.02 CUCM SIP Endpoints, 4.05 SIP | Leave a Comment »

SIP trunk between CME and CM

Posted by Andy on May 5, 2009

Best Practices

Follow these guidelines :

•Configure a SIP Trunk Security Profile with Accept Replaces Header selected.

•Configure a SIP trunk on Unified CM using the SIP Trunk Security Profile created, and also specify a ReRouting CSS. The ReRouting CSS is used to determine where a SIP user (transferor) can refer another user (transferee) to a third user (transfer target) and which features a SIP user can invoke using the SIP 302 Redirection Response and INVITE with Replaces.

•For SIP trunks there is no need to enable the use of media termination points (MTPs) when using SCCP endpoints on Unified CME. However, SIP endpoints on Unified CME require the use of media termination points on Unified CM to be able to handle delayed offer/answer exchanges with the SIP protocol (that is, the reception of INVITEs with no Session Description Protocol).

•Route calls to Unified CME via a SIP trunk using the Unified CM dial plan configuration (route patterns, route lists, and route groups).

•Use Unified CM device pools and regions to configure a G.711 codec within the site and the G.729 codec for remote Unified CME sites.

•Configure the allow-connections sip to sip command under voice services voip on Unified CME to allow SIP-to-SIP call connections.

•For SIP endpoints, configure the mode cme command under voice register global, and configure dtmf-relay rtp-nte under the voice register pool commands for each SIP phone on Unified CME.

•For SCCP endpoints, configure the transfer-system full-consult command and the transfer-pattern .T command under telephony-service on Unified CME.

•Configure the SIP WAN interface voip dial-peers to forward or redirect calls, destined for Unified CM, with session protocol sipv2 and dtmf-relay [sip-notify | rtp-nte] on Unified CME.

via Cisco Unified Communications SRND Based on Cisco Unified Communications Manager 7.x – Call Processing  [Cisco Unified Communications Manager (CallManager)] – Cisco Systems.

Posted in 4.05 SIP | Leave a Comment »

MOH in CM and CME

Posted by Andy on May 5, 2009

Music on Hold

While Unified CM can be enabled to stream MoH in both G.711 and G.729 formats, Unified CME streams MoH only in G.711 format. Therefore, when Unified CME controls the MoH audio on a call placed on hold, it requires a transcoder to transcode between a G.711 MoH stream and a G.729 call leg.

via Cisco Unified Communications SRND Based on Cisco Unified Communications Manager 7.x – Call Processing  [Cisco Unified Communications Manager (CallManager)] – Cisco Systems.

Posted in 7.04 Music-on-hold | Leave a Comment »

Cisco Unified Communications SRND Based on Cisco Unified Communications Manager 7.x – Call Processing  [Cisco Unified Communications Manager (CallManager)] – Cisco Systems

Posted by Andy on May 4, 2009

The arq reject-unknown-prefix command is is used to guard against potential call routing loops across redundant Unified CM trunks.

via Cisco Unified Communications SRND Based on Cisco Unified Communications Manager 7.x – Call Processing  [Cisco Unified Communications Manager (CallManager)] – Cisco Systems.

Posted in 4.03 H.323 | Leave a Comment »

CUCM 7.0 on Vmware

Posted by Andy on April 30, 2009

Do not forget to create disks as an IDE and follow this guidelines

•Processor speed must be 2.0 GHz or greater

•Physical memory size must be 2 GB or greater

•Physical hard disk size must be 72 GB or larger

via Cisco Unified Communications SRND Based on Cisco Unified Communications Manager 7.x – Call Processing  [Cisco Unified Communications Manager (CallManager)] – Cisco Systems.

Posted in Uncategorized | Leave a Comment »

implemented upgrade tool for AP successfully (for first time :) )

Posted by Andy on April 26, 2009

screenshot-4_25_2009-8_21_04-pm

Posted in Uncategorized | Leave a Comment »

option 43 for assinging controller address to AP

Posted by Andy on April 26, 2009

I newer can successfully implement option 43 😦 Here is how my DHCP configured:

ip dhcp pool wireless-ap
network 172.16.3.0 255.255.255.0
default-router 172.16.3.1
dns-server 63.139.196.34 67.151.90.2
domain-name example.com
option 60 ascii “Cisco AP c1130”
option 43 hex f104.ac19.0302 ! 172.16.3.2 in hex , 1 wc interface

but AP seems to using DNS :

*Mar  1 00:00:12.580: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to down
*Mar  1 00:00:19.704: %DHCP-6-ADDRESS_ASSIGN: Interface FastEthernet0 assigned DHCP address 172.16.3.7, mask 255.255.255.0, hostname AP001b.d561.4afe
*Mar  1 00:00:30.156: %CAPWAP-3-ERRORLOG: Not sending discovery request AP does not have an Ip !!
*Mar  1 00:00:30.571: Logging LWAPP message to 255.255.255.255.
*Mar  1 00:00:30.618: %SYS-6-LOGGINGHOST_STARTSTOP: Logging to host 255.255.255.255 started – CLI initiated
*Mar  1 00:00:33.055: %CDP_PD-4-POWER_OK: Full power – NEGOTIATED inline power source
*Mar  1 00:00:33.094: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up
*Mar  1 00:00:33.133: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar  1 00:00:34.056: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to up
*Mar  1 00:00:34.094: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
Translating “CISCO-CAPWAP-CONTROLLER.example.net”…domain server (4.2.2.1)
Translating “CISCO-LWAPP-CONTROLLER.example.net”…domain server (4.2.2.1) [OK]
*Mar  1 00:00:40.208:  capwapHandleDiscoveryTimer Expired
*Mar  1 00:00:41.208: %CAPWAP-3-ERRORLOG: Did not get log server settings from DHCP.
*Mar  1 00:00:41.234: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER.example.netwtpDecodeDiscovery Response numOfCapwapDiscoveryResp = 0
wtpDecodeDiscovery Response numOfCapwapDiscoveryResp = 1
wtpDecodeDiscovery Response numOfCapwapDiscoveryResp = 2
*Mar  1 00:00:52.249:  capwapHandleDiscoveryTimer Expired
*Mar  1 00:00:52.249: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Apr 26 00:12:31.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.16.3.2 peer_port: 5246
*Apr 26 00:12:32.780: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 172.16.3.2 peer_port: 5246
*Apr 26 00:12:32.782: %CAPWAP-5-SENDJOIN: sending Join Request to 172.16.3.2
*Apr 26 00:12:32.782: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN
*Apr 26 00:12:32.884: %CAPWAP-5-CHANGED: CAPWAP changed state to CFG
*Apr 26 00:12:33.390: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset

Posted in wireless | 2 Comments »

eem quick note (authorisation failed)

Posted by Andy on April 23, 2009

How ofthen did y0u see such error ? Me too often 

%HA_EM-6-LOG: NAT : DEBUG(cli_lib) : : OUT : % Authorisation failed.

This post created to resolve this issue. 

 

The following example shows how to set a username to be associated with a Tcl session. If you are using authentication, authorization, and accounting (AAA) security and implement authorization on a command basis, you should use the event manager session cli username command to set a username to be associated with a Tcl session. The username is used when a Tcl policy executes a CLI command. TACACS+ verifies each CLI command using the username associated with the Tcl session that is running the policy. Commands from Tcl policies are not usually verified because the router must be in privileged EXEC mode to register the policy. In the example, the username is yourname, and this is the username that is used whenever a CLI command session is initiated from within an EEM policy.

configure terminal

 event manager session cli username yourname

 end
and voila !

 

Apr 23 13:18:10.210: Track: 101 Up change delayed for 20 secs

Apr 23 13:18:10.210: fh_fd_syslog_event_match: num_matches = 0

Apr 23 13:18:10.210: fh_fd_data_syslog: num_matches = 0

Apr 23 13:18:30.206: Track: 101 Up change delay expired

Apr 23 13:18:30.206: Track: 101 Change #5 rtr 101, state Down->Up

Apr 23 13:18:30.206: fh_track_object_changed: Track notification 101 state up

Apr 23 13:18:30.206: fh_fd_track_event_match: track ED pubinfo enqueue rc = 0

Apr 23 13:18:30.206: fh_fd_syslog_event_match: num_matches = 0

Apr 23 13:18:30.206: fh_fd_data_syslog: num_matches = 0

Apr 23 13:18:30.206: fh_fd_syslog_event_match: num_matches = 0

Apr 23 13:18:30.206: fh_fd_data_syslog: num_matches = 0

Apr 23 13:18:30.214: %HA_EM-6-LOG: NAT : DEBUG(cli_lib) : : CTL : cli_open called.

Apr 23 13:18:30.314: %HA_EM-6-LOG: NAT : DEBUG(cli_lib) : : OUT :

Apr 23 13:18:30.314: %HA_EM-6-LOG: NAT : DEBUG(cli_lib) : : OUT : rtr-1-nightagency line 2

Apr 23 13:18:30.314: %HA_EM-6-LOG: NAT : DEBUG(cli_lib) : : OUT :

Apr 23 13:18:30.314: %HA_EM-6-LOG: NAT : DEBUG(cli_lib) : : OUT : rtr-1-nightagency>

Apr 23 13:18:30.314: %HA_EM-6-LOG: NAT : DEBUG(cli_lib) : : IN  : rtr-1-nightagency>enable

Apr 23 13:18:30.314: cli_history_entry_add: free_hist_list size=0, hist_list size=7

Apr 23 13:18:30.314: check_eem_cli_policy_handler: command_string=enable

Apr 23 13:18:30.318: check_eem_cli_policy_handler: num_matches = 0, response_code = 1

Apr 23 13:18:30.326: %HA_EM-6-LOG: NAT : DEBUG(cli_lib) : : OUT :

Apr 23 13:18:30.326: %HA_EM-6-LOG: NAT : DEBUG(cli_lib) : : OUT : rtr-1-nightagency#

Apr 23 13:18:30.326: %HA_EM-6-LOG: NAT : DEBUG(cli_lib) : : IN  : rtr-1-nightagency#clear ip nat translation forced

Apr 23 13:18:30.330: cli_history_entry_add: free_hist_list size=0, hist_list size=7

Apr 23 13:18:30.330: check_eem_cli_policy_handler: command_string=clear ip nat translation forced

Apr 23 13:18:30.330: check_eem_cli_policy_handler: num_matches = 0, response_code = 1

Apr 23 13:18:30.474: %HA_EM-6-LOG: NAT : DEBUG(cli_lib) : : OUT :

Apr 23 13:18:30.474: %HA_EM-6-LOG: NAT : DEBUG(cli_lib) : : OUT : rtr-1-nightagency#

Apr 23 13:18:30.474: %HA_EM-6-LOG: NAT : DEBUG(cli_lib) : : IN  : rtr-1-nightagency#exit

Apr 23 13:18:30.474: %HA_EM-6-LOG: NAT : DEBUG(cli_lib) : : CTL : cli_close called.cron_tick: num_matches 0

Posted in Uncategorized | 1 Comment »

NEW CCIE Voice Technology Lab Workbook Version 3.0 from CCBOOTCAMP

Posted by Andy on April 23, 2009

What do you think about NEW CCIE Voice Technology Lab Workbook Version 3.0 from CCBOOTCAMP ? Table of contents here. Piece of  junk ? Slightly rewritten old workbook ?

Posted in Uncategorized | Leave a Comment »

My lab preparation companion

Posted by Andy on April 23, 2009

CCIE kitty

CCIE kitty

Posted in Uncategorized | Leave a Comment »