Cisco − Troubleshooting Cisco Voice Connection Trunks

.......................................................................................................................................................................................................................................................3 Determining What Calls are Up ................2 Common Issues for Connection Trunks.....................................................................................................................................................................................................................................................10 Related Topics........................................................................................................................................................................................................................................3 Beginning Troubleshooting...................10 Additional Documentation .........................................................................................................................................................................9 Tools Information..............................................................................................................................................................Cisco − Troubleshooting Cisco Voice Connection Trunks Table of Contents Troubleshooting Voice Connection Trunks .........10 Related Information.....................................................................8 DTMF Troubleshooting.....................................................................1 Solution................................1 Introduction..................................................................................................11 i .......................................................1 Problem...

When using voice trunks the PBX signaling has to match end−to−end. This document troubleshoots these problems. the trunks will function properly. either Voice over IP (VoIP). This is one of the known problems with connection trunks and can be caused by many different issues. As long as the PBXs at both ends are doing the same signaling. Cisco − Troubleshooting Cisco Voice Connection Trunks . The trunk does not care about the signal type that is used. In connection trunks. or Voice over ATM (VoATM). Any commands that you would normally issue under the voice port for signaling characteristics are not relevant and helpful. The calls are established as soon as the router is turned up and the configuration is complete. and signaling from Private Branch Exchange (PBX) to PBX not being transported properly. and complete the call to the other end through the corresponding dial peers.Troubleshooting Voice Connection Trunks Introduction Problem Solution Common Issues for Connection Trunks Beginning Troubleshooting Determining What Calls are Up DTMF Troubleshooting Tools Information Related Information Related Topics Additional Documentation Introduction Voice connection trunks are permanently established voice calls. Once this connection is established. Problem Most problems pertaining to trunks are transparent to the router and therefore very challenging to troubleshoot. it will still come up even if the signaling does not match at both ends. The voice trunk becomes a signaling conduit and relays the signal across the VoIP link. signaling takes on a different behavior once voice trunks are up and functioning. as far as the router is concerned. When the trunk comes up it becomes a software cable and the signal type is considered a connector type. the voice call is in session and connected. As soon as the voice ports are turned up. with routers being completely transparent while establishing a clear link between the two PBXs in the whole process. Other issues are Dual Tone Multifrequency (DTMF) tones not being passed properly. as far as the two PBX machines are concerned. they place a call to the location by automatically dialing the dummy phone number specified under the voice port. The goal is to make the voice trunk connection look identical to a leased T1 line to the PBX. Voice over Frame Relay (VoFR). Most issues seen with voice trunks are manifested by placing a call over the trunks and hearing silence.

Note: You may want to disable Voice Activity Detection (VAD) for troubleshooting purposes. after the trunks are verified. This could be one cause if the trunks are flapping constantly in a network. The terms "sent to dsp" and "received from dsp" are from the Cisco IOS® point of view. This debug will not generate any output until trunk keepalives are missed. Before proceeding to look at the signaling. These are messages that are seen while there is no activity happening on the trunks. it makes the debugs much easier to interpret. verify that the trunks are up and that the Digital Signal Processors (DSPs) are processing the voice packets. You can verify these keepalives by issuing the debug vpm signal command. If there are many trunks. you need to look at the Telephony signaling in order to troubleshoot further. and nobody is trying to make a call. The keepalive messages let the routers on each end of the circuit know that the trunks are still up. Once it has been verified that the trunks are functioning correctly. the output from issuing debug vpm commands can be limited to a single port by issuing the debug vpm port x command option. as shown in the following example: 21:21:08: 21:21:12: 21:21:13: 21:21:17: 21:21:18: 21:21:22: 21:21:23: 21:21:27: 21:21:28: 21:21:32: [3/0:0(1)] [3/0:0(1)] [3/0:0(1)] [3/0:0(1)] [3/0:0(1)] [3/0:0(1)] [3/0:0(1)] [3/0:0(1)] [3/0:0(1)] [3/0:0(1)] rcv from dsp SIG DCBA state 0x0 send to dsp SIG DCBA state 0x0 rcv from dsp SIG DCBA state 0x0 send to dsp SIG DCBA state 0x0 rcv from dsp SIG DCBA state 0x0 send to dsp SIG DCBA state 0x0 rcv from dsp SIG DCBA state 0x0 send to dsp SIG DCBA state 0x0 rcv from dsp SIG DCBA state 0x0 send to dsp SIG DCBA state 0x0 The keepalives are being sent and received every five seconds. trunk keepalive messages are sent back and forth between the remote boxes. you can issue the debug vpm trunk−sc command. The following is the output from issuing the debug vpm signal command when you look at all the ports: 21:18:12: 21:18:12: 21:18:12: 21:18:12: 21:18:12: 21:18:12: 21:18:12: 21:18:12: 21:18:12: 21:18:12: 21:18:13: 21:18:13: [3/0:10(11)] send to dsp sig DCBA state 0x0 [3/0:0(1)] rcv from dsp SIG DCBA state 0x0 [3/0:12(13)] rcv from dsp SIG DCBA state 0x0 [3/0:20(21)] rcv from dsp SIG DCBA state 0x0 [3/0:12(13)] send to dsp SIG DCBA state 0x0 [3/0:20(21)] send to dsp SIG DCBA state 0x0 [3/0:0(1)] send to dsp SIG DCBA state 0x0 [3/0:3(4)] rcv from dsp SIG DCBA state 0x0 [3/0:9(10)] rcv from dsp SIG DCBA state 0x0 [3/0:3(4)] send to dsp SIG DCBA state 0x0 [3/0:9(10)] send to dsp SIG DCBA state 0x0 [3/0:19(20)] rcv from dsp SIG DCBA state 0x0 If you limit this. These keepalives verify trunk connectivity and carry signaling information from end−to−end. where "x" is the voice port in question.Solution The approach to take when troubleshooting connection trunk issues is different than that used for switched calls. you need to look to the PBX signaling to see what is really happening. Generally. by entering the debug vpm port x command. If the trunks are established. To verify whether voice trunk keepalives are being sent and received. Missing five of these messages in a row will cause the trunk to go down. The following is an example of the debug vpm trunk−SC command output when keepalives are missed: 22:22:38: 3/0:22(23): lost Keepalive Cisco − Troubleshooting Cisco Voice Connection Trunks . You could substitute PBX for DSP and it may make it more understandable.

it is best to have a Telnet session to each router in question so that the signaling can be observed as it is passed from one end to the other. no keepalives are being missed. This document uses EMwink signaling since it is fairly popular and wink timing has to be taken into consideration. Common Issues for Connection Trunks There are several bugs associated with voice trunk connections. The following is the output from the router connected to the PBX that originates the call: May 22 19:39:03. Turn off VAD. check that the packet counters are incrementing by issuing the show call active voice brief command. TRUNK_SC_CONN_WO_CLASS ==> TRUNK_SC_CONN_DEFAULT_IDLE If no output is seen from issuing the debug vpm trunk−SC command. event TRUNK_RTC_LOST_KEEPALI trunk_rtc_set_AIS on trunk_rtc_gen_pattern : SIG pattern 0x0 TRUNK_SC. to troubleshoot analog EMconnectivity problems. For this. • Are the DSPs processing packets? − Issue the show voice dsp command to verify this. It may seem like a good idea to bring down the trunks and configure the routers so that they work at each end. TRUNK_SC_CONN_WO_CLASS ==> TRUNK_SC_CONN_DEFAULT_IDLE lost Keepalive TRUNK_SC state : TRUNK_SC_CONN_WO_CLASS. Once everything is verified as functioning correctly. This means that a connection would have to be down for 25 seconds before the trunks will go down. By the time Cisco IOS Software 12.582: [3/0:0(1)] !−−−It is in idle state. but the approach is really counter−productive since anything that you changed now becomes moot once the trunks are established. May 22 19:39:07. it may be because VAD is enabled and is suppressing packets. May 22 19:39:08. This command will also show whether VAD is enabled for the call leg in question. The ideal way to troubleshoot voice trunk connection problems is by examining the signaling that is being passed between the PBXs. most of these issues had been addressed and integrated. and make sure that the trunks are in the S_CONNECTED state. If the trunks are connecting analog ports at any site. bring the trunks up and look at the signaling that is being passed between the PBXs. Refer to Voice − Understanding and Troubleshooting Analog EMInterface Types and Wiring Arrangements. Look through the bugs and be aware that these could be the cause of problems with older code.2 was released. event TRUNK_RTC_LOST_KEEPALI trunk_rtc_set_AIS on trunk_rtc_gen_pattern : SIG pattern 0x0 TRUNK_SC. Also. Even if keepalives are being missed.586: [3/0:0(1)] May 22 19:39:12. re−establish trunks and look again. Beginning Troubleshooting It is necessary to look at the basics to establish that the following are working correctly: • Are the trunks established? − Issue the show voice call summary command. Check these if you see anything unusual. One of the most common issues is getting the PBXs to signal correctly over the trunk connection.22:22:38: 22:22:38: 22:22:38: 22:22:38: 22:22:39: 22:22:39: 22:22:39: 22:22:39: 22:22:39: 3/0:22(23): 3/0:22(23): 3/0:22(23): 3/0:22(23): 3/0:13(14): 3/0:13(14): 3/0:13(14): 3/0:13(14): 3/0:13(14): TRUNK_SC state : TRUNK_SC_CONN_WO_CLASS. it is best to verify the operation of the PBX in non−trunked mode.774: [3/0:0(1)] !−−−ABCD bits=0000. The best way to approach troubleshooting is with the trunks up and functional. the trunk will stay up until five sequential messages are missed. If you do not see packets being processed by the DSPs.778: [3/0:0(1)] rcv from dsp sig DCBA state 0x0 send to dsp SIG DCBA state 0x0 rcv from dsp SIG DCBA state 0x0 send to dsp SIG DCBA state 0x0 Cisco − Troubleshooting Cisco Voice Connection Trunks .

237: [3/0:0(1)] rcv from dsp SIG DCBA state 0xF May 22 19:39:40.593: [3/0:0(1)] rcv from dsp SIG DCBA state 0x0 May 22 19:39:27.569: [3/0:0(1)] send to dsp SIG DCBA state 0x0 Cisco − Troubleshooting Cisco Voice Connection Trunks .817: [3/0:0(1)] rcv from dsp SIG DCBA state 0xF !−−− Receives off−hook from PBX.157: [3/0:0(1)] rcv from dsp SIG DCBA state 0xF May 22 19:39:40.197: [3/0:0(1)] rcv from dsp SIG DCBA state 0xF May 22 19:39:40. May 22 19:39:40.785: [3/0:0(1)] send to dsp SIG DCBA state 0x0 May 22 19:39:33.449: [3/0:0(1)] send to dsp SIG DCBA state 0x0 May 22 19:39:40.117: [3/0:0(1)] rcv from dsp SIG DCBA state 0xF !−−− Receiving wink from remote side.289: [3/0:0(1)] send to dsp SIG DCBA state 0xF May 22 19:39:40.977: [3/0:0(1)] rcv from dsp SIG DCBA state 0xF May 22 19:39:39.777: [3/0:0(1)] send to dsp SIG DCBA state 0x0 May 22 19:39:18.597: [3/0:0(1)] rcv from dsp SIG DCBA state 0x0 May 22 19:39:32.529: [3/0:0(1)] send to dsp SIG DCBA state 0x0 May 22 19:39:40.409: [3/0:0(1)] send to dsp SIG DCBA state 0x0 May 22 19:39:40.249: [3/0:0(1)] send to dsp SIG DCBA state 0xF May 22 19:39:40.429: [3/0:0(1)] send to dsp SIG DCBA state 0x0 May 22 19:39:40.781: [3/0:0(1)] send to dsp SIG DCBA state 0x0 May 22 19:39:28. and passes to PBX. May 22 19:39:40.597: [3/0:0(1)] rcv from dsp SIG DCBA state 0x0 May 22 19:39:37.037: [3/0:0(1)] rcv from dsp SIG DCBA state 0xF May 22 19:39:40.213: [3/0:0(1)] send to dsp SIG DCBA state 0xF May 22 19:39:40.586: [3/0:0(1)] rcv from dsp SIG DCBA state 0x0 May 22 19:39:17. and passes to PBX.789: [3/0:0(1)] send to dsp SIG DCBA state 0x0 May 22 19:39:38.509: [3/0:0(1)] send to dsp SIG DCBA state 0x0 May 22 19:39:40.601: [3/0:0(1)] rcv from dsp SIG DCBA state 0x0 May 22 19:39:39.469: [3/0:0(1)] send to dsp SIG DCBA state 0x0 May 22 19:39:40.017: [3/0:0(1)] rcv from dsp SIG DCBA state 0xF May 22 19:39:40.229: [3/0:0(1)] send to dsp SIG DCBA state 0xF May 22 19:39:40.089: [3/0:0(1)] send to dsp SIG DCBA state 0x0 May 22 19:39:40.149: [3/0:0(1)] send to dsp SIG DCBA state 0xF May 22 19:39:40.877: [3/0:0(1)] rcv from dsp SIG DCBA state 0xF May 22 19:39:39.957: [3/0:0(1)] rcv from dsp SIG DCBA state 0xF May 22 19:39:39.837: [3/0:0(1)] rcv from dsp SIG DCBA state 0xF May 22 19:39:39.997: [3/0:0(1)] rcv from dsp SIG DCBA state 0xF May 22 19:39:40.May 22 19:39:13.217: [3/0:0(1)] rcv from dsp SIG DCBA state 0xF May 22 19:39:40.177: [3/0:0(1)] rcv from dsp SIG DCBA state 0xF May 22 19:39:40.329: [3/0:0(1)] send to dsp SIG DCBA state 0xF May 22 19:39:40.189: [3/0:0(1)] send to dsp SIG DCBA state 0xF May 22 19:39:40.057: [3/0:0(1)] rcv from dsp SIG DCBA state 0xF May 22 19:39:40.137: [3/0:0(1)] rcv from dsp SIG DCBA state 0xF May 22 19:39:40.897: [3/0:0(1)] rcv from dsp SIG DCBA state 0xF May 22 19:39:39.129: [3/0:0(1)] send to dsp SIG DCBA state 0xF May 22 19:39:40.857: [3/0:0(1)] rcv from dsp SIG DCBA state 0xF May 22 19:39:39.917: [3/0:0(1)] rcv from dsp SIG DCBA state 0xF May 22 19:39:39.077: [3/0:0(1)] rcv from dsp SIG DCBA state 0xF May 22 19:39:40.349: [3/0:0(1)] send to dsp SIG DCBA state 0x0 !−−− Wink ended from remote side.309: [3/0:0(1)] send to dsp SIG DCBA state 0xF May 22 19:39:40.797: [3/0:0(1)] rcv from dsp SIG DCBA state 0x0 May 22 19:39:39.549: [3/0:0(1)] send to dsp SIG DCBA state 0x0 May 22 19:39:40. and passes to remote end.493: [3/0:0(1)] send to dsp SIG DCBA state 0x0 May 22 19:39:40.109: [3/0:0(1)] send to dsp SIG DCBA state 0x0 May 22 19:39:40.781: [3/0:0(1)] send to dsp SIG DCBA state 0x0 May 22 19:39:23.593: [3/0:0(1)] rcv from dsp SIG DCBA state 0x0 May 22 19:39:22.269: [3/0:0(1)] send to dsp SIG DCBA state 0xF May 22 19:39:40.389: [3/0:0(1)] send to dsp SIG DCBA state 0x0 May 22 19:39:40.257: [3/0:0(1)] rcv from dsp SIG DCBA state 0xF May 22 19:39:40. May 22 19:39:39.097: [3/0:0(1)] rcv from dsp SIG DCBA state 0xF May 22 19:39:40.937: [3/0:0(1)] rcv from dsp SIG DCBA state 0xF May 22 19:39:39.169: [3/0:0(1)] send to dsp SIG DCBA state 0xF May 22 19:39:40.777: [3/0:0(1)] rcv from dsp SIG DCBA state 0x0 May 22 19:39:39.369: [3/0:0(1)] send to dsp SIG DCBA state 0x0 May 22 19:39:40.

565: [3/0:0(1)] send to dsp SIG DCBA state 0xF May 22 19:40:05.629: [3/0:0(1)] send to dsp SIG DCBA state 0x0 May 22 19:39:40.261: [3/0:0(1)] rcv from dsp SIG DCBA state 0xF May 22 19:39:50.568: [3/0:0(1)] send to dsp SIG DCBA state 0xF May 22 19:40:15.649: [3/0:0(1)] send to dsp SIG DCBA state 0x0 May 22 19:39:40.572: [3/0:0(1)] send to dsp SIG DCBA state 0xF May 22 19:40:19.589: [3/0:0(1)] send to dsp SIG DCBA state 0x0 May 22 19:39:40.441: [3/0:0(1)] send to dsp SIG DCBA state 0xF May 22 19:39:50.689: [3/0:0(1)] send to dsp SIG DCBA state 0x0 May 22 19:39:40.481: [3/0:0(1)] send to dsp SIG DCBA state 0xF May 22 19:39:50.272: [3/0:0(1)] rcv from dsp SIG DCBA state 0xF May 22 19:40:10.756: [3/0:0(1)] send to dsp SIG DCBA state 0x0 May 22 19:40:19.321: [3/0:0(1)] send to dsp SIG DCBA state 0xF May 22 19:39:50.341: [3/0:0(1)] send to dsp SIG DCBA state 0xF May 22 19:39:50.461: [3/0:0(1)] send to dsp SIG DCBA state 0xF May 22 19:39:50.261: [3/0:0(1)] send to dsp SIG DCBA state 0xF May 22 19:39:50.561: [3/0:0(1)] send to dsp SIG DCBA state 0xF May 22 19:40:00.736: [3/0:0(1)] send to dsp SIG DCBA state 0x0 May 22 19:40:19.121: [3/0:0(1)] send to dsp SIG DCBA state 0xF !−−− Wink ends.856: [3/0:0(1)] send to dsp SIG DCBA state 0x0 May 22 19:40:19.281: [3/0:0(1)] send to dsp SIG DCBA state 0xF May 22 19:39:50.876: [3/0:0(1)] send to dsp SIG DCBA state 0x0 Cisco − Troubleshooting Cisco Voice Connection Trunks .836: [3/0:0(1)] rcv from dsp SIG DCBA state 0x0 !−−− Both side hung up.265: [3/0:0(1)] rcv from dsp SIG DCBA state 0xF May 22 19:39:55.716: [3/0:0(1)] send to dsp SIG DCBA state 0x0 May 22 19:40:19.836: [3/0:0(1)] send to dsp SIG DCBA state 0x0 May 22 19:40:19. the conversation happens.276: [3/0:0(1)] rcv from dsp SIG DCBA state 0xF May 22 19:40:15.561: [3/0:0(1)] send to dsp SIG DCBA state 0xF May 22 19:39:55.161: [3/0:0(1)] send to dsp SIG DCBA state 0xF May 22 19:39:50.856: [3/0:0(1)] rcv from dsp SIG DCBA state 0x0 May 22 19:40:19. the remote end is now off−hook.773: [3/0:0(1)] send to dsp SIG DCBA state 0x0 May 22 19:39:50.361: [3/0:0(1)] send to dsp SIG DCBA state 0xF May 22 19:39:50. May 22 19:39:50.421: [3/0:0(1)] send to dsp SIG DCBA state 0xF May 22 19:39:50.696: [3/0:0(1)] send to dsp SIG DCBA state 0xF May 22 19:40:19.769: [3/0:0(1)] send to dsp SIG DCBA state 0x0 May 22 19:39:45.796: [3/0:0(1)] rcv from dsp SIG DCBA state 0xF May 22 19:40:19.501: [3/0:0(1)] send to dsp SIG DCBA state 0xF May 22 19:39:50.613: [3/0:0(1)] send to dsp SIG DCBA state 0x0 May 22 19:39:40.081: [3/0:0(1)] send to dsp SIG DCBA state 0x0 May 22 19:39:50.749: [3/0:0(1)] send to dsp SIG DCBA state 0x0 May 22 19:39:40. back to idle state.709: [3/0:0(1)] send to dsp SIG DCBA state 0x0 May 22 19:39:40.676: [3/0:0(1)] send to dsp SIG DCBA state 0xF May 22 19:40:19.269: [3/0:0(1)] rcv from dsp SIG DCBA state 0xF May 22 19:40:00.301: [3/0:0(1)] send to dsp SIG DCBA state 0xF May 22 19:39:50.381: [3/0:0(1)] send to dsp SIG DCBA state 0xF May 22 19:39:50.241: [3/0:0(1)] send to dsp SIG DCBA state 0xF May 22 19:39:50.541: [3/0:0(1)] send to dsp SIG DCBA state 0xF May 22 19:39:50.181: [3/0:0(1)] send to dsp SIG DCBA state 0xF May 22 19:39:50.268: [3/0:0(1)] rcv from dsp SIG DCBA state 0xF May 22 19:40:05.May 22 19:39:40.669: [3/0:0(1)] send to dsp SIG DCBA state 0x0 May 22 19:39:40.729: [3/0:0(1)] send to dsp SIG DCBA state 0x0 May 22 19:39:40.101: [3/0:0(1)] send to dsp SIG DCBA state 0x0 May 22 19:39:50.221: [3/0:0(1)] send to dsp SIG DCBA state 0xF May 22 19:39:50.564: [3/0:0(1)] send to dsp SIG DCBA state 0xF May 22 19:40:10. May 22 19:40:19.776: [3/0:0(1)] send to dsp SIG DCBA state 0x0 May 22 19:40:19.816: [3/0:0(1)] send to dsp SIG DCBA state 0x0 May 22 19:40:19.141: [3/0:0(1)] send to dsp SIG DCBA state 0xF May 22 19:39:50.816: [3/0:0(1)] rcv from dsp SIG DCBA state 0xF May 22 19:40:19.401: [3/0:0(1)] send to dsp SIG DCBA state 0xF May 22 19:39:50.796: [3/0:0(1)] send to dsp SIG DCBA state 0x0 May 22 19:40:19.197: [3/0:0(1)] send to dsp SIG DCBA state 0xF May 22 19:39:50.521: [3/0:0(1)] send to dsp SIG DCBA state 0xF May 22 19:39:50.

602: [3/0:0(1)] send to dsp SIG DCBA state 0x0 May 22 19:39:39.110: [3/0:0(1)] rcv from dsp SIG DCBA state 0x0 May 22 19:39:40.838: [3/0:0(1)] send to dsp SIG DCBA state 0xF May 22 19:39:39.018: [3/0:0(1)] send to dsp SIG DCBA state 0xF May 22 19:39:40.594: [3/0:0(1)] send to dsp SIG DCBA state 0x0 May 22 19:39:27.178: [3/0:0(1)] send to dsp SIG DCBA state 0xF May 22 19:39:40.896: 19:40:19.190: [3/0:0(1)] rcv from dsp SIG DCBA state 0xF May 22 19:39:40.782: [3/0:0(1)] rcv from dsp SIG DCBA state 0x0 May 22 19:39:33.038: [3/0:0(1)] send to dsp SIG DCBA state 0xF May 22 19:39:40.916: 19:40:19.798: [3/0:0(1)] send to dsp SIG DCBA state 0x0 May 22 19:39:39.590: [3/0:0(1)] send to dsp SIG DCBA state 0x0 May 22 19:39:22.774: [3/0:0(1)] rcv from dsp SIG DCBA state 0x0 !−−− Idle state.May May May May May May 22 22 22 22 22 22 19:40:19. May 22 19:39:08.938: [3/0:0(1)] send to dsp SIG DCBA state 0xF May 22 19:39:39.078: [3/0:0(1)] send to dsp SIG DCBA state 0xF May 22 19:39:40.118: [3/0:0(1)] send to dsp SIG DCBA state 0xF May 22 19:39:40. Network Time Protocol (NTP) is synced.818: [3/0:0(1)] send to dsp SIG DCBA state 0xF !−−− Remote side off−hook.130: [3/0:0(1)] rcv from dsp SIG DCBA state 0xF !−−− Receive wink from PBX.238: [3/0:0(1)] send to dsp SIG DCBA state 0xF May 22 19:39:40.916: 19:40:19.774: [3/0:0(1)] rcv from dsp SIG DCBA state 0x0 May 22 19:39:18.586: [3/0:0(1)] send to dsp SIG DCBA state 0x0 May 22 19:39:12.598: [3/0:0(1)] send to dsp SIG DCBA state 0x0 May 22 19:39:32. May 22 19:39:39. May 22 19:39:17.582: [3/0:0(1)] send to dsp SIG DCBA state 0x0 May 22 19:39:07.878: [3/0:0(1)] send to dsp SIG DCBA state 0xF May 22 19:39:39.858: [3/0:0(1)] send to dsp SIG DCBA state 0xF May 22 19:39:39.2(1a) or later.782: [3/0:0(1)] rcv from dsp SIG DCBA state 0x0 May 22 19:39:28.586: [3/0:0(1)] send to dsp SIG DCBA state 0x0 May 22 19:39:15.218: [3/0:0(1)] send to dsp SIG DCBA state 0xF May 22 19:39:40.598: [3/0:0(1)] send to dsp SIG DCBA state 0x0 May 22 19:39:37.230: [3/0:0(1)] rcv from dsp SIG DCBA state 0xF May 22 19:39:40.998: [3/0:0(1)] send to dsp SIG DCBA state 0xF May 22 19:39:40.896: 19:40:19. both side on−hook.936: [3/0:0(1)] [3/0:0(1)] [3/0:0(1)] [3/0:0(1)] [3/0:0(1)] [3/0:0(1)] rcv from dsp SIG DCBA state 0x0 send to dsp SIG DCBA state 0x0 rcv from dsp SIG DCBA state 0x0 send to dsp SIG DCBA state 0x0 rcv from dsp SIG DCBA state 0x0 send to dsp SIG DCBA state 0x0 The following output shows the router terminating the call.774: [3/0:0(1)] rcv from dsp SIG DCBA state 0x0 May 22 19:39:13.250: [3/0:0(1)] rcv from dsp SIG DCBA state 0xF Cisco − Troubleshooting Cisco Voice Connection Trunks .898: [3/0:0(1)] send to dsp SIG DCBA state 0xF May 22 19:39:39.198: [3/0:0(1)] send to dsp SIG DCBA state 0xF May 22 19:39:40. it is a normal functioning state.778: [3/0:0(1)] rcv from dsp SIG DCBA state 0x0 May 22 19:39:23.876: 19:40:19.098: [3/0:0(1)] send to dsp SIG DCBA state 0xF May 22 19:39:40.210: [3/0:0(1)] rcv from dsp SIG DCBA state 0xF May 22 19:39:40. May 22 19:39:40.170: [3/0:0(1)] rcv from dsp SIG DCBA state 0xF May 22 19:39:40.978: [3/0:0(1)] send to dsp SIG DCBA state 0xF May 22 19:39:39. May 22 19:39:03.958: [3/0:0(1)] send to dsp SIG DCBA state 0xF May 22 19:39:39.138: [3/0:0(1)] send to dsp SIG DCBA state 0xF May 22 19:39:40.158: [3/0:0(1)] send to dsp SIG DCBA state 0xF May 22 19:39:40.778: [3/0:0(1)] send to dsp SIG DCBA state 0x0 May 22 19:39:39.150: [3/0:0(1)] rcv from dsp SIG DCBA state 0xF May 22 19:39:40. It is not an error !−−− message.786: [3/0:0(1)] rcv from dsp SIG DCBA state 0x0 May 22 19:39:38.383: [1/0:0(1)] Signaling RTP packet has no particle !−−− You will see this message if you are running Cisco IOS !−−− Software Release 12.058: [3/0:0(1)] send to dsp SIG DCBA state 0xF May 22 19:39:40.918: [3/0:0(1)] send to dsp SIG DCBA state 0xF May 22 19:39:39.090: [3/0:0(1)] rcv from dsp SIG DCBA state 0x0 May 22 19:39:40. this is conveyed to the PBX.

262: [3/0:0(1)] send to dsp SIG DCBA state 0xF May 22 19:39:45.097: [3/0:0(1)] rcv from dsp SIG DCBA state 0x0 May 22 19:39:50.261: [3/0:0(1)] send to dsp SIG DCBA state 0xF May 22 19:39:50.650: [3/0:0(1)] rcv from dsp SIG DCBA state 0x0 May 22 19:39:40.357: [3/0:0(1)] rcv from dsp SIG DCBA state 0xF May 22 19:39:50.177: [3/0:0(1)] rcv from dsp SIG DCBA state 0xF May 22 19:39:50.710: [3/0:0(1)] rcv from dsp SIG DCBA state 0x0 May 22 19:39:40.517: [3/0:0(1)] rcv from dsp SIG DCBA state 0xF May 22 19:39:50. the conversation happens.590: [3/0:0(1)] rcv from dsp SIG DCBA state 0x0 May 22 19:39:40.297: [3/0:0(1)] rcv from dsp SIG DCBA state 0xF May 22 19:39:50.570: [3/0:0(1)] rcv from dsp SIG DCBA state 0x0 May 22 19:39:40.477: [3/0:0(1)] rcv from dsp SIG DCBA state 0xF May 22 19:39:50.270: [3/0:0(1)] rcv from dsp SIG DCBA state 0xF May 22 19:39:40.770: [3/0:0(1)] rcv from dsp SIG DCBA state 0x0 May 22 19:39:50.730: [3/0:0(1)] rcv from dsp SIG DCBA state 0x0 May 22 19:39:40.437: [3/0:0(1)] rcv from dsp SIG DCBA state 0xF May 22 19:39:50.310: [3/0:0(1)] rcv from dsp SIG DCBA state 0xF May 22 19:39:40.410: [3/0:0(1)] rcv from dsp SIG DCBA state 0x0 May 22 19:39:40.269: [3/0:0(1)] send to dsp SIG DCBA state 0xF May 22 19:40:05.337: [3/0:0(1)] rcv from dsp SIG DCBA state 0xF May 22 19:39:50.257: [3/0:0(1)] rcv from dsp SIG DCBA state 0xF May 22 19:39:50.750: [3/0:0(1)] rcv from dsp SIG DCBA state 0x0 May 22 19:39:40. May 22 19:39:40.561: [3/0:0(1)] rcv from dsp SIG DCBA state 0xF May 22 19:40:05.510: [3/0:0(1)] rcv from dsp SIG DCBA state 0x0 May 22 19:39:40.237: [3/0:0(1)] rcv from dsp SIG DCBA state 0xF May 22 19:39:50.269: [3/0:0(1)] send to dsp SIG DCBA state 0xF May 22 19:40:00. May 22 19:39:55.417: [3/0:0(1)] rcv from dsp SIG DCBA state 0xF May 22 19:39:50.550: [3/0:0(1)] rcv from dsp SIG DCBA state 0x0 May 22 19:39:40. waiting for an answer.450: [3/0:0(1)] rcv from dsp SIG DCBA state 0x0 May 22 19:39:40.430: [3/0:0(1)] rcv from dsp SIG DCBA state 0x0 May 22 19:39:40.277: [3/0:0(1)] rcv from dsp SIG DCBA state 0xF May 22 19:39:50.258: [3/0:0(1)] send to dsp SIG DCBA state 0xF May 22 19:39:40.377: [3/0:0(1)] rcv from dsp SIG DCBA state 0xF May 22 19:39:50.670: [3/0:0(1)] rcv from dsp SIG DCBA state 0x0 May 22 19:39:40.157: [3/0:0(1)] rcv from dsp SIG DCBA state 0xF May 22 19:39:50.265: [3/0:0(1)] send to dsp SIG DCBA state 0xF May 22 19:39:55.537: [3/0:0(1)] rcv from dsp SIG DCBA state 0xF May 22 19:39:50.217: [3/0:0(1)] rcv from dsp SIG DCBA state 0xF May 22 19:39:50.077: [3/0:0(1)] rcv from dsp SIG DCBA state 0x0 May 22 19:39:50. May 22 19:39:50.610: [3/0:0(1)] rcv from dsp SIG DCBA state 0x0 May 22 19:39:40.770: [3/0:0(1)] rcv from dsp SIG DCBA state 0x0 May 22 19:39:45.317: [3/0:0(1)] rcv from dsp SIG DCBA state 0xF May 22 19:39:50.630: [3/0:0(1)] rcv from dsp SIG DCBA state 0x0 May 22 19:39:40.497: [3/0:0(1)] rcv from dsp SIG DCBA state 0xF May 22 19:39:50.561: [3/0:0(1)] rcv from dsp SIG DCBA state 0xF Cisco − Troubleshooting Cisco Voice Connection Trunks .137: [3/0:0(1)] rcv from dsp SIG DCBA state 0xF May 22 19:39:50.557: [3/0:0(1)] rcv from dsp SIG DCBA state 0xF May 22 19:40:00.397: [3/0:0(1)] rcv from dsp SIG DCBA state 0xF May 22 19:39:50.117: [3/0:0(1)] rcv from dsp SIG DCBA state 0xF !−−− Receive off−hook from PBX.350: [3/0:0(1)] rcv from dsp SIG DCBA state 0x0 !−−− Wink ended.457: [3/0:0(1)] rcv from dsp SIG DCBA state 0xF May 22 19:39:50.530: [3/0:0(1)] rcv from dsp SIG DCBA state 0x0 May 22 19:39:40.May 22 19:39:40.370: [3/0:0(1)] rcv from dsp SIG DCBA state 0x0 May 22 19:39:40.690: [3/0:0(1)] rcv from dsp SIG DCBA state 0x0 May 22 19:39:40.390: [3/0:0(1)] rcv from dsp SIG DCBA state 0x0 May 22 19:39:40.470: [3/0:0(1)] rcv from dsp SIG DCBA state 0x0 May 22 19:39:40.290: [3/0:0(1)] rcv from dsp SIG DCBA state 0xF May 22 19:39:40.490: [3/0:0(1)] rcv from dsp SIG DCBA state 0x0 May 22 19:39:40.557: [3/0:0(1)] rcv from dsp SIG DCBA state 0xF !−−− Both sides off−hook.197: [3/0:0(1)] rcv from dsp SIG DCBA state 0xF May 22 19:39:50.330: [3/0:0(1)] rcv from dsp SIG DCBA state 0xF May 22 19:39:40.

Determining What Calls are Up Since it does little or no good to look at the show call active voice or show voice call summary command output for trunked calls.813: [3/0:0(1)] rcv from dsp SIG DCBA state 0x0 May 22 19:40:19. two−way audio should be present.857: [3/0:0(1)] send to dsp SIG DCBA state 0x0 May 22 19:40:19. last−TX−ABCD=0000.673: [3/0:0(1)] rcv from dsp SIG DCBA state 0xF May 22 19:40:19.May 22 19:40:10.565: [3/0:0(1)] rcv from dsp SIG DCBA state 0xF May 22 19:40:15. !−−− Timeslot 8. last−TX−ABCD=0000. Other types of signaling can be seen using these same debugs. last−TX−ABCD=0000. One of the easiest ways to do this is by issuing the show voice trunk−conditioning signaling command in conjunction with the include parameter using ABCD as the included string. last−TX−ABCD=0000. trunk−conditioning signaling | include ABCD last−RX−ABCD=0000 last−RX−ABCD=0000 last−RX−ABCD=0000 last−RX−ABCD=0000 last−RX−ABCD=0000 last−RX−ABCD=0000 last−RX−ABCD=0000 last−RX−ABCD=0000 last−RX−ABCD=0000 last−RX−ABCD=1111 last−RX−ABCD=0000 last−RX−ABCD=0000 last−RX−ABCD=0000 last−RX−ABCD=0000 last−RX−ABCD=0000 last−RX−ABCD=0000 The above output shows a call active on timeslot 10 and another call being started on timeslot 8. You may want to make an alias for this rather long command if you will be using it a lot.569: [3/0:0(1)] rcv from dsp SIG DCBA state 0xF May 22 19:40:19. last−TX−ABCD=1111.897: [3/0:0(1)] send to dsp SIG DCBA state 0x0 The above output shows the signaling that occurs on both sides of a voice trunk using EMwink signaling.773: [3/0:0(1)] rcv from dsp SIG DCBA state 0x0 May 22 19:40:19. This can be verified by looking at either the show voice dsp or the show call active voice brief command output.873: [3/0:0(1)] rcv from dsp SIG DCBA state 0x0 May 22 19:40:19. last−TX−ABCD=0000. last−TX−ABCD=0000. If everything looks alright there and you are getting audio problems (no audio or one−way) with analog connections.853: [3/0:0(1)] rcv from dsp SIG DCBA state 0x0 May 22 19:40:19. If you see calls established correctly (as shown above). you need a simple method to determine which voice trunks are supporting active calls.797: [3/0:0(1)] send to dsp SIG DCBA state 0xF May 22 19:40:19. back to idle. last−TX−ABCD=0000.817: [3/0:0(1)] send to dsp SIG DCBA state 0xF May 22 19:40:19.733: [3/0:0(1)] rcv from dsp SIG DCBA state 0x0 May 22 19:40:19.837: [3/0:0(1)] send to dsp SIG DCBA state 0x0 !−−− Both sides are back on−hook. last−TX−ABCD=0000. last−TX−ABCD=0000.693: [3/0:0(1)] rcv from dsp SIG DCBA state 0xF May 22 19:40:19. Cisco − Troubleshooting Cisco Voice Connection Trunks . !−−− Timeslot 10.713: [3/0:0(1)] rcv from dsp SIG DCBA state 0x0 May 22 19:40:19. last−TX−ABCD=1111. last−TX−ABCD=0000.273: [3/0:0(1)] send to dsp SIG DCBA state 0xF May 22 19:40:15. check these connections again.893: [3/0:0(1)] rcv from dsp SIG DCBA state 0x0 May 22 19:40:19. last−TX−ABCD=0000.753: [3/0:0(1)] rcv from dsp SIG DCBA state 0x0 May 22 19:40:19.833: [3/0:0(1)] rcv from dsp SIG DCBA state 0x0 May 22 19:40:19. last−TX−ABCD=0000. May 22 19:40:19. as shown in the following example: Phoenix#show voice last−TX−ABCD=0000.273: [3/0:0(1)] send to dsp SIG DCBA state 0xF May 22 19:40:10. last−TX−ABCD=0000.877: [3/0:0(1)] send to dsp SIG DCBA state 0x0 May 22 19:40:19.793: [3/0:0(1)] rcv from dsp SIG DCBA state 0x0 May 22 19:40:19.

As shown in the following example. E_VTSP_DIGIT] *Mar 1 00:22:45. This output will be displayed at the originating side. S_TRUNKED. E_VTSP_DIGIT] *Mar 1 00:22:40.249: htsp_digit_ready: digit = 30 *Mar 1 00:22:45. Depending upon how it is configured. This feature allows the DSPs at the end. The answer lies in using the dtmf−relay command. S_TRUNKED.499: [1/0:1(2)] Signaling RTP packet has no partical *Mar 1 00:22:41.789: htsp_digit_ready: digit = 37 *Mar 1 00:22:42.350: htsp_digit_ready: digit = 38 *Mar 1 00:22:43. How do you verify what digits are being passed if there is no call setup and you have to extract that information from the packet stream between the routers? How to do this depends upon what type of dtmf−relay command is being employed. not at the terminating side. uses a proprietary cisco payload type. You can issue the debug vpm signal command in conjunction with the debug vpm port x/x:y. Some people prefer to use the low bit rate codecs in order to save bandwidth.021: [1/0:1(2).628: htsp_digit_ready: digit = 23 *Mar 1 00:22:46. S_TRUNKED.815: [1/0:1(2)] rcv from dsp SIG DCBA state 0xF all digits 0−9 are represented by 30−39.592: [1/0:1(2).562: htsp_digit_ready: digit = 33 *Mar 1 00:22:40.672: htsp_digit_ready: digit = 35 *Mar 1 00:22:41. * = 2A and # = 23.249: [1/0:1(2).572: [1/0:1(2)] send to dsp SIG DCBA state 0xF *Mar 1 00:22:46.672: [1/0:1(2).007: htsp_digit_ready: digit = 2A *Mar 1 00:22:46. DTMF tones do not conform to these algorithms very well and need some other method of being conveyed unless the customer is using g711 codec. This feature poses another debugging problem for trunk troubleshooting. S_TRUNKED. E_VTSP_DIGIT] *Mar 1 00:22:42. S_TRUNKED. E_VTSP_DIGIT] *Mar 1 00:22:40. S_TRUNKED. Cisco − Troubleshooting Cisco Voice Connection Trunks . the only other thing that the routers pass between the PBXs (besides voice) are DTMF tones. originating the tone. S_TRUNKED.079: htsp_digit_ready: digit = 39 *Mar 1 00:22:44. There is also an audio path so this should not be a problem. S_TRUNKED.350: [1/0:1(2). the dtmf−relay cisco−rtp command.131: htsp_digit_ready: digit = 34 *Mar 1 00:22:41.628: [1/0:1(2). S_TRUNKED. to recognize the DTMF tone and separate it from the regular audio stream. E_VTSP_DIGIT] *Mar 1 00:22:43.810: [1/0:1(2)] rcv from dsp SIG DCBA state 0xF *Mar 1 00:22:46.021: htsp_digit_ready: digit = 32 *Mar 1 00:22:40.499: [1/0:1(2)] send to dsp SIG DCBA state 0xF *Mar 1 00:22:41.810: [1/0:1(2)] rcv from dsp SIG DCBA state 0xF *Mar 1 00:22:41. S_TRUNKED. The problem arises with how you are doing audio over that path.562: [1/0:1(2).192: htsp_digit_ready: digit = 36 *Mar 1 00:22:42. however.z command (to limit output to the port in question) to see the digits being passed to the DSPs at the originating side.DTMF Troubleshooting Aside from off−hook and on−hook signaling. E_VTSP_DIGIT] *Mar 1 00:22:41. E_VTSP_DIGIT] *Mar 1 00:22:40.131: [1/0:1(2). the DSP then codes this tone as either a different type of Real Time Protocol (RTP) packet or as an h245 message to be sent across the link separately from the audio stream. E_VTSP_DIGIT] *Mar 1 00:22:50.592: htsp_digit_ready: digit = 31 *Mar 1 00:22:39.079: [1/0:1(2). E_VTSP_DIGIT] *Mar 1 00:22:46. The issue comes up that these low bit rate codecs are designed using algorithms that were written for human speech.789: [1/0:1(2).011: [1/0:1(2). E_VTSP_DIGIT] *Mar 1 00:22:42.572: [1/0:1(2)] Signaling RTP packet has no partical *Mar 1 00:22:46. This is the same process behind the fax−relay and modem−relay commands. S_TRUNKED. S_TRUNKED. E_VTSP_DIGIT] *Mar 1 00:22:44. there is a problem. *Mar 1 00:22:39. so you must look down at the DSPs to see this. E_VTSP_DIGIT] *Mar 1 00:22:45.192: [1/0:1(2).

749: H245 MSC OUTGOING ENCODE BUFFER::= 6D 400131 1 00:34:17.350: 1 00:34:18.You can verify what digits are being sent from the originating side by issuing the dtmf−relay h245−alphanumric command. As shown in the following example.350: H245 MSC OUTGOING PDU ::= MultimediaSystemControlMessage ::= indication : userInput : alphanumeric : "2" 1 00:34:18. Tools Information For additional resources.838: H245 MSC OUTGOING ENCODE BUFFER::= 6D 400133 Terminating side: *Mar *Mar *Mar value *Mar *Mar *Mar value *Mar *Mar *Mar value 1 17:45:16.424: H245 MSC INCOMING ENCODE BUFFER::= 6D 400131 1 17:45:16.350: H245 MSC OUTGOING ENCODE BUFFER::= 6D 400132 1 00:34:18.514: H245 MSC INCOMING PDU ::= MultimediaSystemControlMessage ::= indication : userInput : alphanumeric : "3" The dtmf−relay h245−signal command is very similar and can be seen using the same debugs as the dtmf−relay h245−alphanumeric command. the digits can easily be seen at both the originating and the terminating sides of the trunk by enabling the debug h245 asn1 command: Originating side: *Mar 1 00:34:17.749: H245 MSC OUTGOING PDU ::= value MultimediaSystemControlMessage ::= indication : userInput : alphanumeric : "1" *Mar *Mar *Mar value *Mar *Mar *Mar value *Mar 1 00:34:17.753: 1 00:34:18.514: 1 17:45:17. The dtmf−relay h245−alphanumric command uses the alphanumeric portion of h. Overall.838: H245 MSC OUTGOING PDU ::= MultimediaSystemControlMessage ::= indication : userInput : alphanumeric : "3" 1 00:34:18.025: 1 17:45:17. refer to Cisco TAC Tools for Voice. troubleshooting connection trunks by issuing the dtmf−relay command is rather difficult without the debugs mentioned above. Related Information Related Topics • Configuring and Troubleshooting Transparent CCS • Configuring Voice Connection Trunk Cisco − Troubleshooting Cisco Voice Connection Trunks .514: H245 MSC INCOMING ENCODE BUFFER::= 6D 400133 1 17:45:17.245 to convey the tones. Telephony and Messaging Technologies.424: 1 17:45:16.424: H245 MSC INCOMING PDU ::= MultimediaSystemControlMessage ::= indication : userInput : alphanumeric : "1" 1 17:45:17.025: H245 MSC INCOMING PDU ::= MultimediaSystemControlMessage ::= indication : userInput : alphanumeric : "2" 1 17:45:17.025: H245 MSC INCOMING ENCODE BUFFER::= 6D 400132 1 17:45:17.

Inc. Telephony and Messaging Top Issues • Field Notices • Voice. Telephony and Messaging Technologies • Voice. Telephony and Messaging Products • Cisco Solutions Voice. 2002 Document ID: 23443 Cisco − Troubleshooting Cisco Voice Connection Trunks .Additional Documentation • Voice. All rights reserved. Updated: Sep 17. Important Notices and Privacy Statement. Telephony and Messaging Tac eLearning Solutions All contents are Copyright © 1992−−2002 Cisco Systems. Telephony and Messaging Technical Tips • Voice. Telephony and Messaging • Voice.

Sign up to vote on this title
UsefulNot useful