Critical Bytes

Search This Blog

Ahmed Bukhatir ( Don´t let me go)

on April 16, 2010

Get link
Facebook
X
Pinterest
Email
Other Apps

Get link
Facebook
X
Pinterest
Email
Other Apps

Comments

Call Failure on SendToVRU Node in ICM Script

I would like to share one very interesting observation during one of my UCCE project at one big Telecom Company. During this project everything goes according to plan, except getting call failure on Send to VRU node in ICM scripts, after going through the logs of CVP, I found that gateway is rejecting calls & getting 403 Call Forbidden response in CVP (CVP8 was being used)Logs . After further investigation found out that gateway is rejecting calls because of toll fraud security settings on gateway. If toll fraud security is not configured correctly it will drop untrusted endpoints traffic . Solution is to configure the correct toll fraud security setting otherwise disable IP address trusted list authentication altogether.

How to copy database from LoggerA to LoggerB and HDS1 to HDS2

https://supportforums.cisco.com/docs/DOC-15290 From SQL Management Studio... 1. Backup LoggerA and HDS1 databases (for safety precautions, which is a good practice anyway). 2. Take a copy LoggerA DB and transfer/FTP it to LoggerB server. And, take a copy of HDS1 DB and transfer/FTP it to HDS2 server. 3. Stop LoggerB services from service control. 4. Stop all AW/HDS2 services from service control. 5. From the LoggerB server: http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/icm_enterprise/icm_enterprise_7_5/maintenance/guide/icm75ag.pdf a. Using ICMDBA, "Recreate" the database (pg 46). b. Import LoggerA's data...

PGW Design Considerations with CVP

PGW Design Considerations with CVP Introduction In many Hosted environments, particularly when the service provider is itself a PSTN carrier, all the actual call routing occurs via an ICM NIC. In that sense, these deployments are very much like Deployment Model #4 (i.e VRU Only with NIC Controlled Routing). The same situation applies if a PGW is being used to route calls using (typically) the ICM SS7 NIC. PGW can be consider in such deployment models where a service provider is looking to support very high level of call volume. Such deployment could use the UCCE parent child model. Features PGW does support Geographic redundancy, call limiting, SIP virtual interfaces, etc; PGW can support SIP to SIP over 1000 call per second today, and has potential to double this performance. It is based on class-4 softswitch, and has powerful routing capabilities for both E.164 and FQDN-based routing. It is a full SIP B2BUA that also supports SIP proxy mode. Call Control Traffic Unified CVP is curr...

Powered by Blogger