Dynamips和Vmware完成CCVP试验(3)

2009/03/07
一：系统切换到CHARLES_1.5G，安装vmware tools后指针灵活
二：CIPC(cisco ip communicator)和VTGO(7960)在CCM中添加方式不一样的
三：VTGO对SRST支持不好，改用CIPC7.0可以正常SRST，但是拨打+1或者+011忙音
四：SRST后没有测试PSTN拨入情况，估计不行，因call_loop，待下次再次测试
五：CCS也没有测试，下次再测试

2009/03/06
发现dila-peer voip不支持forward或者strip，写了一个translation-rule去掉1，再拨打测试，显示"unknown number"失败，但是用test voice translation-rule被叫发送正确

2009/03/09
发现dial-peer voip不支持T或者*，在Chicago上老老实实写成如下语句才能匹配
dial-peer voice 102 voip
 de.ion LD
 destination-pattern 1312.......  //不能用1T或者1312*,show dialplan 1 number 13124012222不能匹配
 translate-outgoing called 1
 session target ipv4:200.0.0.254
!
dial-peer voice 101 voip
 de.ion == Local Calls
 destination-pattern 775.......
 session target ipv4:200.0.0.254
!
dial-peer voice 103 voip
 de.ion == International
 destination-pattern 011............  //不能用011T或者011*,show dialplan 1 number 011442030013333不能匹配
 session target ipv4:200.0.0.254
!

PSTN上的发现
num-exp 1312....... 312.......才是控制拨入后转换的关键语句，如果没有，主叫方显示“UNKNOWN NUMBER”，虽然test voice translation-rule被叫发送正确或者show dialplan number 1312401222可以匹配

SRST后测试CSS，工作正常

2009/03/10
开启UK，测试CME-CCM互通，失败；引出如下思考：
significant digits用在GATEWAY上
CCM&Unity step-by-step>chapter 3>adding gateways
call routing information>inbound calls>significant digits（prefix DN）
outbound calls>caller ID DN

The Significant Digits field determines the number of digits of an incoming dialed number that CallManager uses. CallManager counts from right to left, so if the number entered in this field is 4 and the digits received are 8105559090, 810555 would be removed and .ly 9090 would be used to determine the destination of this call.

The Prefix DN field defines what digits will be added to the front of the incoming destination number. This is applied to the number, after CallManager truncates the number based . the Significant Digits setting.

本文出自 “虹桥漫步” 博客，谢绝转载！