Welcome to Unified Networking

Cisco CME DSP Issue If you are running through any of the following error, then this post is for you.  Applicable to Fxo, Fxs ports and PRI E1/T1 ports deployments. 1. Only one way communication is happening 2. Frequently getting the console message:  FLEXDSPRM-3-TDM_CONNECT: failed to connect voice-port (1/1/0) to dsp_channel(1/1/3) 3. Able to call but no audio The reason here, we can call it as a cisco bug or misbehaviour of the router. When there are frequent changes at one side of the PRI trunk or fxs port then router's dsp fails to function properly. Signalling works without any issues though. When this happens you might face one way audio through router. That means if you are having a pri trunk then calls in one direction, pbx --> router or router --> pbx works but not works in the reverse path. Even though if you are calls are working in both the ways, if you see this error, you might experience calls disconnecting in feature. So you should be awa...

Hello all,            In this, document i will tell you how to successfully integrate Cisco Call manager Express (CME) with any third party PBX with examples. This process is called PRI Trunking or PRI integration.           Recently i was into PRI integration with 3 Cisco routers (Cisco 3945, 2951 and 4130) with IRIS lite PBX.           Integrating a PBX is not a that hard as we think, but it's bit sensitive. Sensitive in the sense while during the PRI integration we just need to be careful while assigning the parameters, they should match at both ends, i.e., on PBX side and CME side as well.           The very first thing to consider for PRI trunking is   "cable".   Yes, the cable which needs to connected between PBX and CME should be a cross over cable. For connecting a cross over cable, at cisco side we should connect to 1,2 4,5. In PBX side we...

Cisco SRST configuration in CME. Watch the whole configuration from Here Highlighted part is related to SRST. Building configuration... Current configuration : 2179 bytes ! ! Last configuration change at 09:48:23 UTC Wed Sep 21 2016 by pyramid version 15.3 service timestamps debug datetime msec service timestamps log datetime msec no service password-encryption ! hostname Router ! boot-start-marker boot-end-marker ! aqm-register-fnf ! enable password pyramid ! no aaa new-model ! ! ! ! ! ! ! ip cef no ipv6 cef multilink bundle-name authenticated ! ! ! ! ! ! ! voice-card 0 ! ! ! voice service voip  allow-connections h323 to h323  allow-connections h323 to sip  allow-connections sip to h323  allow-connections sip to sip  fax protocol t38 version 0 ls-redundancy 0 hs-redundancy 0 fallback none  sip   registrar server expires max 600 min 60 ! ! voice register global  mode srst  s...

Recently i have came across the issue that even after making the correct configuration SSL Portal was note opening in Fortigate frimware version 5.2.5 and above. Solution: So in your policies you might have written  Source interface: ssl.root source address: all Destination interface: internal Destination address: all service: all action: accept Here, you should not give source address to all. Your ssl root --> lan policy should look like this Source interface: ssl.root source address: <SSL-VPN-SUBNET> source users: <source users group>     >>>>>> The SSL Users group you have created. Destination interface: internal Destination address: all service: all action: accept If your configuration is correct apart from this, then you should now be able to see the portal.

Recently i have came across the issue that even after making the correct configuration SSL Portal was note opening in Fortigate frimware version 5.2.5 and above. Solution: So in your policies you might have written  Source interface: ssl.root source address: all Destination interface: internal Destination address: all service: all action: accept Here, you should not give source address to all. Your ssl root --> lan policy should look like this Source interface: ssl.root source address: <SSL-VPN-SUBNET> source users: <source users group>     >>>>>> The SSL Users group you have created. Destination interface: internal Destination address: all service: all action: accept If your configuration is correct apart from this, then you should now be able to see the portal.

Bandwidth restricting/limiting/shaping with Sub-Interfaces in Cisco IOS The following port describes on what is bandwidth limiting and how we can configure them with Cisco routers which are configured with Sub-Interfaces. Scenario: Switch0 configure with 3 vlans Router0 configured with 3 sub-interfaces with correct vlan tags. switch <--> router configured as trunk port. Configuration in router:  Creating access lists that matches the LAN networks. access-list 101 permit ip any 192.168.10.0 0.0.0.255 access-list 102 permit ip any 192.168.20.0 0.0.0.255 access-list 103 permit ip any 192.168.30.0 0.0.0.255   Creating class-maps that maps to the LAN networks:   class-map match-all vlan10  match access-group 101 class-map match-all vlan20  match access-group 102 class-map match-all vlan30  match access-group 103 Note: here vlan10, vlan20, vlan30 are the names of the class-maps that we have cre...

CISCO TELEPRESENCE SERVER (TCS) INSTALLATION [STEP BY STEP] For complete installation video watch the video ^ Read carefully!! Important things to remember: 1)You will having an .exe file to install TCS. No any ISO file or .OVA file is required. 2)Windows server 2012 Installed. 3)Sql 2012server SP1 Installed. ( Officially it is said that it will support SP1, SP2, SP3) 4)Licenses you should have one release key and options keys. Installation: 1) Install the windows 2012 server.      In Roles and services add Web server, .net 3.5, .net 4.5, asp .net, Window server Backup. 2) Install SQL 2012 server.     Create a DB Instance with name TCS. and all defaults. 3)Now copy the TCS Installer folder to C drive in windows server. 4)Open command prompt with adminstrator rights. 5)Edit license.txt file and add your serial number, release key and option keys in there without any special characters. 6)Now in command prompt go to the installation...