Collaboration

Cisco Collaboration CICD & CIVND.
In this course, am going to explain the complete series end to end. 

Popular posts from this blog

Converting cisco 1852 AP to controller (Mobility express)

           CONVERTING 1852 AP TO MOBILITY EXPRESS Get your work done easily, watch the video for this process:   CLICK HERE FOR VIDEO Pre requisites: 1.1852 AP 2.Mobilty express image 3.Mobility express update image 4.TFTP server 5.DHCP server Procedure: Step-1: Connect the 1852 AP in network which have DHCP server. Your PC should be in same network and reachability should be there. (between PC and AP) Step-2: Install the ME image  Open the tftp server and start it. Keep the Mobility express image (30MB) in TFTP-Root directory. go to AP console and issue the below commands: logging console disable      //optional prevents from bothering up with console logging messages debug capwap console cli ap-type mobility-express tftp://x.x.x.x/<image>.tar With the above commands, We have downloaded the ME image into the AP. It Will automatically reboots waits until it does!  Wait 10 - 15 M...
Read more

Configuring SX20 as a Standalone device

Image
Things get much simpler and easy when you want to configure SX20 as a Standalone device. This is a much needed feature when someone wants to use SX20 for Video conferencing but they don't have any telepresence equipment. Using H323 protocol we can configure SX20 as standalone device, where as SIP can be used in case of CUCM deployed environments. To configure SX20 as a standalone device, follow the below steps: 1. Enable H323 from network service 2. Select default call control protocol as H323 3. Select Mode to Off (Optional) 4. Go to H323 configuration page; System -- Configuration -- H323  5. Select Call setup mode: Direct 6. Port Allocation: Static 7. Under H323 Alias, Configure ID as Your SX20 Unit IP address.     Do not assign any URI under ID, leave it with just the IP address. URI will be configured only for       SIP, whereas H323 will work based on IP address only.    (Private or Public IP is immaterial, just assign whatever th...
Read more

FLEXDSPRM-3-TDM_CONNECT: failed to connect voice-port (1/1/0) to dsp_channel(1/1/3)

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...
Read more