Home | Skip to Content | Skip to Search | Skip to Navigation | Skip to Footer |
Worldwide [change] |Register |About Cisco
Guest

Hierarchical Navigation

Cisco BTS 10200 Softswitch

IP MGCP Phone with BTS 10200 Configuration Example

Downloads

Document ID: 60362


Contents

Introduction
Prerequisites
      Requirements
      Components Used
      Conventions
Background Information
Configure
      Network Diagram
      Configurations
Verify
Troubleshoot
      Troubleshooting Commands
NetPro Discussion Forums - Featured Conversations
Related Information

Introduction

This document provides a sample configuration for Cisco IP phones controlled via the Media Gateway Control Protocol (MGCP) by a Cisco BTS 10200. The configuration is suitable for basic call handling and in a lab environment. No advanced call feature is covered.

Prerequisites

Requirements

Before you attempt this configuration, ensure that you meet these requirements:

  • The Cisco IP phone is loaded with a software image that supports MGCP.

  • The BTS 10200 application is installed and both the Call Agent (CA) and the Element Management System (EMS) are operative.

  • A basic Dial Plan is already in place in the BTS 10200 configuration.

Components Used

The information in this document is based on these software and hardware versions:

  • Cisco BTS 10200 version 4.1 and later

  • Cisco 7940/7960 IP phone with 7.1.0 (and later) MGCP software

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.

Conventions

For more information on document conventions, refer to the Cisco Technical Tips Conventions.

Background Information

When the Cisco IP phone 7960/7940 boots, it first receives the IP address from the Dynamic Host Configuration Protocol (DHCP) server (if not configured for a static IP address). It then contacts the TFTP server to collect the configuration (and if necessary to load a new software image).

The phone specific configuration file for an MGCP software image is called 'MGC<Phone_MAC_address>.cnf'.

The phone CLI is accessible via Telnet.

Configure

In this section, you are presented with the information to configure the features described in this document.

Note: To find additional information on the commands used in this document, use the Command Lookup Tool ( registered customers only) .

Network Diagram

This document uses this network setup:

mgcp-bts10200-config-1.gif

Configurations

This document uses these configurations:

This is the IP phone configuration as it appears from the phone CLI. The configuration entries are the same (except the one that needs to be changed via DHCP). They can be used in the phone specific configuration file on the TFTP server (in this case, it is called MGC000CCE62B656.cnf).

Please note these items during configuration:

  • The phone gets the first configuration entries (IP address, mask, gateway, DNS, domain, TFTP server, IP address) form the DHCP server (or via a static configuration in the phone configuration menu).

  • my_name is the phone name combination of the word MGC and the phone MAC address.

  • tos_media is the IP Type Of Serice (TOS) that is set to 7 in the default files. The standard practice is to change it to 5 (critical) in VoIP.

  • telnet_level should be set to 2 to get full access to the phone via the CLI. This is useful in a lab environment.

  • Set mgc_gw_controller to the IP address of the Call Agent. In this example, it is set to the virtual IP address used for MGCP by the BTS. This address is moved to the secondary Call Agent in case of failover on the primary Call Agent.

  • For mgcp_input_port and mgcp_output_port you can leave the value proposed in the default file. They work fine with BTS 10200.

  • The DTMP configuration can be added if required.

  • mgcp_endpoint_id must correspond to the endpoint identifier used by the BTS 10200.

Cisco 7940 IP Phone 

MGCP Phone> show configuration
------ Current *FLASH* Configuration ------
Platform : Cisco IP Phone 7940
Elasped Time: 2 days, 18:35:37

dhcp_server : 10.48.84.43
my_ip_addr : 10.48.84.201
subnet_mask : 255.255.255.0
defaultgw : 10.48.84.1
backupgw_1 : 10.48.84.119
dyn_dns_addr_1 : 0.0.0.0
dyn_dns_addr_2 : 0.0.0.0
dns_addr : 144.254.10.123
dns_backup_1: 144.254.71.184
primary_tftp_addr : 10.48.84.20
dyn_tftp_addr : 0.0.0.0
my_mac_addr : 000c:ce62:b656
domain_name : cisco.com


my_name : MGC000CCE62B656
Status Flags : 12300000

network_media_type : Auto
network_port2_type : Hub/Switch
tos_media : 5
phone_label : ""
tftp_cfg_dir : ""
phone_password : **********
phone_prompt : "MGCP Phone"
language : english
sntp_mode : Unicast
sntp_server : "10.48.84.43"
time_zone : GMT
dst_offset : 1
dst_start_month : "April"
dst_start_day : 0
dst_start_day_of_week : "Sun"
dst_start_week_of_month : 1
dst_start_time : 2
dst_stop_month : "Oct"
dst_stop_day : 0
dst_stop_day_of_week : "Sun"
dst_stop_week_of_month : 8
dst_stop_time : 2
dst_auto_adjust : 1
time_format_24hr : 1
date_format : D/M/Y
nat_enable : 0
nat_address : Unprovisioned
voip_control_port : 5060
start_media_port : 16384
end_media_port : 32766
sync : "1"
xml_card_dir : ""
xml_card_file : "CARD.XML"
telnet_level : 2
services_url : ""
directory_url : ""
logo_url : "http://10.48.84.20/tftpboot/two_bongo.bmp"
http_proxy_addr : Unprovisioned
http_proxy_port : 80
garp_enable : 1
mgcp_gw_controller : 10.48.84.74
mgcp_input_port : 2427
mgcp_output_port : 2727
use_mac_name : 0
dtmf_outofband : none
dtmf_avt_payload : 101
mgcp_keepalive : 0
mgcp_keepalive_timer : 30
use_domain_name_braces : 0
mgcp_endpoint_id : "AALN/S0/SU0/0"
MGCP Phone>

This is the BTS 10200 configuration (with the assumption that a Dial Plan is already in place). The show commands for verification purposes are also included.

The commands to activate the newly configured components are included in the last part of this configuration. It is necessary to make sure that the endpoint name in the "add termination" and "add subscriber" corresponds to the one configured in the IP phone.

BTS 10200

 
CLI>add mgw-profile id=79XX-MGCP
Reply : Success: CLI add successful
Transaction 108989191215206 was processed.

CLI>add mgw id=7940-mgcp-1; call_agent_id=CA146; type=RGW; 
    mgw_profile_id=79XX-MGCP; tsap_addr=10.48.84.201

!--- This command is brought down to a second line
!--- for spatial reasons.


Reply : Success: CLI add successful
Transaction 108989192175706 was processed.

CLI>show mgw 

ID=7940-mgcp-1
TSAP_ADDR=10.48.84.201
CALL_AGENT_ID=CA146
MGW_PROFILE_ID=79XX-MGCP
STATUS=OOS
MGW_MONITORING_ENABLED=Y
TYPE=RGW

CLI>add termination mgw_id=7940-mgcp-1; port_start=0; port_end=1; 
    prefix=AALN/S0/SU0/ ; type=line

!--- This command is brought down to a second line
!--- for spatial reasons.

Please wait....

Reply : Success: Transaction 108989213885606 was processed.


!--- This shows the configuration already in place for 
!--- the dial plan and the digit map.


CLI>show dial-plan 

ID=dp1
DIGIT_STRING=46
DEST_ID=dest-to-csps1
SPLIT_NPA=NONE
DEL_DIGITS=0
MIN_DIGITS=3
MAX_DIGITS=14
NOA=UNKNOWN

ID=dp1
DIGIT_STRING=888999
DEST_ID=local-call
SPLIT_NPA=NONE
DEL_DIGITS=0
MIN_DIGITS=3
MAX_DIGITS=14
NOA=UNKNOWN

 

Reply : Success: Entries 1-5 of 5 returned.

CLI> show subscriber-profile

ID=subpf1
DIGIT_MAP_ID=dig-map-1
DIAL_PLAN_ID=dp1
LOCAL_PFX1_OPT=NR
TOLL_PFX1_OPT=RQ
POP_ID=1
OLI=0
EA_USE_PIC1=Y

Reply : Success: Entry 1 of 1 returned.

CLI> show digit-map

ID=dig-map-1
DIGIT_PATTERN=[8]xxxxxxxxx|[4-6]xxx|[9]xxxxxxxx

Reply : Success: Entry 1 of 1 returned.


======================================
CLI>add subscriber id=7940-mgcp-1=sub1; DN1=8889996841; TERM_ID=AALN/S0/SU0/0; 
    MGW_ID=7940-mgcp-1; SUB_PROFILE_ID=subpf1

!--- This command is brought down to a second line
!--- for spatial reasons.


Reply : Success: Transaction 108989266230406 was processed.

CLI>control mgw ID=7940-mgcp-1; target-state=INS; mode=forced

MGW ID -> 7940-mgcp-1
INITIAL STATE -> ADMIN_OOS 
REQUEST STATE -> ADMIN_INS 
RESULT STATE -> ADMIN_INS 
FAIL REASON -> ADM found no failure
REASON -> ADM executed successful
RESULT -> ADM configure result in success

Reply : Success: CLI change successful


CLI> equip subscriber-termination id=7940-mgcp-1=sub1

ID -> Subcriber ID -> 7940-mgcp-1=sub1
FAIL REASON -> ADM found no failure
REASON -> ADM executed successful
RESULT -> ADM configure result in success

Reply : Success: CLI change successful

CLI>control subscriber-termination id= 7940-mgcp-1=sub1; 
   target_state=INS; mode=forced

!--- This command is brought down to a second line
!--- for spatial reasons.


INITIAL STATE -> ADMIN_OOS 
ID -> 7940-mgcp-1=sub1
REQUEST STATE -> ADMIN_INS 
RESULT STATE -> ADMIN_INS 
FAIL REASON -> ADM found no failure
REASON -> ADM executed successful
RESULT -> ADM configure result in success

Reply : Success: CLI change successful

Verify

See the BTS 10200 configuration section for the verification show commands.

Certain show commands are supported by the Output Interpreter Tool ( registered customers only) , which allows you to view an analysis of show command output.

Troubleshoot

This section provides information you can use to troubleshoot your configuration.

There are three places where you can collect useful troubleshooting information:

  • Phone debug commands.

  • BTS 10200 Call Agent log files.

  • Packet trace as UNIX snoop or a Cisco snooper.

Troubleshooting Commands

Note: Before issuing debug commands, refer to Important Information on Debug Commands.

  • debug mgcpio—Displays the MGCP message received and transmitted by the phone.

  • debug mgcp_parse—Displays possible message interpretation errors.

The BTS 10200 Call Agent log files are located in the /opt/Opticall/CA146/bin/logs directory.

This output is an example of a BTS 10200 log message for a good call. Issue the tail -f /opt/Opticall/CA146/bin/logs/trace_<replace_with_current_trace_file_name>.log | egrep '(BCM|MGA)' command to run this trace.

Note: The lines in this output have been brought down to second and third lines for spatial reasons.

[I3 16:13:27.469 MGA     01-2 ------------]
 "sent setup.ind-->:ep=AALN/S0/SU0/0@10.48.84.201 termIdx=27 csaId=0 oper=0x181
 digitCount=10 digits=8889996811" [mga_sig_sai.c:1435]

[I3 16:13:27.469 BCM     01-1 ------------]
 "  57  MGA-->SetupInd(OBCSM)-->BCM_97 :: s: 41 ss: 90 ps: 1 " 
[bcm_calltrace.c:482]

[I3 16:13:27.469 BCM     01-1 ------------] 
"ANI: 8889996841    ,OEP : AALN/S0/SU0/0@7940-mgcp-1        , 
DNIS : 8889996811TEP :  " [bcm_calltrace.c:521]

[I3 16:13:27.469 BCM     01-1 ------------]
 "  57  BCM-->SetupReqInd(TBCSM)-->BCM_107 :: s: 20 ss: 91 ps: 0 " 
[bcm_calltrace.c:466]

[I3 16:13:27.469 BCM     01-1 ------------] 
"Create Conn issued: CLeg = 207, PLeg = 217" [bcm_tbcsm_sa_proc.c:4509]

[I3 16:13:27.469 MGA     01-2 ------------] 
"createconn.req recvd<--:for ep=AALN/S0/SU0/0@10.48.84.201 termIdx=27 oper=181 
connRef=52 rs_methd=0 connMode=2 cmd_seq_count=1" [mga_conn_control.c:484]

[I3 16:13:27.492 MGA     01-1 ------------] 
"createconn.req recvd<--:for ep=aaln/S1/1@vsig-iad-2.cisco.com termIdx=1 
oper=181 connRef=62 rs_methd=0 connMode=3 cmd_seq_count=0" [mga_conn_control.c:484]

[I3 16:13:27.555 BCM     01-1 ------------] 
"  57  MGA-->CreateConnectionAck(TBCSM)-->BCM_107 :: s: 23 ss: 83 ps: 63 " 
[bcm_calltrace.c:482]

[I3 16:13:27.555 BCM     01-1 ------------] 
"  57  BCM_107-->SetupReq(TBCSM)-->MGA :: s: 23 ss: 89 ps: 63 " 
[bcm_calltrace.c:497]

[I3 16:13:27.555 BCM     01-1 ------------] 
"ANI: 8889996841    ,OEP : AALN/S0/SU0/0@7940-mgcp-1        , DNIS : 8889996811
     TEP : aaln/S1/1@vsig-iad-2 " [bcm_calltrace.c:521]

[I3 16:13:27.555 MGA     01-1 ------------] 
"setup.req recvd<-- termIdx=1 mgaState=CALL_DISCONNECT_IDLE oper=0x181" 
[mga_sig_sai.c:218]

[I3 16:13:27.566 MGA     01-1 ------------] 
"sent alert.ind-->:ep=aaln/S1/1@vsig-iad-2.cisco.com termIdx=1 
csaId=107 pd=0 userInfoType=0 oper=0x181" [mga_sig_sai.c:1692]

[I3 16:13:27.566 BCM     01-1 ------------] 
"  57  MGA-->AlertingInd(TBCSM)-->BCM_107 :: s: 23 ss: 89 ps: 63 " 
[bcm_calltrace.c:482]

[I3 16:13:27.566 BCM     01-1 ------------] 
"  57  BCM-->AlertingReqInd(OBCSM)-->BCM_97 :: s: 7 ss: 82 ps: 7 " 
[bcm_calltrace.c:466]

[I3 16:13:27.566 BCM     01-1 ------------] 
"  57  BCM_97-->AlertingReq(OBCSM)-->MGA :: s: 8 ss: 84 ps: 45 " 
[bcm_calltrace.c:497]

[I3 16:13:27.566 MGA     01-2 ------------] 
"alert.req recvd<-- termIdx=27 mgaState=ORIG_START oper=0x181" 
[mga_sig_sai.c:304]

[I3 16:13:29.457 MGA     01-1 ------------] 
"sent setup.conf-->:ep=aaln/S1/1@vsig-iad-2.cisco.com termIdx=1 csaId=107 
oper=0x181" [mga_sig_sai.c:1183]

[I3 16:13:29.457 BCM     01-1 ------------] 
"  57  MGA-->SetupConf(TBCSM)-->BCM_107 :: s: 24 ss: 84 ps: 64 " 
[bcm_calltrace.c:482]

[I3 16:13:29.457 BCM     01-1 ------------] 
"  57  BCM-->SetupRespConf(OBCSM)-->BCM_97 :: s: 8 ss: 84 ps: 45 " 
[bcm_calltrace.c:466]

[I3 16:13:29.457 BCM     01-1 ------------] 
"  57  BCM_97-->ModifyConnection(OBCSM)-->MGA :: s: 9 ss: 85 ps: 49 " 
[bcm_calltrace.c:497]

[I3 16:13:29.457 BCM     01-1 ------------] 
"  57  BCM_97-->SetupResp(OBCSM)-->MGA :: s: 9 ss: 85 ps: 49 " 
[bcm_calltrace.c:497]

[I3 16:13:29.457 MGA     01-2 ------------] 
"setup.resp recvd<-- termIdx=27 mgaState=ORIG_START oper=0x101" 
[mga_sig_sai.c:372]

[I3 16:13:29.478 BCM     01-1 ------------] 
"  57  MGA-->ModifyConnectionAck(OBCSM)-->BCM_97 :: s: 9 ss: 85 ps: 49 " 
[bcm_calltrace.c:482]

[I3 16:13:35.040 MGA     01-1 ------------]
 "sent rel.ind-->:ep=aaln/S1/1@vsig-iad-2.cisco.com termIdx=1 csaId=107 
digits= digitCount=0 oper=0x101" [mga_sig_sai.c:1518]

[I3 16:13:35.040 BCM     01-1 ------------] 
"  57  MGA-->ReleaseInd(TBCSM)-->BCM_107 :: s: 25 ss: 85 ps: 67 " 
[bcm_calltrace.c:482]

[I3 16:13:35.040 BCM     01-1 ------------] 
"cause action = 2 (1=re-attempt 4=route-advacne 3=re-route 2=no" 
[bcm_bcsm_util.c:6963]

[I3 16:13:35.040 BCM     01-1 ------------] 
"  57  BCM-->SuspendReqInd(OBCSM)-->BCM_97 :: s: 9 ss: 85 ps: 49 " 
[bcm_calltrace.c:466]

[I3 16:13:36.391 MGA     01-2 ------------] 
"sent rel.ind-->:ep=AALN/S0/SU0/0@10.48.84.201 termIdx=27 csaId=97 
digits= digitCount=0 oper=0x101" [mga_sig_sai.c:1518]

[I3 16:13:36.391 BCM     01-1 ------------] 
"  57  MGA-->ReleaseInd(OBCSM)-->BCM_97 :: s: 10 ss: 88 ps: 50 " 
[bcm_calltrace.c:482]

[I3 16:13:36.391 BCM     01-1 ------------] 
"cause action = 2 (1=re-attempt 4=route-advacne 3=re-route 2=no" 
[bcm_bcsm_util.c:6963]

[I3 16:13:36.391 BCM     01-1 ------------] 
"  57  BCM_97-->DeleteConnection(OBCSM)-->MGA :: s: 53 ss: 91 ps: 10 " 
[bcm_calltrace.c:497]

[I3 16:13:36.391 BCM     01-1 ------------] 
"  57  BCM-->ReleaseReqInd(TBCSM)-->BCM_107 :: s: 26 ss: 88 ps: 26 " 
[bcm_calltrace.c:466]

[I3 16:13:36.391 BCM     01-1 ------------] 
"  57  BCM_107-->DeleteConnection(TBCSM)-->MGA :: s: 71 ss: 91 ps: 26 " 
[bcm_calltrace.c:497]

[I3 16:13:36.391 BCM     01-1 ------------] 
"  57  BCM_107-->ReelaseResp(TBCSM)-->MGA :: s: 20 ss: 91 ps: 26 " 
[bcm_calltrace.c:497]

[I3 16:13:36.391 BCM     01-1 ------------] 
"  57  BCM-->ReleaseRespConf(OBCSM)-->BCM_97 :: s: 53 ss: 91 ps: 10 " 
[bcm_calltrace.c:466]

[I3 16:13:36.391 BCM     01-1 ------------] 
"  57  BCM_97-->ReelaseResp(OBCSM)-->MGA :: s: 1 ss: 91 ps: 10 " 
[bcm_calltrace.c:497]

[I3 16:13:36.391 MGA     01-2 ------------] 
"deleteconn.req recvd<--:for ep=AALN/S0/SU0/0@10.48.84.201 termIdx=27 
oper=100 connRef=52 isTermInitialized=1 operation=8 cmd_seq_count=1" 
[mga_conn_control.c:1188]

[I3 16:13:36.391 MGA     01-2 ------------] 
"rel.resp recvd<-- termIdx=27 mgaState=MGA_CALL_DISCONNECT oper=0x100" 
[mga_sig_sai.c:512]

[I3 16:13:36.391 MGA     01-1 ------------] 
"deleteconn.req recvd<--:for ep=aaln/S1/1@vsig-iad-2.cisco.com termIdx=1 
oper=100 connRef=62 isTermInitialized=1 operation=8 cmd_seq_count=0" 
[mga_conn_control.c:1188]

[I3 16:13:36.391 MGA     01-1 ------------] 
"rel.resp recvd<-- termIdx=1 mgaState=MGA_CALL_DISCONNECT oper=0x100" 
[mga_sig_sai.c:512]

[I3 16:13:36.402 MGA     01-2 ------------] 
"delete conn ack sent-->:connRef=52 termIdx=27" [mga_conn_control.c:1619]

[I3 16:13:36.412 BCM     01-1 ------------] 
"  57  MGA-->DeleteConnectionAck(OBCSM)-->BCM_97 :: s: 1 ss: 91 ps: 10 " 
[bcm_calltrace.c:482]

[I3 16:13:36.412 MGA     01-1 ------------] 
"delete conn ack sent-->:connRef=62 termIdx=1" [mga_conn_control.c:1619]

[I3 16:13:36.412 BCM     01-1 ------------]
 "  57  MGA-->DeleteConnectionAck(TBCSM)-->BCM_107 :: s: 20 ss: 91 ps: 26 " 
[bcm_calltrace.c:482]^Croot@vsig-bts4#

This output is an example packet trace of a Cisco snooper. The trace starts when the IP phone boots and the trace contains a voice call.

Note: The lines in this output have been brought down to second and third lines for spatial reasons.

18:09:32.826112  10.48.84.201:2427    10.48.84.74:2727     
     MGCP...... -> RSIP 1 AALN/S0/SU0/0@10.48.84.201 MGCP 1.0 
                   RM: restart 
18:09:32.827193  10.48.84.74:2727     10.48.84.201:2427    
     MGCP...... -> 200 1 OK  
                   N: vbts-MGCP-1.vsig.cisco.com:2727  
18:09:32.910324  10.48.84.74:2727     10.48.84.201:2427    
     MGCP...... -> RQNT 53687393 AALN/S0/SU0/0@10.48.84.201 MGCP 1.0  
                   N: vbts-MGCP-1.vsig.cisco.com:2727  
                   X: 1B00000001  
                   R: L/hd(N)  
                   S:   
                   K: 53687392  
18:09:32.917491  10.48.84.201:2427    10.48.84.74:2727     
     MGCP...... -> 200 53687393 OK 

18:10:48.180429  10.48.84.201:2427    10.48.84.74:2727     
     MGCP...... -> 200 53687394 OK 
18:10:52.119512  10.48.84.201:2427    10.48.84.74:2727     
     MGCP...... -> NTFY 3 AALN/S0/SU0/0@10.48.84.201 MGCP 1.0 
                   N: vbts-MGCP-1.vsig.cisco.com:2727 
                   X: 1B00000002 
                   O: D/8, D/8, D/8, D/9, D/9, D/9, D/6, D/8, D/1, D/1 
18:10:52.120878  10.48.84.74:2727     10.48.84.201:2427    
     MGCP...... -> 200 3 OK  
18:10:52.121291  10.48.84.74:2727     10.48.84.201:2427    
     MGCP...... -> RQNT 53687395 AALN/S0/SU0/0@10.48.84.201 MGCP 1.0  
                   X: 1B00000003  
                   R: L/hu(N),L/hf(N)  
                   K: 53687394  
18:10:52.130754  10.48.84.201:2427    10.48.84.74:2727     
     MGCP...... -> 200 53687395 OK 
18:10:52.132146  10.48.84.74:2727     10.48.84.201:2427    
     MGCP...... -> CRCX 53687396 AALN/S0/SU0/0@10.48.84.201 MGCP 1.0  
                   C: 3c  
                   L: p:10-30,  a:PCMU;PCMA;G.729A, e:off, s:on, t:b0, nt:IN, r:be  
                   M: recvonly  
                   K: 53687395  
18:10:52.147662  10.48.84.201:2427    10.48.84.74:2727     
     MGCP...... -> 200 53687396 OK 
                   I: 0 
                   v=0  
                   o=- 7940 7940 IN IP4 10.48.84.201 
                   s=MGCP Call 
                   c=IN IP4 10.48.84.201 
                   t=0 0 
                   m=audio 21732 RTP/AVP 0 18 
                   a=rtpmap:0 PCMU/8000 
18:10:52.150336  10.48.84.74:2427     10.48.84.45:2427     
     MGCP...... -> CRCX 126 aaln/S1/1@vsig-iad-2.cisco.com MGCP 1.0  
                   C: 3c  
                   L: p:10-30,  a:PCMU;PCMA;G.729A, e:off, s:on, t:b0, nt:IN, r:be  
                   M: sendrecv  
                   K: 125  
                                                                           
                   v=0  
                   o=- 7940 7940 IN IP4 10.48.84.201  
                   s=MGCP Call  
                   c=IN IP4 10.48.84.201  
                   t=0 0  
                   m=audio 21732 RTP/AVP 0 18  
                   a=rtpmap:0 PCMU/8000  
18:10:52.174270  10.48.84.45:2427     10.48.84.74:2427     
     MGCP...... -> 200 126 OK 
                   I: 10 
                   v=0  
                   o=- 16 0 IN IP4 10.48.84.45  
                   s=Cisco SDP 0  
                   c=IN IP4 10.48.84.45  
                   t=0 0  
                   m=audio 17804 RTP/AVP 0 100  
                   a=rtpmap:100 X-NSE/8000  
                   a=fmtp:100 200-202  
                   a=X-sqn:0  
                   a=X-cap: 1 audio RTP/AVP 100  
                   a=X-cpar: a=rtpmap:100 X-NSE/8000  
                   a=X-cpar: a=fmtp:100 200-202  
                   a=X-cap: 2 image udptl t38  
18:10:52.177324  10.48.84.74:2727     10.48.84.201:2427    
     MGCP...... -> MDCX 53687397 AALN/S0/SU0/0@10.48.84.201 MGCP 1.0  
                   I: 0  
                   C: 3c  
                   M: recvonly  
                   K: 53687396  
                                                                           
                   v=0  
                   o=- 16 0 IN IP4 10.48.84.45  
                   s=Cisco SDP 0  
                   c=IN IP4 10.48.84.45  
                   t=0 0  
                   m=audio 17804 RTP/AVP 0 100  
                   a=rtpmap:100 X-NSE/8000  
                   a=fmtp:100 200-202  
                   a=X-sqn:0  
                   a=X-cap:1 audio RTP/AVP 100  
                   a=X-cpar:a=rtpmap:100 X-NSE/8000  
                   a=X-cpar:a=fmtp:100 200-202  
                   a=X-cap:2 image udptl t38  
18:10:52.198348  10.48.84.201:2427    10.48.84.74:2727     
     MGCP...... -> 200 53687397 OK 
                   I: 0 
                   v=0  
                   o=- 7940 7940 IN IP4 10.48.84.201 
                   s=MGCP Call 
                   c=IN IP4 10.48.84.201 
                   t=0 0 
                   m=audio 21732 RTP/AVP 0 
                   a=rtpmap:0 PCMU/8000 
18:10:52.201049  10.48.84.74:2427     10.48.84.45:2427     
     MGCP...... -> RQNT 127 aaln/S1/1@vsig-iad-2.cisco.com MGCP 1.0  
                   X: 10000002C  
                   R: L/hd(N)  
                   S: L/rg  
                   K: 126  
18:10:52.207257  10.48.84.45:2427     10.48.84.74:2427     
     MGCP...... -> 200 127 OK 
18:10:52.210515  10.48.84.74:2727     10.48.84.201:2427    
     MGCP...... -> RQNT 53687398 AALN/S0/SU0/0@10.48.84.201 MGCP 1.0  
                   X: 1B00000004  
                   R: L/hu(N)  
                   S: G/rt  
                   K: 53687397  
18:10:52.218395  10.48.84.201:2427    10.48.84.74:2727     
     MGCP...... -> 200 53687398 OK 
18:10:55.690844  10.48.84.45:2427     10.48.84.74:2427     
     MGCP...... -> NTFY 25 aaln/S1/1@vsig-iad-2.cisco.com MGCP 1.0 
                   N: vbts-MGCP-1.vsig.cisco.com:2427 
                   X: 10000002C 
                   O: L/hd 
18:10:55.691858  10.48.84.74:2427     10.48.84.45:2427     
     MGCP...... -> 200 25 OK  
18:10:55.692265  10.48.84.74:2427     10.48.84.45:2427     
     MGCP...... -> RQNT 128 aaln/S1/1@vsig-iad-2.cisco.com MGCP 1.0  
                   X: 10000002D  
                   R: L/hu(N),L/hf(N)  
                   K: 127  
18:10:55.697682  10.48.84.45:2427     10.48.84.74:2427     
     MGCP...... -> 200 128 OK 
18:10:55.702798  10.48.84.74:2727     10.48.84.201:2427    
     MGCP...... -> MDCX 53687399 AALN/S0/SU0/0@10.48.84.201 MGCP 1.0  
                   I: 0  
                   C: 3c  
                   M: sendrecv  
                   K: 53687398  
18:10:55.723871  10.48.84.201:2427    10.48.84.74:2727     
     MGCP...... -> 200 53687399 OK 
                   I: 0 
                   v=0  
                   o=- 7940 7940 IN IP4 10.48.84.201 
                   s=MGCP Call 
                   c=IN IP4 10.48.84.201 
                   t=0 0 
                   m=audio 21732 RTP/AVP 0 
                   a=rtpmap:0 PCMU/8000 
18:10:55.724954  10.48.84.74:2727     10.48.84.201:2427    
     MGCP...... -> RQNT 53687400 AALN/S0/SU0/0@10.48.84.201 MGCP 1.0  
                   X: 1B00000005  
                   R: L/hu(N),L/hf(N)  
                   S:   
                   K: 53687399  
18:10:55.733586  10.48.84.201:2427    10.48.84.74:2727     
     MGCP...... -> 200 53687400 OK 
18:11:00.264348  10.48.84.45:2427     10.48.84.74:2427     
     MGCP...... -> NTFY 26 aaln/S1/1@vsig-iad-2.cisco.com MGCP 1.0 
                   N: vbts-MGCP-1.vsig.cisco.com:2427 
                   X: 10000002D 
                   O: L/hu 
18:11:00.265618  10.48.84.74:2427     10.48.84.45:2427     
     MGCP...... -> 200 26 OK  
18:11:00.265967  10.48.84.74:2427     10.48.84.45:2427     
     MGCP...... -> RQNT 129 aaln/S1/1@vsig-iad-2.cisco.com MGCP 1.0  
                   X: 10000002E  
                   R: L/hd(N)  
                   K: 128  
18:11:00.271426  10.48.84.45:2427     10.48.84.74:2427     
     MGCP...... -> 200 129 OK 
18:11:01.787031  10.48.84.201:2427    10.48.84.74:2727     
     MGCP...... -> NTFY 4 AALN/S0/SU0/0@10.48.84.201 MGCP 1.0 
                   N: vbts-MGCP-1.vsig.cisco.com:2727 
                   X: 1B00000005 
                   O: L/hu 
18:11:01.788209  10.48.84.74:2727     10.48.84.201:2427    
     MGCP...... -> 200 4 OK  
18:11:01.788674  10.48.84.74:2727     10.48.84.201:2427    
     MGCP...... -> RQNT 53687401 AALN/S0/SU0/0@10.48.84.201 MGCP 1.0  
                   X: 1B00000006  
                   R: L/hd(N)  
                   K: 53687400  
18:11:01.793781  10.48.84.74:2427     10.48.84.45:2427     
     MGCP...... -> DLCX 130 aaln/S1/1@vsig-iad-2.cisco.com MGCP 1.0  
                   I: 10  
                   C: 3c  
                   K: 129  
18:11:01.797380  10.48.84.201:2427    10.48.84.74:2727     
     MGCP...... -> 200 53687401 OK 
18:11:01.798019  10.48.84.74:2727     10.48.84.201:2427    
     MGCP...... -> DLCX 53687402 AALN/S0/SU0/0@10.48.84.201 MGCP 1.0  
                   I: 0  
                   C: 3c  
                   K: 53687401  
18:11:01.805858  10.48.84.201:2427    10.48.84.74:2727     
     MGCP...... -> 250 53687402 OK 
18:11:01.815300  10.48.84.45:2427     10.48.84.74:2427     
      MGCP...... -> 250 130 OK 
                    P: PS=378, OS=30004, PR=304, OR=48640, PL=0, JI=65, LA=0

NetPro Discussion Forums - Featured Conversations

Networking Professionals Connection is a forum for networking professionals to share questions, suggestions, and information about networking solutions, products, and technologies. The featured links are some of the most recent conversations available in this technology.
NetPro Discussion Forums - Featured Conversations for Voice
Service Providers: Voice over IP
Voice & Video: Voice over IP
Voice & Video: IP Telephony
Voice & Video: IP Phone Services for End Users
Voice & Video: Unified Communications
Voice & Video: IP Phone Services for Developers
Voice & Video: General

Related Information

Updated: Feb 02, 2006Document ID: 60362