Attached should be the output of this command:   snmpwalk.exe -v 2c -c REDACTED 10.25.0.19 1 > full-snmp.txt ... View more

The output should be that of a walk, so the whole tree:     ----------------------- New Test ----------------------- Paessler SNMP Tester 5.1.3 9/01/2018 14:53:13 (6 ms) : Device: 10.25.0.19 9/01/2018 14:53:13 (10 ms) : SNMP V2c 9/01/2018 14:53:13 (13 ms) : Walk 1.3.6.1.4.1.9.10.19.1.1.9 ----------------------- New Test ----------------------- Paessler SNMP Tester 5.1.3 9/01/2018 14:53:32 (8 ms) : Device: 10.25.0.19 9/01/2018 14:53:32 (11 ms) : SNMP V2c 9/01/2018 14:53:32 (15 ms) : Walk 1.3.6.1.2.1.1 9/01/2018 14:53:32 (26 ms) : 1.3.6.1.2.1.1.1.0 = "Cisco IOS Software, ISR Software (X86_64_LINUX_IOSD-UNIVERSALK9-M), Version 15.5(3)S6, RELEASE SOFTWARE (fc3) Technical Support: http://www.cisco.com/techsupport Copyright (c) 1986-2017 by Cisco Systems, Inc. Compiled Mon 24-Jul-17 20:26 by mcpre" 9/01/2018 14:53:32 (38 ms) : 1.3.6.1.2.1.1.2.0 = "1.3.6.1.4.1.9.1.2093" 9/01/2018 14:53:32 (50 ms) : 1.3.6.1.2.1.1.3.0 = "187836263" 9/01/2018 14:53:32 (61 ms) : 1.3.6.1.2.1.1.4.0 = "" 9/01/2018 14:53:32 (71 ms) : 1.3.6.1.2.1.1.5.0 = "hostname redacted" 9/01/2018 14:53:32 (83 ms) : 1.3.6.1.2.1.1.6.0 = "" 9/01/2018 14:53:32 (93 ms) : 1.3.6.1.2.1.1.7.0 = "78" 9/01/2018 14:53:32 (104 ms) : 1.3.6.1.2.1.1.8.0 = "0" As you can see from this output, it does actually produce a tree of answers when querying it. 1.3.6.1.4.1.9.10.19.1.1.9 however produces no results.   ... View more

The output should be that of a walk, so the whole tree:     ----------------------- New Test ----------------------- Paessler SNMP Tester 5.1.3 9/01/2018 14:53:13 (6 ms) : Device: 10.25.0.19 9/01/2018 14:53:13 (10 ms) : SNMP V2c 9/01/2018 14:53:13 (13 ms) : Walk 1.3.6.1.4.1.9.10.19.1.1.9 ----------------------- New Test ----------------------- Paessler SNMP Tester 5.1.3 9/01/2018 14:53:32 (8 ms) : Device: 10.25.0.19 9/01/2018 14:53:32 (11 ms) : SNMP V2c 9/01/2018 14:53:32 (15 ms) : Walk 1.3.6.1.2.1.1 9/01/2018 14:53:32 (26 ms) : 1.3.6.1.2.1.1.1.0 = "Cisco IOS Software, ISR Software (X86_64_LINUX_IOSD-UNIVERSALK9-M), Version 15.5(3)S6, RELEASE SOFTWARE (fc3) Technical Support: http://www.cisco.com/techsupport Copyright (c) 1986-2017 by Cisco Systems, Inc. Compiled Mon 24-Jul-17 20:26 by mcpre" 9/01/2018 14:53:32 (38 ms) : 1.3.6.1.2.1.1.2.0 = "1.3.6.1.4.1.9.1.2093" 9/01/2018 14:53:32 (50 ms) : 1.3.6.1.2.1.1.3.0 = "187836263" 9/01/2018 14:53:32 (61 ms) : 1.3.6.1.2.1.1.4.0 = "" 9/01/2018 14:53:32 (71 ms) : 1.3.6.1.2.1.1.5.0 = "tel-cube03.mechelen.intra" 9/01/2018 14:53:32 (83 ms) : 1.3.6.1.2.1.1.6.0 = "" 9/01/2018 14:53:32 (93 ms) : 1.3.6.1.2.1.1.7.0 = "78" 9/01/2018 14:53:32 (104 ms) : 1.3.6.1.2.1.1.8.0 = "0" As you can see from this output, it does actually produce a tree of answers when querying it. 1.3.6.1.4.1.9.10.19.1.1.9 however produces no results.   ... View more

I don't have that snmpwalk utility on a network that can directly access the device, but when I use the Paessler snmp tool, I simply get nothing.     ----------------------- New Test ----------------------- Paessler SNMP Tester 5.1.3 9/01/2018 13:21:48 (4 ms) : Device: 10.25.0.19 9/01/2018 13:21:48 (5 ms) : SNMP V2c 9/01/2018 13:21:48 (7 ms) : Walk 1.3.6.1.4.1.9.10.19.1.1.9   When I try something else, I do get information back:   ----------------------- New Test ----------------------- Paessler SNMP Tester 5.1.3 9/01/2018 13:23:28 (6 ms) : Device: 10.25.0.19 9/01/2018 13:23:28 (10 ms) : SNMP V2c 9/01/2018 13:23:28 (13 ms) : Walk 1.3.6.1.2.1.1.3 9/01/2018 13:23:28 (23 ms) : 1.3.6.1.2.1.1.3.0 = "187295866" ... View more

These are the dial-peers:   dial-peer voice 100 pots description Proximus destination-pattern +T no digit-strip port 0/1/0:15 ! dial-peer voice 300 pots description Alcatel destination-pattern +32152829[89]. no digit-strip port 0/1/1:15 ! dial-peer voice 200 voip description CUCM preference 2 session protocol sipv2 session target ipv4:10.160.9.10 destination e164-pattern-map 200 incoming uri via 200 voice-class codec 100 voice-class sip options-keepalive dtmf-relay rtp-nte   There are more, but they are just copies of dial-peer 300 with different number ranges. As I stated before: the e164-pattern-map includes individual numbers in e164 format. They represent the users who have migrated from the Legacy PBX to CUCM.   What kind of call do you want the debug output for. Also, I might not have the possibility to get that output immediately.   Kind regards,   Tom ... View more

This, I believe, is not true.   The e164-pattern-map towards CUCM only has specific numbers in them, no ranges, so it can't get any more specific to that. If we dial a CUCM number from the Legacy PBX, we still  get the interdigit timeout.    Also, having the # as a terminator, would involve end user training. Or where do you propose to insert the # in the dial-string?    Kind regards,   Tom ... View more

CUCM 11.5 ... View more

Hi   I'm sorry, I lost track of this.   It's just the point that I don't want to use any phone number, as there are multiple ranges that go over the same ISDN line. I would purely like to select the incoming dial-peer based on port for all calls coming in through ISDN, and then based on dial-peer groups select an outbound dial-peer. But the order of selection for the inbound dial-peers prevents me from having it selected based on port, because I always have some destination-pattern in a dial-peer somewhere that would also match.   Regards,   Tom ... View more

Both these answers assume one also logs in on the CIPC phone? Because we would like to avoid that if possible, since the devicename is already user specific, we would like to configure it with the users phone number configured on the phone directly. But that would mean this answer is not valid. If it is not possible otherwise, we probably will have to go this route, that you still have to log in on a CIPC, but it would be nicer if we wouldn't need to go this route. ... View more