Signaling trace on GSM/CDMA VoIP Gateway

Transcription

1 Signaling trace on GSM/CDMA VoIP Gateway Part1. Login the gateway & General Knowledge the command This is a document for some customers who need to get the logs on gateway Tips: The document is fit for all DWG models with firmware version 01/02xx0601 or later. Run system tool Telnet to login DWG unit. The default username and password is "admin". C:\Users\Administrator>telnet Welcome to Command Shell! Username:admin Password:***** ROS> There is only a litter commands in "ROS>" mode. If you need more commands you must enter the "" mode. Input "enable" to enter "" mode if you have in the "ROS>" mode. ROS> ROS> ROS>en Command in mode to enable debug ^config To exit mode exit

2 Command in mode to print the logs ^ada [076-16:19:23:350]ADA CONNECTED...,WELCOME! Part2. Signaling traces 1. ECC Traces Call details(ecc) is debug detailed information of call progress. With ECC trace, you will see the calling/called number, routing/number manipulation rules that match with current calls. Welcome to Command Shell! Username:admin Password:***** ROS>en ^config #####to start the trace, must to enable debug for the gateway #### deb port all Debug All!!. ##### set debug level for the gateway #### deb cli level debug then exit and entry into "ada" mode to output the logs,with the commands

3 ex ^ada ADA CONNECTED...,WELCOME! #### with turnon 84 to enable the output on the window #### turnon 84 Make a call then the logs will display on the window, example: Apr 18 07:52: mpe_ecc: <184> [ DEBUG] get route entry 29 Apr 18 07:52: mpe_ecc: <185> [ DEBUG] get route, to port:1 Apr 18 07:52: mpe_ecc: <186> [ DEBUG] ECC:<port:1>,<69,1,out_idle> Return sip index:69, dest:1!, nextstrtport:2 Apr 18 07:52: mpe_ecc: <187> [ DEBUG] ECC:<port:1> <==recv msg:sip_call_invite,localindex:69 Apr 18 07:52: mpe_ecc: <188> [ DEBUG] ECC:<port:1>,eccb:69, State:0(out_idle), calling:816, dial:10086 <==recv msg:sip_call_invite,localindex: 69 Apr 18 07:52: mpe_ecc: <189> [ DEBUG] ECC:<port:1>,<69,1,out_idle> <<== SIP_CALL_INVITE Apr 18 07:52: mpe_ecc: <190> [ DEBUG] ECC:<port:1> port 1 user register OK Apr 18 07:52: mpe_ecc: <191> [ DEBUG] ECC:<port:1>,<69,1,out_idle> set active ccb 69 Apr 18 07:52: mpe_ecc: <192> [ DEBUG] ECC:<port:1>,<69,1,out_idle> <<==recv invite, sdp:v=0 o= IN IP s=a conversation c=in IP t=0 0 m=audio RTP/AVP a=rtpmap:18 G729/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:101 telephone-event/8000

4 a=fmtp: a=sendrecv #### with turnoff 84 to disable the output #### turnoff SIP Trace It is necessary to enable debug with command "deb port all" before start to SIP trace. deb port all Debug All!!. deb sip msg all then exit and entry into output the SIP logs, with the commands: ex ^ada ADA CONNECTED...,WELCOME! #### with turnon 71 to enable the output on the window #### turnon 71 Make a call then the logs will display on the window, example:

5 Apr 18 08:01: mpe_sip: <232> [ DEBUG] <<---*** message from /5060,crypt:FALSE, proto:ud INVITE sip:10086@ SIP/2.0 Via: SIP/2.0/UDP :5060;branch=z9hG4bK From: lich <sip:816@ :5060>;tag= To: "10086" <sip:10086@ > Call-ID: @ CSeq: 1 INVITE Contact: <sip:816@ :5060> Max-Forwards: 70 Supported: replaces, join, path User-Agent: voip-phone Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, REFER, NOTIFY, INFO, PRACK, UPDATE, MESSAGE Content-Type: application/sdp Content-Length: 246 #### with turnoff 71 to disable the output #### turnoff Enable SIP and ECC trace at the same time If you want to enable SIP and ECC trace at the same time, as following steps: deb port all Debug All!!. deb sip msg all ex ^ada ADA CONNECTED...,WELCOME! turnon 84 turnon 71 With the turnoff 84 and turnoff 71 to disable trace after call complete.

6 4. Module Logs trace cmd Apr 18 08:14: mpe_sys: <249> [ DEBUG] set module channel at cmd:0 debug:on Command cmd is to enable trace port 0, 0 0 is port range that to be traced, 1 means enable debug, 0 means disable debug cmd Apr 18 08:20: mpe_sys: < 25> [ DEBUG] set module channel at cmd:0 debug:off Example: Trace module logs of port 5, the command should be cmd Trace module logs from port 3,4,5,6,7, the command should be cmd And disable the trace with command cmd Part3. How do I make decision to enable traces? 1. IP to mobile call failed? 1) Not sure if the call hinted to the gateway It s better to enable SIP trace to check INVITE request as well as calling and called number; 2) Call is hit to the gateway but not connect Enable ECC trace to analysis call routing and manipulation rules etc. 3) No idea with the calls To enable all traces: ECC, SIP 4) SMS/USSD Fail Enable ECC and module trace 2. Mobile to IP call failed Enable ECC and SIP trace to analysis the call handle well and check detailed error that generate in the gateway or response from opposite side.