Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- Cisco Community
- :
- About Mikolaj Moryto
Stats
Member since
05-26-2014
64
Posts
65
Helpful
2
Solutions
Created by
Mikolaj Moryto
in Wireless and Mobility
in Wireless and Mobility
09-10-2019
08:39 AM
09-10-2019
08:39 AM
So that wasn't really an AP or WLC configuration issue. Below commands were doing what they were supposed to. debug capwap console cli
clear capwap ap all-config
erase /all nvram: The reason for getting "DTLS handshake" error was because I misconfigured the interfaces and put all of them into single port group on ESXi side. Once changing it AP instantly registered to the WLC. Thanks everyone for your assistance.
... View more
Created by
Mikolaj Moryto
in Wireless and Mobility
in Wireless and Mobility
09-09-2019
06:38 PM
09-09-2019
06:38 PM
That command worked after using "debug capwap console cli" but it did not solve the issue. I am still having the same "DTLS handshake" error on the controller side.
... View more
Created by
Mikolaj Moryto
in Wireless and Mobility
in Wireless and Mobility
09-09-2019
05:43 AM
09-09-2019
05:43 AM
These two commands are not available now when the AP is registered to vWLC. Does it need to be factory reset? When I did the factory reset with MODE button for the last time I did not see "clear capwap ap all-config" there either.
... View more
Created by
Mikolaj Moryto
in IP Telephony and Phones
in IP Telephony and Phones
09-08-2019
11:52 PM
09-08-2019
11:52 PM
Hi, Look at your debug closer. You do not receive any reply for the service provider to your INVITE. Your router sends 6 INVITES- 500ms, 1s, 2s, 4s and 8s after initial INVITE. You have your router set to send 5 retries and CUBE does it while doubling the time between retries (this is how it works). The question is why you do not receive 100-Trying from service provider. It's either them not receiving your INVITE or receiving but not responding to it. Do you have any firewalls between your router and sipgate that may block SIP?
... View more
Created by
Mikolaj Moryto
in Wireless and Mobility
in Wireless and Mobility
09-08-2019
11:28 PM
09-08-2019
11:28 PM
Hi Sandeep, Does the AP need to be in specific mode for that? I have it currently registered to vWLC and I have this: When I was trying previously with recovery mode (MODE button) I had "clear capwap ap" command available but "all-config" was not there. There were only "clear capwap ap controller", "clear capwap ap ip" but not "clear capwap ap all-config".
... View more
09-08-2019
04:10 PM
Hi, Because of some vWLC limitations I decided to test 9800-CL (16.11.1c) and after initial configuration I am stuck with AP not joining the controller. I followed all guides I could find and all discussions here I could find but nothing worked so far. Also tried to factory reset the AP with MODE button and clearing AP with following command: delete flash:private-multiple-fs
clear capwap private-multiple-fs As I want to migrate AP from vWLC to 9800 before factory resetting the AP I also tried to disable SSC and set authentication token on AP (through vWLC) and also on the 9800 side. That didn't work either. Initial configuration completed: - access (passwords, SSH, etc.) - interfaces - AP country - wireless management interface - wireless config vwlc-ssc key-size 2048 signature-algo sha256 password 0 <pwd> AP (DHCP - 192.168.1.8): *Sep 8 21:31:35.003: %LWAPP-3-CLIENTERRORLOG: Config load from flash failed. Initialising Cfg
*Sep 8 21:31:35.015: %LWAPP-3-CLIENTERRORLOG: Config load from flash failed. Initialising Cfg
*Sep 8 21:31:45.015: AP has SHA2 MIC certificate - Using SHA2 MIC certificate for DTLS.
*Sep 8 21:31:45.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.1.151 peer_port: 5246
*Sep 8 21:31:45.000: DTLS_CLIENT_EVENT: dtls_connectionDB_add_connection: Added Connection 0x57FC158 Server 192.168.1.151:147E, Client 192.168.1.8:2531
*Sep 8 21:31:45.000: DTLS_CLIENT_EVENT: dtls_process_HelloVerifyRequest: Processing...
*Sep 8 21:31:45.000: DTLS_CLIENT_EVENT: dtls_process_HelloVerifyRequest:
dtls_process_HelloVerifyRequest: cookie_len = 20
*Sep 8 21:31:45.003: DTLS_CLIENT_EVENT: dtls_process_ServerHello: Processing...
*Sep 8 21:31:45.003: DTLS_CLIENT_EVENT: dtls_connection_set_cipher: Setting cipher to TLS_RSA_WITH_AES_128_CBC_SHA
*Sep 8 21:31:45.003: DTLS_CLIENT_EVENT: dtls_connection_is_resumed_session:
DTLS connection database is initialized
*Sep 8 21:31:45.003: DTLS_CLIENT_EVENT: dtls_connection_is_resumed_session:
DTLS connection database is initialized
*Sep 8 21:31:45.003: DTLS_CLIENT_EVENT: dtls_process_Certificate: Processing...
*Sep 8 21:31:45.023: DTLS_CLIENT_EVENT: wtpDtlsCallback: Certificate verified ok!
*Sep 8 21:31:45.023: DTLS_CLIENT_EVENT: dtls_process_CertificateRequest: Processingt...
*Sep 8 21:31:45.023: DTLS_CLIENT_EVENT: dtls_process_ServerHelloDone: Processing...
*Sep 8 21:31:45.023: DTLS_CLIENT_EVENT: wtpDtlsCallback: Certificate installed for PKI based authentication.
*Sep 8 21:31:45.023: DTLS_CLIENT_EVENT: dtls_send_Certificate: Sending 1 certificates
*Sep 8 21:31:45.023: DTLS_CLIENT_EVENT: dtls_handshake_fragment_and_send: Re-aligning the last fragmenti by 1
*Sep 8 21:31:45.219: DTLS_CLIENT_EVENT: dtls_connection_is_resumed_session:
DTLS connection database is initialized
*Sep 8 21:31:45.219: DTLS_CLIENT_EVENT: dtls_prf: Called...
*Sep 8 21:31:45.219: DTLS_CLIENT_EVENT: dtls_prf: Called...
*Sep 8 21:31:45.219: DTLS_CLIENT_EVENT: dtls_prf: Called...
*Sep 8 21:31:45.219: DTLS_CLIENT_EVENT: dtls_connection_is_resumed_session:
DTLS connection database is initialized
*Sep 8 21:31:45.231: DTLS_CLIENT_EVENT: dtls_connection_is_resumed_session:
DTLS connection database is initialized
*Sep 8 21:31:45.231: DTLS_CLIENT_EVENT: dtls_process_Finished: Processing...
*Sep 8 21:31:45.231: DTLS_CLIENT_EVENT: dtls_prf: Called...
*Sep 8 21:31:45.231: DTLS_CLIENT_EVENT: dtls_connection_is_resumed_session:
DTLS connection database is initialized
*Sep 8 21:31:45.231: DTLS_CLIENT_EVENT: dtls_connection_is_resumed_session:
DTLS connection database is initialized
*Sep 8 21:31:45.231: DTLS_CLIENT_EVENT: dtls_connection_established: Connection established!
*Sep 8 21:31:45.231: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.1.151 peer_port: 5246
*Sep 8 21:31:45.231: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.1.151
*Sep 8 21:31:45.231: DTLS_CLIENT_EVENT: wtpDtlsCallback: DTLS-Ctrl Connection 0x57FC158 established
*Sep 8 21:31:50.231: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.1.151 9800-CL (static - 192.168.1.151): Sep 8 21:31:45.592: %CAPWAPAC_SMGR_TRACE_MESSAGE-3-EWLC_GEN_ERR: Chassis 1 R0/0: wncd: Error in Session-IP:192.168.1.8[9521] CAPWAP DTLS session closed for AP, cause: DTLS handshake error 2019/09/08 21:05:55.067 {wncd_x_R0-0}{1}: [capwapac-smgr-srvr] [23645]: (ERR): Unknown message type from load balancer, dropping
2019/09/08 21:05:55.067 {wncd_x_R0-0}{1}: [capwapac-smgr-srvr] [23645]: (ERR): Unknown message type from load balancer, dropping
2019/09/08 21:05:55.067 {wncd_x_R0-0}{1}: [capwapac-smgr-srvr] [23645]: (ERR): Unknown message type from load balancer, dropping
2019/09/08 21:05:55.084 {wncmgrd_R0-0}{1}: [capwapac-srvr] [23098]: (info): MAC: 80e0.1d92.530c IP:192.168.1.8[9521], Discovery Request received
2019/09/08 21:05:55.097 {wncmgrd_R0-0}{1}: [capwapac-srvr] [23098]: (info): MAC: 80e0.1d92.530c IP:192.168.1.8[9521], Discovery Response sent
2019/09/08 21:05:55.097 {wncmgrd_R0-0}{1}: [ewlc-infra-evq] [23098]: (debug): instance :0 port:11585MAC: 4b39.0001.000b
2019/09/08 21:05:55.097 {wncmgrd_R0-0}{1}: [capwapac-srvr] [23098]: (info): MAC: 80e0.1d92.530c Source IP:192.168.1.8[9521], Discovery handling completed for AP.
2019/09/08 21:05:55.097 {wncmgrd_R0-0}{1}: [capwapac-srvr] [23098]: (info): MAC: 80e0.1d92.530c IP:192.168.1.8[9521], Discovery Request received
2019/09/08 21:05:55.097 {wncmgrd_R0-0}{1}: [capwapac-srvr] [23098]: (info): MAC: 80e0.1d92.530c IP:192.168.1.8[9521], Discovery Response sent
2019/09/08 21:05:55.097 {wncmgrd_R0-0}{1}: [ewlc-infra-evq] [23098]: (debug): instance :0 port:11585MAC: 4b39.0001.000b
2019/09/08 21:05:55.097 {wncmgrd_R0-0}{1}: [capwapac-srvr] [23098]: (info): MAC: 80e0.1d92.530c Source IP:192.168.1.8[9521], Discovery handling completed for AP.
2019/09/08 21:05:55.097 {wncmgrd_R0-0}{1}: [capwapac-srvr] [23098]: (info): MAC: 80e0.1d92.530c IP:192.168.1.8[9521], Discovery Request received
2019/09/08 21:05:55.097 {wncmgrd_R0-0}{1}: [capwapac-srvr] [23098]: (info): MAC: 80e0.1d92.530c IP:192.168.1.8[9521], Discovery Response sent
2019/09/08 21:05:55.097 {wncmgrd_R0-0}{1}: [ewlc-infra-evq] [23098]: (debug): instance :0 port:11585MAC: 4b39.0001.000b
2019/09/08 21:05:55.097 {wncmgrd_R0-0}{1}: [capwapac-srvr] [23098]: (info): MAC: 80e0.1d92.530c Source IP:192.168.1.8[9521], Discovery handling completed for AP.
2019/09/08 21:05:55.098 {wncmgrd_R0-0}{1}: [capwapac-srvr] [23098]: (info): MAC: 80e0.1d92.530c IP:192.168.1.8[9521], Discovery Request received
2019/09/08 21:05:55.098 {wncmgrd_R0-0}{1}: [capwapac-srvr] [23098]: (info): MAC: 80e0.1d92.530c IP:192.168.1.8[9521], Discovery Response sent
2019/09/08 21:05:55.098 {wncmgrd_R0-0}{1}: [ewlc-infra-evq] [23098]: (debug): instance :0 port:11585MAC: 4b39.0001.000b
2019/09/08 21:05:55.098 {wncmgrd_R0-0}{1}: [capwapac-srvr] [23098]: (info): MAC: 80e0.1d92.530c Source IP:192.168.1.8[9521], Discovery handling completed for AP.
2019/09/08 21:05:55.098 {wncmgrd_R0-0}{1}: [capwapac-srvr] [23098]: (info): MAC: 80e0.1d92.530c IP:192.168.1.8[9521], Discovery Request received
2019/09/08 21:05:55.098 {wncmgrd_R0-0}{1}: [capwapac-srvr] [23098]: (info): MAC: 80e0.1d92.530c IP:192.168.1.8[9521], Discovery Response sent
2019/09/08 21:05:55.098 {wncmgrd_R0-0}{1}: [ewlc-infra-evq] [23098]: (debug): instance :0 port:11585MAC: 4b39.0001.000b
2019/09/08 21:05:55.098 {wncmgrd_R0-0}{1}: [capwapac-srvr] [23098]: (info): MAC: 80e0.1d92.530c Source IP:192.168.1.8[9521], Discovery handling completed for AP.
2019/09/08 21:05:55.098 {wncmgrd_R0-0}{1}: [capwapac-srvr] [23098]: (info): MAC: 80e0.1d92.530c IP:192.168.1.8[9521], Discovery Request received
2019/09/08 21:05:55.098 {wncmgrd_R0-0}{1}: [capwapac-srvr] [23098]: (info): MAC: 80e0.1d92.530c IP:192.168.1.8[9521], Discovery Response sent
2019/09/08 21:05:55.098 {wncmgrd_R0-0}{1}: [ewlc-infra-evq] [23098]: (debug): instance :0 port:11585MAC: 4b39.0001.000b
2019/09/08 21:05:55.098 {wncmgrd_R0-0}{1}: [capwapac-srvr] [23098]: (info): MAC: 80e0.1d92.530c Source IP:192.168.1.8[9521], Discovery handling completed for AP.
2019/09/08 21:06:05.082 {wncd_x_R0-0}{1}: [ewlc-infra-evq] [23645]: (info): DTLS record type: 22, handshake
2019/09/08 21:06:05.082 {wncd_x_R0-0}{1}: [ewlc-infra-evq] [23645]: (info): DTLS client hello
2019/09/08 21:06:05.083 {wncd_x_R0-0}{1}: [ewlc-infra-evq] [23645]: (info): DTLS record type: 22, handshake
2019/09/08 21:06:05.083 {wncd_x_R0-0}{1}: [ewlc-infra-evq] [23645]: (info): DTLS client hello
2019/09/08 21:06:05.083 {wncd_x_R0-0}{1}: [ewlc-infra-evq] [23645]: (info): DTLS record type: 22, handshake
2019/09/08 21:06:05.083 {wncd_x_R0-0}{1}: [ewlc-infra-evq] [23645]: (info): DTLS client hello
2019/09/08 21:06:05.084 {wncd_x_R0-0}{1}: [ewlc-infra-evq] [23645]: (info): DTLS record type: 22, handshake
2019/09/08 21:06:05.084 {wncd_x_R0-0}{1}: [ewlc-infra-evq] [23645]: (info): DTLS client hello
2019/09/08 21:06:05.085 {wncd_x_R0-0}{1}: [capwapac-smgr-srvr] [23645]: (ERR): IPv4: 192.168.1.8Failed to Process DTLS Hello message from loadbalancer server
2019/09/08 21:06:05.085 {wncd_x_R0-0}{1}: [capwapac-smgr-srvr] [23645]: (ERR): IPv4: 192.168.1.8Failed to Process DTLS Hello message from loadbalancer server
2019/09/08 21:06:05.303 {wncd_x_R0-0}{1}: [ewlc-infra-evq] [23645]: (info): DTLS record type: 22, handshake
2019/09/08 21:06:05.303 {wncd_x_R0-0}{1}: [ewlc-infra-evq] [23645]: (info): DTLS record type: 22, handshake
2019/09/08 21:06:05.303 {wncd_x_R0-0}{1}: [ewlc-infra-evq] [23645]: (info): DTLS record type: 22, handshake
2019/09/08 21:06:05.304 {wncd_x_R0-0}{1}: [ewlc-infra-evq] [23645]: (info): DTLS record type: 22, handshake
2019/09/08 21:06:05.304 {wncd_x_R0-0}{1}: [ewlc-infra-evq] [23645]: (info): DTLS record type: 22, handshake
2019/09/08 21:06:05.304 {wncd_x_R0-0}{1}: [ewlc-infra-evq] [23645]: (info): DTLS record type: 22, handshake
2019/09/08 21:06:05.304 {wncd_x_R0-0}{1}: [ewlc-infra-evq] [23645]: (info): DTLS record type: 22, handshake
2019/09/08 21:06:05.304 {wncd_x_R0-0}{1}: [ewlc-infra-evq] [23645]: (info): DTLS record type: 22, handshake
2019/09/08 21:06:05.304 {wncd_x_R0-0}{1}: [ewlc-infra-evq] [23645]: (info): DTLS record type: 0, unknown type
2019/09/08 21:06:05.304 {wncd_x_R0-0}{1}: [ewlc-infra-evq] [23645]: (info): DTLS record type: 22, handshake
2019/09/08 21:06:05.304 {wncd_x_R0-0}{1}: [ewlc-infra-evq] [23645]: (info): DTLS record type: 22, handshake
2019/09/08 21:06:05.304 {wncd_x_R0-0}{1}: [ewlc-infra-evq] [23645]: (info): DTLS record type: 22, handshake
2019/09/08 21:06:05.304 {wncd_x_R0-0}{1}: [ewlc-infra-evq] [23645]: (info): DTLS record type: 22, handshake
2019/09/08 21:06:05.304 {wncd_x_R0-0}{1}: [ewlc-infra-evq] [23645]: (info): DTLS record type: 22, handshake
2019/09/08 21:06:05.304 {wncd_x_R0-0}{1}: [ewlc-infra-evq] [23645]: (info): DTLS record type: 22, handshake
2019/09/08 21:06:05.304 {wncd_x_R0-0}{1}: [ewlc-infra-evq] [23645]: (info): DTLS record type: 0, unknown type
2019/09/08 21:06:05.304 {wncd_x_R0-0}{1}: [ewlc-infra-evq] [23645]: (info): DTLS record type: 22, handshake
2019/09/08 21:06:05.305 {wncd_x_R0-0}{1}: [ewlc-infra-evq] [23645]: (info): DTLS record type: 22, handshake
2019/09/08 21:06:05.305 {wncd_x_R0-0}{1}: [ewlc-infra-evq] [23645]: (info): DTLS record type: 22, handshake
2019/09/08 21:06:05.305 {wncd_x_R0-0}{1}: [ewlc-infra-evq] [23645]: (info): DTLS record type: 0, unknown type
2019/09/08 21:06:05.305 {wncd_x_R0-0}{1}: [ewlc-infra-evq] [23645]: (info): DTLS record type: 22, handshake
2019/09/08 21:06:05.308 {wncd_x_R0-0}{1}: [ewlc-dtls-sessmgr] [23645]: (info): Remote Host: 192.168.1.8[9521] Completed cert verification, status:CERT_VALIDATE_SUCCESS
2019/09/08 21:06:05.314 {wncd_x_R0-0}{1}: [capwapac-smgr-sess-fsm] [23645]: (info): Session-IP: 192.168.1.8[9521] Mac: Close CAPWAP DTLS session.
2019/09/08 21:06:05.314 {wncd_x_R0-0}{1}: [capwapac-smgr-sess-fsm] [23645]: (note): Session-IP: 192.168.1.8[9521] Mac: Last Control Packet information not available.AP terminated in DTLS phase.
2019/09/08 21:06:05.314 {wncd_x_R0-0}{1}: [capwapac-smgr-sess-fsm] [23645]: (note): Session-IP: 192.168.1.8[9521] Mac: Last Data Keep Alive Packet information not available.Data session was not established
2019/09/08 21:06:05.314 {wncd_x_R0-0}{1}: [apmgr-db] [23645]: (ERR): 80e0.1d92.530c Mismatch in session handles.Record already deleted and recreated
2019/09/08 21:06:10.312 {wncd_x_R0-0}{1}: [capwapac-smgr-srvr] [23645]: (ERR): Unknown message type from load balancer, dropping
2019/09/08 21:06:10.312 {wncd_x_R0-0}{1}: [capwapac-smgr-srvr] [23645]: (ERR): Unknown message type from load balancer, dropping
2019/09/08 21:06:10.312 {wncd_x_R0-0}{1}: [capwapac-smgr-srvr] [23645]: (ERR): Unknown message type from load balancer, dropping Thanks, Mikolaj
... View more
Labels:
Created by
Mikolaj Moryto
in Wireless and Mobility
in Wireless and Mobility
09-06-2019
12:31 AM
09-06-2019
12:31 AM
Hi, Disabling AVC improves the through for another 20-30% but it's far from reaching the value it gets with central switching. As with local switching more features are offloaded to AP I believe this is the reason for worse performance. Thanks everyone for their input. Regards, Mikolaj
... View more
Created by
Mikolaj Moryto
in Wireless and Mobility
in Wireless and Mobility
09-02-2019
02:52 PM
09-02-2019
02:52 PM
Upgraded to 8.5.151.0 and it is the same. At this point I believe it is the AP and its CPU not being fast enough for Flex AVC. During file transfer: Disabling AVC improves the throughput and CPU utilization goes down a bit
... View more
Created by
Mikolaj Moryto
in Wireless and Mobility
in Wireless and Mobility
08-31-2019
07:00 PM
08-31-2019
07:00 PM
Hi Rasika, It's 8.5.135. Today I took screenshot transferring few times to confirm it's consistent and it was. Also, I observer that couple of weeks ago and it has been like that since when I turned on AVC (I mean before I was using central switching because I did not need AVC so the moment I wanted to have AVC I changed switching to local). Can the AVC downgrade the performance?. It doesn't hurt that much when browsing internet but I am trying to get the maximum throughput for transferring the files on the LAN between PCs and file servers where I would expect local switching to beat central. Thank you
... View more
Created by
Mikolaj Moryto
in Wireless and Mobility
in Wireless and Mobility
08-31-2019
06:13 AM
08-31-2019
06:13 AM
Hi, I was wondering if anyone has seen it in their deployments. I have a simple network at home with 2702i AP being connected to the 3560G switch. ESXi server where I have vWLC (8.5.*) is connected to the same switch directly. What I observed is that I have slower network (throughput) when using FlexConnect local switching for my WLAN comparing to FlexConnect central switching. I would agree if that was opposite way. I have not run any intensive, detailed performance tests so I base that only on copying files from the file server VM which sits on the same ESXi server where vWLC is installed. I sit quite close to the AP and Tx rate is 1300 Mbps. The reason why I prefer local switching is because I wanted to use Flex AVC and local switching must be enabled for that. It is quite fast so I do not complain, just wonder if anyone experienced that before. Central switching: Local switching: Thanks, Mikolaj
... View more
Labels:
Created by
Mikolaj Moryto
in IP Telephony and Phones
in IP Telephony and Phones
08-01-2018
08:42 AM
08-01-2018
08:42 AM
Hi,
Depending on your design you can try these two options below on CUCM:
1. translation pattern with option “Route Next Hop By Calling Party Number”
2. calling party transformation masks for incoming calls (you can also modify calling number on the gateway to set it to specific pattern and then use calling party transformation mask on the CUCM for the specific pattern as it will not break up other calls)
Thank you,
Mikolaj
**** PLEASE RATE IF USEFUL ****
... View more
Created by
Mikolaj Moryto
in IP Telephony and Phones
in IP Telephony and Phones
07-25-2018
09:02 AM
07-25-2018
09:02 AM
You can modify or create new softkey template which will not have transfer button.
https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/10_0_1/ccmcfg/CUCM_BK_C95ABA82_00_admin-guide-100/CUCM_BK_C95ABA82_00_admin-guide-100_chapter_01001111.pdf
Thank you,
Mikolaj
**** PLEASE RATE IF USEFUL ****
... View more
Created by
Mikolaj Moryto
in IP Telephony and Phones
in IP Telephony and Phones
07-24-2018
06:25 AM
07-24-2018
06:25 AM
You are getting SIP/2.0 500 Server Internal Error from remote device. What is the device with IP 10.10.10.10? Do you have access to that?
Thank you,
Mikolaj
**** PLEASE RATE IF USEFUL ****
... View more
Created by
Mikolaj Moryto
in IP Telephony and Phones
in IP Telephony and Phones
07-24-2018
06:16 AM
07-24-2018
06:16 AM
Hi,
1) try to make an international call and then pull logs for relative time of last 10 minutes.
2) the problem is that when you, for instance, dial 0001234567890, your CUCM replaces the dialled number with +1234567890 before sending the call to the gateway. If your intention was to match incoming dial peer 1000, you are not matching that (I think you are matching 1001) and the translation profile on that dial peer is not applied to the called number. For that reason you are also not matching outgoing dial peer 110. I incorrectly said in the previous post that you are but looking deeper you are not.
Apply below change on the gateway if you have access and see what happens. After that it should match incoming dial peer, transform the number correctly and match outgoing dial peer.
dial-peer voice 1000 voip
incoming-called number +T
3) I need confirmation that you attached the correct gateway config because the IP address of the gateway in the config does not match the IP address CUCM sends call to. Maybe you are sending it to the incorrect device/IP and that is why there is no reply to INVITE.
... View more
Created by
Mikolaj Moryto
in IP Telephony and Phones
in IP Telephony and Phones
07-18-2018
07:29 PM
07-18-2018
07:29 PM
Can you share the configuration?
Thank you,
Mikolaj
**** PLEASE RATE IF USEFUL ****
... View more
09-10-2019
So that wasn't really an AP or WLC configuration issue. Below commands
were doing what they were sup...
09-09-2019
That command worked after using "debug capwap console cli" but it did
not solve the issue. I am stil...
09-09-2019
These two commands are not available now when the AP is registered to
vWLC. Does it need to be facto...
Created by
Mikolaj Moryto
in IP Telephony and Phones
09-08-2019
09-08-2019
Hi, Look at your debug closer. You do not receive any reply for the
service provider to your INVITE....
09-08-2019
Hi Sandeep,Does the AP need to be in specific mode for that? I have it
currently registered to vWLC ...
09-08-2019
Hi,Because of some vWLC limitations I decided to test 9800-CL (16.11.1c)
and after initial configura...
09-06-2019
Hi,Disabling AVC improves the through for another 20-30% but it's far
from reaching the value it get...
09-02-2019
Upgraded to 8.5.151.0 and it is the same. At this point I believe it is
the AP and its CPU not being...
08-31-2019
Hi Rasika,It's 8.5.135. Today I took screenshot transferring few times
to confirm it's consistent an...
Created by
Mikolaj Moryto
in Wireless and Mobility
08-31-2019
08-31-2019
Hi, I was wondering if anyone has seen it in their deployments. I have a
simple network at home with...
Created by
Mikolaj Moryto
in FirePOWER
12-14-2018
12-14-2018
So I understand you can use LDAP authentication with FDM but for FMC you
can use LDAP or RADIUS? Sti...
Created by
Mikolaj Moryto
in FirePOWER
12-13-2018
12-13-2018
Thank you for your comments. You're right about the remote VPN licensing
as I have just found follow...
Created by
Mikolaj Moryto
in FirePOWER
12-13-2018
12-13-2018
Hi, Have been trying to find a replacement for client's 5510. I found
5506-X and based on the data s...
Created by
Mikolaj Moryto
in TelePresence and Video Infrastructure
11-07-2018
11-07-2018
Thank you Jaime and Nick, I was using the install guide but apparently
missed the part about the SQL...
Created by
Mikolaj Moryto
in TelePresence and Video Infrastructure
11-07-2018
11-07-2018
Hi, Have been wondering if anyone here saw that before. I am trying to
install TMS 15.7.0 with exter...
Public Statistics
| Date Registered | 05-26-2014 03:16 AM |
| Date Last Visited | 09-11-2019 02:07 AM |
| Total Messages Posted | 64 |
| Total Helpful Votes Received | 65 |
Helpful Votes Given To
| User | Helpful Count |
|---|---|
| 10 | |
| 5 | |
| 15 | |
| 5 | |
| 5 |
.jpg "VIP Mentor"){kind=icon}
.jpg "Hall of Fame Cisco Employee"){kind=icon}
Helpful Votes From
| User | Helpful Count |
|---|---|
| 25 | |
| 5 | |
| 5 | |
| 5 | |
| 5 |
