csim start command

csim start {number} is a hidden command to initiate simulated calls. It allows debugging for call routing from voice gateways and CUCME.

When command was issued it will looks into dial-peer configured on the router and send call to destination-pattern configured in dial-peer.

Note that this command also bypass COR configured in dial-peer.

Router#csim start 7101   ---> this case dial-peer was found and success to call

csim: called number = 7101, loop count = 1 ping count = 0

csim err csimDisconnected recvd DISC cid(4885)

csim: loop = 1, failed = 1

csim: call attempted = 1, setup failed = 1, tone failed = 0

Router#csim start 8001   ---> this case dial-peer was not found

csim: called number = 8001, loop count = 1 ping count = 0

csim err:csim_do_test Error peer not found

    

Understanding Dial Peer

Dial peers are the primary used to implement a dial plan on Cisco voice gateways. Dial peers are used to determine which calls are routed and the path a call should take.

POTS dial peers are used to process calls that are connected to traditional telephony equipment such as PBX, Analog Phone and PSTN.

VOIP dial peers are used to process calls to or from the data network.

Pots Dial Peers

Configuration

Router(config)#dial-peer voice 1 pots
Router(config-dial-peer)#destination-pattern 2222
Router(config-dial-peer)#port 0/0/0

VOIP Dial Peers

Configuration

Router(config)#dial-peer voice 100 voip
Router(config-dial-peer)#destination-pattern 3333
Router(config-dial-peer)#session-target ipv4:192.168.1.1

Dial Peer Matching

Inbound and Outbound Dial Peers.

 Inbound Dial Peer Matching

Priority1 "incoming called-number" ---> Defines the called number or DNIS string

Priority2 "answer-address" ---> Defines the originating calling number or ANI string

Priority3 "destination-pattern" ---> Uses the calling number (originating or ANI string) to match the incoming call leg to an inbound dial peer.

Priority4 "port" ---> Attempts to match the configured dial-peer port to the voice port associated with the incoming call (POTS dial peers only).

Priority5 "default" dial-peer or dial peer 0, is matched when no other inbound dial peer is used. It is better to configure a specific dial peer to match incoming calls.

Outbound Dial Peer Matching

For outbound dial peer matching, the called number is matched against the configured destination-pattern in the dial peers with the longest matched.

Consider the following scenario.

R1 has 4 dial-peers configuration, 2 pots and 2 voips.

When phone 2222 call 3333,

dial-peer 2 pots will match as an inbound dial-peer because "incoming called-number" is the 1st priority when matching inbound dial-peer and the call will be processed as one-stage dialing(you will not get the second dial tone to enter additional digits).

dial-peer 101 voip will match as an outgoing dial-peer because 3333 is the longest matched and codec g.729r8 will be used for RTP media stream over ip network.  

  

ISDN PRI Gateway Configuration

Environment

1. Cisco Router 3825 with VWIC2-1MFT-T1/E1 card in router HWIC0 slot.
2. PVDM2-32
3. Link to PSTN with ISDN PRI E1 EURO Protocol.

Router(config)#card type e1 0 0
Router(config)#network-clock-participate wic 0
Router(config)#network-clock-select 1 E1 0/0/0
Router(config)#isdn switch-type primary-net5
Router(config)#controller E1 0/0/0
Router(config-controller)#pri-group timeslots 1-31
Router(config-controller)#interface serial 0/0/0:15
Router(config-if)#isdn switch-type primary-net5
Router(config-if)#isdn incoming-voice voice
Router(config-if)#end
Router#show isdn status

Global ISDN Switchtype = primary-net5
ISDN Serial0/0/0:15 interface
        dsl 0, interface ISDN Switchtype = primary-net5
    Layer 1 Status:
        ACTIVE
    Layer 2 Status:
        TEI = 0, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED
    Layer 3 Status:
        0 Active Layer 3 Call(s)
    Active dsl 0 CCBs = 0
    The Free Channel Mask:  0xFFFF7FFF
    Number of L2 Discards = 0, L2 Session ID = 1

Now use dial-peer to create the numbering plan.
     

MGCP Gateway Auto Configuration

MGCP was created for a centralized architecture, where most of the configuration and call-control intelligence resides on a call agent, such as Cisco Callmanager.

Configuration on IOS Router,

MGCP-Gateway(config)#ccm-manager mgcp
MGCP-Gateway(config)#ccm-manager music-on-hold
MGCP-Gateway(config)#ccm-manager config server
MGCP-Gateway(config)#ccm-manager config
---> After this command Gateway will download configuration from Callmanager.

Configuration Callmanager

Note:

1. Domain Name must be the same with router hostname.

2. If you have command "ip domain-name" in router configuration for example "ip domain-name uclab.com" in Callmanager Gateway Configuration Page use Domain Name = MGCP-Gateway.uclab.com

3. If you have command "no ip domain-name" in router configuration just use MGCP-Gateway in Callmanager Gateway Configuration Page.