MMI customer training(MVD troubleshooting)
- 格式:ppt
- 大小:2.84 MB
- 文档页数:43


中 国 移 动 通 信 企 业 标 准 QB-╳╳-╳╳╳-╳╳╳╳ China Mobile CM-IMS Test Specification - MGCF&IM-MGW 版本号:1.2.0 中国移动通信集团公司 发布 ╳╳╳╳-╳╳-╳╳发布 ╳╳╳╳-╳╳-╳╳实施中国移动C M -I M S M G C F 及I M -M G W 设备测试规范目录前言 (IV)1范围 (1)2规范性引用文件 (1)3术语、定义和缩略语 (2)3.1缩略语 (2)3.2接口标识 (3)4测试环境及说明 (3)4.1测试环境配置 (3)5设备功能测试 (4)5.1与基于ISUP的CS域的基本呼叫互通 (4)5.1.1呼叫建立 (4)5.1.1.1IMS始呼(要求Precondition) (4)5.1.1.2IMS始呼(不要求Precondition) (7)5.1.1.3PSTN/PLMN始呼(要求Precondition) (9)5.1.1.4PSTN/PLMN始呼(不要求Precondition) (13)5.1.2呼叫释放 (17)5.1.2.1呼叫建立后IMS发起呼叫释放 (17)5.1.2.2呼叫建立后PSTN/PLMN发起呼叫释放 (18)5.1.2.3IM-MGW发起的呼叫释放 (19)5.1.3异常处理 (20)5.1.3.1被叫忙 (20)5.1.3.2被叫未注册 (24)5.1.3.3被叫无应答 (28)5.1.3.4被叫不可及 (31)5.1.3.5被叫为空号 (36)5.1.3.6呼叫早释放 (38)5.1.3.7被叫拒接 (41)5.1.3.8IMS始发到PSTN/PLMN的视频呼叫回落语音 (45)5.1.3.9PLMN始发到IMS的基本视频呼叫失败 (46)5.1.3.10IMS侧发起语音通话切换为视频通话被拒绝 (47)5.1.3.11电路管理 (48)5.1.3.12IM-MGW承载建立失败 (49)5.1.4补充业务 (51)5.1.4.1呼叫保持和恢复 (51)5.1.4.2呼叫等待 (53)5.1.4.3呼叫前转 (56)5.1.4.4主叫号码显示和主叫号码显示限制 (59)5.1.5号码分析与处理 (60)5.1.5.1IMS始呼到本网PLMN手机用户 (60)5.1.5.2IMS始呼到它网PLMN手机用户 (60)5.1.5.3IMS始呼到它网PSTN固话用户 (61)5.1.5.4PSTN/PLMN始呼到IMS用户 (61)5.2与基于BICC的CS域的基本呼叫互通 (62)5.2.1呼叫建立 (62)5.2.1.1IMS始呼(要求Precondition) (62)5.2.1.2IMS始呼(不要求Precondition) (66)5.2.1.3PSTN/PLMN始呼(要求Precondition) (68)5.2.1.4PSTN/PLMN始呼(不要求Precondition) (72)5.2.2呼叫释放 (76)5.2.2.1呼叫建立后IMS发起呼叫释放 (76)5.2.2.2呼叫建立后PSTN/PLMN发起呼叫释放 (77)5.2.2.3IM-MGW发起的呼叫释放 (78)5.2.3异常处理 (79)5.2.3.1被叫忙 (79)5.2.3.2被叫未注册 (83)5.2.3.3被叫无应答 (87)5.2.3.4被叫不可及 (90)5.2.3.5被叫为空号 (94)5.2.3.6呼叫早释放 (96)5.2.3.7被叫拒接 (99)5.2.3.8IMS始发到PSTN/PLMN的视频呼叫回落语音 (103)5.2.3.9PLMN始发到IMS的基本视频呼叫失败 (104)5.2.3.10IMS侧发起语音通话切换为视频通话被拒绝 (105)5.2.3.11电路管理 (106)5.2.3.12IM-MGW承载建立失败 (107)5.2.4补充业务 (109)5.2.4.1呼叫保持和恢复 (109)5.2.4.2呼叫等待 (110)5.2.4.3呼叫前转 (113)5.2.4.4主叫号码显示和主叫号码显示限制 (116)5.2.5号码分析与处理 (118)5.2.5.1IMS始呼到本网PLMN手机用户 (118)5.2.5.2IMS始呼到2G/3G接入的V oLTE用户 (118)5.2.5.3IMS始呼到它网PLMN手机用户 (119)5.2.5.4IMS始呼到它网PSTN固话用户 (119)5.2.5.5PSTN/PLMN始呼到IMS用户 (120)5.2.5.6本网PLMN始呼到本网已签约被叫一号通业务的PLMN用户 (120)5.2.6DTMF处理 (121)5.2.6.1带内DTMF信号转带外处理 (121)5.2.6.2带外DTMF信号转带内处理 (122)5.2.7传真功能 (123)5.2.7.1IMS始呼到PSTN的低速传真 (123)5.2.7.2IMS始呼到PSTN的高速传真 (124)5.2.7.3PSTN始呼到IMS的低速传真 (126)5.2.7.4PSTN始呼到IMS的高速传真 (127)5.3关口局功能 (128)5.3.1被叫有CAMEL签约 (128)5.3.2被叫无CAMEL签约 (129)5.3.3被叫激活无条件前转(CFU) (130)5.3.4被叫激活不可及前转(CFNRc) (130)5.3.5被叫激活呼入闭锁业务(BAIC) (131)5.4IM-MGW管理(可选) (132)5.4.1IM-MGW注册 (132)5.4.2MGCF对IM-MGW的审计 (132)5.4.3IM-MGW上报异常事件 (133)5.5网管测试 (133)6编制历史 (133)前言本标准依据ITU-T和3GPP制定的相关标准,结合有关国内标准和中国移动其他企业标准,基于中国移动CM-IMS总体技术要求、VoLTE总体技术要求和实际需求而拟定,充分考虑了网络的平滑演进能力,为中国移动CM-IMS技术试验、网络建设和运行维护提供技术依据。
第2 章故障诊断1 维修呼叫程序呼叫流程 (213)002xxx HDD002770 作业模板处理HD 满RAP (215)003xxx IPSESS 通讯003318 IIT 软件故障RAP (217)003319 IIT 视频驱动程序检测故障RAP (217)003320 IISSESS 通讯故障 1 RAP (218)003321 IISSESS 通讯故障 2 RAP (218)003322 IISSESS 通讯故障 3RAP (219)003323 IISSESS 通讯故障 4 RAP (219)003324 IISSESS 通讯故障 5 RAP (220)003325 IISSESS 通讯故障 6 RAP (220)003326 IISSESS 通讯故障7RAP (221)003327 IISSESS 通讯故障8 RAP (221)003328 IISSESS 通讯故障9 RAP (222)003329 IISSESS 通讯故障10 RAP (222)003330 IISSESS 通讯故障11RAP (223)003331 IISSESS 通讯故障12 RAP (223)003332 IISSESS 通讯故障13 RAP (224)003333 IISSESS 通讯故障14 RAP (224)003334 IISSESS 通讯故障15RAP (225)003335 IISSESS 通讯故障16 RAP (225)003336 IISSESS 通讯故障17 RAP (226)003337 IISSESS 通讯故障18 RAP (226)003338 IISSESS 通讯故障19RAP (227)003339 IISSESS 通讯故障20 RAP (227)003340 IISSESS 通讯故障21 RAP (228)003341 IISSESS 通讯故障22 RAP (228)003342 IISSESS 通讯故障23RAP (229)003343 IISSESS 通讯故障24 RAP (229)003345 X PIO 未锁定故障 1 RAP (230)003346 X PIO 未锁定故障 2 RAP (230)003750 书本双面原稿不够RAP (231)003751 PANTHER 容量低下(扫描)RAP (231)003753 扫描不能超过300dpi RAP (232)003760 扫描设置故障RAP (232)003761 不正确的纸盘尺寸RAP (233)003763 未发现调整表RAP (233)003780 扫描图像压缩故障RAP (234)003795 AMS 限制错误RAP (234)003942 原稿尺寸自动检测故障RAP (235)003944 图像重复计数RAP (235)003945 放大倍率不适合RAP (236)003946 每个方向都矛盾(复印APS)RAP (236)003947 返回原稿计数错误RAP (237)003948 返回原稿不匹配RAP (237)003949 原稿不适当(图像覆盖)RAP (238)003950 混合原稿尺寸错误RAP (238)003955 原稿尺寸交换错误RAP (239)003956 原稿尺寸不明错误RAP (239)003957 原稿尺寸错误RAP (240)003963 无APS 目标纸盘RAP (240)003965 ATS/APS 无纸(IIT 检测)RAP (241)003966 ATS/APS 无目标(IIT)RAP (241)003970 传真行存储器溢出RAP (242)003972 最大存储页溢出RAP (242)003973 各个方向都矛盾 (243)003974 下一原稿规格RAP (243)003976 传真行存储器溢出(N up)RAP (244)003977 原稿不匹配(多重扫描)RAP (244)003980 装钉位置错误RAP (245)003981 装钉尺寸错误RAP (245)005xxx DADF005121 CVT 输送传感器On 卡纸RAP (247)005122 CVT 单面/面1 预定位On 卡纸RAP …………………………………248005123 CVT 单面/面 1 定位卡纸RAP (249)005125 CVT 定位传感器Off 卡纸RAP (250)005131 CVT 翻转On 卡纸RAP (251)005132 CVT 翻转On 卡纸2RAP ………………………………… (252)005134 CVT 翻转传感器Off 卡纸(翻转器)RAP (253)005135 CVT 面 2 预定位On 卡纸RAP (254)005136 CVT 面 2 定位On 卡纸RAP (255)005139 CVT 翻转传感器Off 卡纸RAP…………………………………… (256)005145 CVT 定位传感器Off 卡纸(翻转器)RAP (257)005146 CVT 预定位传感器Off 卡纸RAP (258)005147 CVT 预定位传感器Off 卡纸(翻转器)RA P (259)005194 在FF 混合尺寸中SS 尺寸不匹配卡纸RAP (260)005196 CVT 尺寸不匹配卡纸(无混合)RAP (261)005197 禁止组合尺寸卡纸RAP (262)005198 太短尺寸卡纸RAP (263)005199 太长尺寸卡纸RAP (264)005280 DADF EEPROM 故障RAP (265)005283 DADF 高度传感器逻辑故障RAP (265)005284 DADF APS 传感器故障RAP (266)005285 DADF 轻推辊提升故障RAP (267)005286 DADF 输出传感器故障RAP (268)005302 DADF 输送器盖联锁打开RAP (269)005304 CVT 稿台联锁打开RAP (270)005305 CVT 输送器联锁打开(运行)RAP (270)005307 CVT 稿台联锁在运行中打开RA (271)005906 CVT 输送传感器静态卡纸RAP (271)005907 CVT 预定位传感器静态卡纸RAP (272)005908 CVT 定位传感器静态卡纸RAP (272)005913 CVT 翻转传感器静态卡纸RAP (273)005915 CVT APS No1 传感器静态卡纸RAP (273)005916 CVT APS No2 传感器静态卡纸RAP …………………………………274005917 CVT APS No3 传感器静态卡纸RAP (274)005942 DADF 中放置的原稿故障RAP (275)005943 DADF 盘提升故障RAP (276)010xxx 定影器2nd Version 09/ 状态指示维修DC236/286 21010313 控制热敏电阻故障RAP (277)010314 侧端热敏电阻故障RAP (277)010318 热下跌恢复故障RAP (278)010320 热辊过热故障RAP (278)010327 定影器On 时间故障RAP (279)010398 定影器锁位故障RAP (280)012xxx 装订器012111 装订器H传输入口传感器Off 卡纸RAP (281)012112 装订器H传输入口传感器On 卡纸RAP (282)012121 H传输出口传感器Off 卡纸RAP (283)012126 H传输入口传感器Off 卡纸RAP (284)012151 编辑盘入口传感器Off 卡纸RAP (285)012152 编辑盘入口传感器On 卡纸RAP (286)012161 装订器压板卡纸RAP (287)012162 H传输出口传感器On 卡纸RAP (288)012211 堆积盘故障RAP (289)012212 堆积盘上限故障RAP (290)012221 前对齐板原位传感器On 故障RAP (291)012223 前对齐板原位传感器Off 故障RAP (292)012224 后对齐板原位传感器Off 故障RAP (293)012260 排出压板原位传感器On 故障RAP (294)012263 后对齐板故障RAP (295)012282 排出压板原位传感器Off 故障RAP (296)012283 放置压板原位传感器On 故障RAP (297)012284 放置压板原位传感器Off 故障RAP (298)012291 装订器故障RAP ………………………………… (299)012293 装订前角传感器On 故障RAP (2100)012294 装订前角传感器Off 故障RAP (2101)012295 装订移动传感器On 故障RAP (2102)012296 装订移动传感器Off 故障RAP ………………………………… (2103)012301 装订器顶盖打开RAP (2104)012302 装订器前盖打开RAP (2104)012303 装订器H传输盖打开RAP (2105)012901 装订器H传输入口传感器静态卡纸RAP (2105)012902 H传输出口传感器静态卡纸RAP (2106)012903 纸张留在编辑盘入口传感器RAP (2106)012905 编辑盘纸张传感器静态卡纸RAP (2107)012923 H传输入口传感器静态卡纸BRAP (2107)016xxx 传真服务016210 SW 选项故障(HDD 不存在)RAP (2109)016211 SW 选项故障(系统存储器不足)RAP (2109)016212 SW 选项故障(页存储器不足)RAP …………………………………2110016213 SW 选项故障(打印机卡不存在)RAP (2110)016214 SW 选项故障(传真卡不存在)RAP (2111)016215 SW 选项故障(JPEG 板不存在)RAP (2111)016311 扫描器未安装RAP (2112)016315 IIT 接口故障RAP (2112)016316 未检测到页存储器RAP (2113)016317 页存储器中止标准RAP (2113)016318 页存储器中止选项RAP (2114)016321 传真模块故障RAP (2114)016322 JBA 帐户满RAP (2115)016450 SMB 主机名重复RAP (2115)016454 DNS 动态更新故障RAP (2116)016455 SNTP 服务器超时RAP (2116)016456 SNTP 时间异步RAP (2117)016503 SMTP 服务器重定向故障RAP (2117)016504 POP 服务器重定向故障RAP (2118)016505 POP 重定向验证故障RAP (2118)016600 KO 验证锁定RAP (2119)016601 非法访问检测RAP (2119)016701 ART EX 内存不足RAP (2120)016702 页缓冲器不足RAP (2120)016703 Email 至无效邮箱RAP (2121)016704 邮箱满RAP (2121)016705 安全打印故障RAP (2122)016706 最大用户数超出RAP (2122)016707 样本打印故障RAP (2123)016708 HD 因注解/水印图象而满RAP (2123)016709 ART EX 命令故障RAP (2124)016710 延时打印故障RAP (2124)016711 Email 传输尺寸限制超出RAP (2125)016712 PANTHER 能下低下(IFormatted)RAP (2125)016716 TIFF 数据溢出RAP (2126)016718 超出PCL6 存储器RAP (2126)016719 超出PCL 存储器RAP (2127)016720 PCL 命令故障RAP (2127)016721 其它错误RAP (2128)016722 作业被装订位置NG 删除RAP (2128)016728 不支持TIFF 数据RAP (2129)016729 TIFF 数据尺寸太大RAP (2129)016730 不支持ART 命令RAP (2130)016731 无效TIFF 数据RAP (2130)016732 表格未注册RAP (2131)016735 更新作业模板RAP (2131)016736 远程目录加锁错误 (2132)016737 远程加锁目录卸载错误 (2132)016746 不支持PDF 文件RAP (2133)016748 HD 满RAP (2133)016749 JCL 语法错误RAP (2134)016751 PDF 故障RAP (2134)016752 PDF 内存不足RAP (2135)016753 PDF 命令不匹配RAP (2135)016754 PDF LZW 未安装RAP (2136)016755 PDF 打印被禁止RAP (2136)016756 审计禁止服务RAP (2137)016757 审计无效用户RAP (2137)016758 审计禁止功能。
DeviceMaster Troubleshooting.Can’t open the serial port or there are no communications on the serial port when using the computer’s comm ports to send serial data.1. What does PortVision show regarding the Device Master? Highlight the folder in the top rightof the PortVision GUI so the Device Masters appear in the bottom right.In the above example, it shows 192.168.13.10 is unable to communicate over the network.Try opening a command prompt and doing a ‘Ping’ agai nst the IP Address (192.168.13.10.This is discussed later in this document. The instructions to use PortVision are here:/html/DM_PRO_RTS_SERIALHUB_pvpx.htmTo Download PortVision, go to this webpage:/html/DM_PRO_RTS_SERIALHUB_pvdx2.htm2. Is the Device Master communicating with the driver?a. In PortVision, examine the Software Version. If you are using the computer com portsto send data, then you are using the driver. PortVision will inform whether the driver iscommunicating to the DeviceMaster by noting whether the Software Version is NS-Linkor SocketServer. If it says SocketServer, then the driver is not communicating on port 4606 of the Device Master.b.Go to your computer’s Start Menu -> Comtrol -> DeviceMaster Driver ManagementConsolec.Highlight the Device Master on the left side of the GUId.Check, if using Mac Mode that the correct Mac address is displayed. If you see “00 C04E # # #, use the drop down and see if the Mac Address is displayed. Select if it is there, otherwise manually enter the Mac address using spaces between the hex number pairs.Depress the ‘Apply’ button.Go to the Advanced Tab in the Management Console and look at the “Device Status”. If it does not say “Device is Active and OK”, go back to the General Tab.e.Enter the IP Address of the Device Ma ster and select ‘IP Mode’ and click ‘Apply’.Go to the Advanced Tab and examine Device Status. If it is other than “Device is Active and OK”, then we need to see if you can ‘ping’ the Device Master.Note- if you don’t know the Device Master IP Ad dress, use Port Vision to scan thenetwork to detect the Device Master. Once the Device Master is found, highlight the folder in the top right of the GUI so the Device Master appears in the bottom right.If IP Mode works, then something is blocking layer 2 network protocol (Operating System, Switch or Router). IP Mode is just as effective as Mac Mode, IP Mode usesLayer 3 on the network stack. If IP Mode does not work either, then try the below steps to see if there is a network connection.f.Open a command prompt by depressing the ‘Windows key’ and ‘R key’ simultaneously.To bring up the command GUI. Type ‘cmd’ to get a command prompt.At the command prompt, type “ping <device_master_IP_address>. For example,assume the Device Master IP Address is 192.168.250.250, type “ping 192.168.250.250”.If there is anything oth er than , “reply from 192.168.250.250: bytes=32 time xmsTTL=xxx” where ‘x’ is a number, then you have network issues.Also, se e if you can open the web page for the Device Master’s IP Address(http://192.168.250.250 for example)For network issues, note that the computer running the driver must be using the samenetmask and IP Address range as the Device Master. For instance, if the Device Masteris using the IP Address of 192.168.250.250 and a Netmask of 255.255.0.0, then thecomputer should have an IP Address of 192. 168.250.xxx (enter number 1-249 or 251-254)(Computer network properties)(Device Master IP Address / Netmask)g.If ping still fails, connect the Ethernet cable directly to the Device Master’s Down Port (ifthere is one) or regular Ethernet port. Retry starting at Step ‘e’ above.h.If ping still fails, swap the Ethernet cable with a known good cable.i.If there are still problems communicating with the Device Master, call Support.3. Is the Serial Port already being used by an application or another computer?a.The figure below shows a computer with the MAC Address of 1c:1b:0d:40:56:f6 is usingPhysical Port 1 on the Device Master. My computer, 192.168.250.4 is connected to theDevice Master via my driver, but will not be able to open Port 1 because it is in use byanother computer.4. If all the above checks out, isolate whether the problem is between your computer and theDevice Master or is not. The best way to do this is to do a loopback test. For instructions on Loopback Tests, please see the “DeviceMaster Serial Port Testing .pd f file in/contribs/devicemaster/help_files/testing/。