Sample H323 configuration with CUCM

-
!
vty-async
isdn switch-type primary-net5
!
!
voice rtp send-recv
!
voice service voip
 allow-connections h323 to h323
 allow-connections h323 to sip
 allow-connections sip to h323
 allow-connections sip to sip
 supplementary-service h450.12
 fax protocol pass-through g711alaw
 h323
  no h225 timeout keepalive
 modem passthrough nse codec g711alaw redundancy
 sip
  registrar server expires max 3600 min 3600
!
voice class h323 1
  h225 timeout tcp establish 3
  call start slow
!
!
controller E1 0/0/0
 framing NO-CRC4
 pri-group timeslots 1-31
!
controller E1 0/0/1
 framing NO-CRC4
 pri-group timeslots 1-31
!
controller E1 0/1/0
 framing NO-CRC4
 pri-group timeslots 1-31
!
interface Serial0/0/0:15
 no ip address
 encapsulation hdlc
 isdn switch-type primary-net5
 isdn incoming-voice voice
 no cdp enable
!
interface Serial0/0/1:15
 no ip address
 encapsulation hdlc
 isdn switch-type primary-net5
 isdn incoming-voice voice
 no cdp enable
!
interface Serial0/1/0:15
 no ip address
 encapsulation hdlc
 isdn switch-type primary-net5
 isdn incoming-voice voice
 no cdp enable
!
!
!
voice-port 0/1/0:15
 bearer-cap Speech
!
voice-port 0/0/0:15
 bearer-cap Speech
!
voice-port 0/0/1:15
 bearer-cap Speech
!
!
dial-peer voice 100 pots
 description **outbound calls POTS leg**
 preference 1
 destination-pattern 9T
 direct-inward-dial
 port 0/0/0:15
 forward-digits 10
!
dial-peer voice 102 pots
 description **outbound calls POTS leg**
 destination-pattern 9T
 direct-inward-dial
 port 0/0/1:15
 forward-digits 10
!
dial-peer voice 103 pots
 description **outbound calls POTS leg**
 preference 2
 destination-pattern 9T
 direct-inward-dial
 port 0/1/0:15
 forward-digits 10
!
dial-peer voice 106 pots
 description **National outbound calls POTS leg**
 preference 1
 destination-pattern 90T
 direct-inward-dial
 port 0/0/0:15
 forward-digits 11
!
dial-peer voice 107 pots
 description **National outbound calls POTS leg**
 destination-pattern 90T
 direct-inward-dial
 port 0/0/1:15
 forward-digits 11
!
dial-peer voice 108 pots
 description **National outbound calls POTS leg**
 preference 2
 destination-pattern 90T
 direct-inward-dial
 port 0/1/0:15
 forward-digits 11
!
dial-peer voice 104 voip
 description **incoming VOIP cal leg**
 destination-pattern 4......
 voice-class h323 1
 session target ipv4:172.31.110.10
 incoming called-number .
!
dial-peer voice 112 pots
 description **incoming POTS call leg**
 incoming called-number .
 direct-inward-dial
!
dial-peer voice 109 pots
 description **International outbound calls POTS leg**
 destination-pattern 900T
 direct-inward-dial
 port 0/0/0:15
 prefix 00
!
dial-peer voice 110 pots
 description **International outbound calls POTS leg**
 preference 1
 destination-pattern 900T
 direct-inward-dial
 port 0/0/1:15
!
dial-peer voice 111 pots
 description **International outbound calls POTS leg**
 preference 2
 destination-pattern 900T
 direct-inward-dial
 port 0/1/0:15
 prefix 00
!
!

Comments

Post a Comment

Popular posts from this blog

Status: Local Agent is not responding. This may be due to Master or Local Agent being down.

-
If you have read my previous post , you would understand why LA and MA services are important for such a scenario and no component has backed-up, rather you get the above error message. Symptoms -   All Disaster Recovery Framework (DRF) services are down, and no new devices, schedules, or statuses can be viewed from the DRF console. Also, when you access the DRF admin pages, the above error message is received. Affected CM releases 6.1.5 and later. Resolution In order to resolve it, first, verify if the Certificate Serial Number in the keystore of Publisher is present in the Truststore of all Subscribers. Complete these steps: Log on to CUCM OS Administration page of Publisher server of the cluster setup. Choose Security > Certificate Management . The Certificate List window displays. You can use the Find controls in order to filter the certificate. Click on the ipsec.pem file and check the serial number of the certificate. Log on to CUCM OS Admin...
Read more

Understanding code yellow

-
Understanding sample code yellow alert- Oct 3 01:00:10, cms01, Error, Cisco CallManager, ccm: 147896: Oct 03 05:00:10.616 UTC : %CCM_CALLMANAGER-CALLMANAGER-3-CodeYellowEntry: CodeYellowEntry Expected Average Delay:362 Entry Latency:20 Exit Latency:8 Sample Size:10 Total Code Yellow Entry:14 High Priority Queue Depth:2 Normal Priority Queue Depth:12 Low Priority Queue Depth:70 Cluster ID:StandAloneCluster Node ID:cms01, 3652 The above alert is about code yellow entry, it shows the time when server enters code yellow state. There are no specifications to note at this alert, CM enters code yellow when it achieves the mentioned conditions for code yellow state as mentioned in service parameters. Oct 3 01:00:12, cms01, Error, Cisco CallManager, ccm: 147897: Oct 03 05:00:12.268 UTC : %CCM_CALLMANAGER-CALLMANAGER-3-CodeYellowExit: CodeYellowExit Expected Average Delay:0 Entry Latency:20 Exit Latency:8 Sample Size:10 Time Spent in Code Yellow:2 Number of Calls Rejected Due to C...
Read more