topic Configuring UC-Proxy on ASA version 8.0 in Network Security

Configuring UC-Proxy on ASA version 8.0

guigonza — Mon, 11 Mar 2019 22:19:25 GMT

Hi ... I'm trying to configure UC-Proxy using an ASA 5505 with software version 8.0.4.

I was following the instructions in DOC-5704 and ASA 8.0 CLI.

I don't have USB security tokens in UC solution, instead I'm using IP phones Cisco 7961 with MIC.

I configure all the items as the documentation says but when I restart the phone outside the Firewall, the 7961 don't registrate with the Call Manager.

Checking the troubleshooting I found that it's possible certificates problems but I don't know if I need to do something in phones.

Any suggestion ?, I would like to know if there is any consideration when the UC proxy works just with MIC.

In file attached my configuration (some lines).

The outside phone is a Cisco 7961 configured with static IP address and TFTP address of Call Manager (static NAT in ASA).

Thanks in advance ...

Configuring UC-Proxy on ASA version 8.0

Julio Carvajal — Thu, 26 Jan 2012 00:15:31 GMT

Hello Guigonza,

How is the default gateway of the CUCM ( to go to the outside)??

Regards,

Julio

Configuring UC-Proxy on ASA version 8.0

guigonza — Thu, 26 Jan 2012 01:30:33 GMT

The default gateway of the CUCM is the firewall.

The firewall has configured the NAT and Global to make CUCM able to go outside.

Configuring UC-Proxy on ASA version 8.0

Julio Carvajal — Thu, 26 Jan 2012 06:00:32 GMT

Hello,

Can you do captures from the phone to the TFTP server in this case the CUCM I guess.

access-list capout permit udp host phone_ip host X.X.X.93 eq 69

access-list capout permit udp host X.X.X.93 eq 69 host phone_ip

access-list capin permit udp host phone_ip host 192.168.21.252 eq 69

access-list capin permit udp host 192.168.21.252 eq 69 host phone_ip

capture capin access-list capin interface inside

capture capout access-list capout interface outside tftp proxy

debug phone-proxy tftp

I forgot the last part of the capture on the outside its something with crypto ( Due to the phone proxy feature) will let you know tomorrow morning.

Rate helpful posts.

Julio

Configuring UC-Proxy on ASA version 8.0

guigonza — Thu, 26 Jan 2012 13:03:54 GMT

Thanks for help ...

I made a factory default reset in the outside IP Phone and now I can see the CTL file in the phone.

But the IP phone still tries to registering.

I made the captures and debugs:

Captures:

asa# sh capture capout

24 packets captured

1: 08:42:59.262132 802.1Q vlan#2 P0 190.167.215.94.49152 > 190.167.215.93.69: udp 31

2: 08:42:59.515522 802.1Q vlan#2 P0 190.167.215.94.49153 > 190.167.215.93.69: udp 36

3: 08:43:11.139290 802.1Q vlan#2 P0 190.167.215.94.49154 > 190.167.215.93.69: udp 31

4: 08:43:12.181188 802.1Q vlan#2 P0 190.167.215.94.49155 > 190.167.215.93.69: udp 34

5: 08:43:21.625028 802.1Q vlan#2 P0 190.167.215.94.49156 > 190.167.215.93.69: udp 30

6: 08:43:25.404565 802.1Q vlan#2 P0 190.167.215.94.49157 > 190.167.215.93.69: udp 31

7: 08:43:40.520648 802.1Q vlan#2 P0 190.167.215.94.49158 > 190.167.215.93.69: udp 30

8: 08:43:44.369762 802.1Q vlan#2 P0 190.167.215.94.49159 > 190.167.215.93.69: udp 34

9: 08:47:54.116937 802.1Q vlan#2 P0 190.167.215.94.49645 > 190.167.215.93.69: udp 31

10: 08:47:54.278580 802.1Q vlan#2 P0 190.167.215.94.50922 > 190.167.215.93.69: udp 31

11: 08:47:54.695459 802.1Q vlan#2 P0 190.167.215.94.52314 > 190.167.215.93.69: udp 36

12: 08:47:57.308501 802.1Q vlan#2 P0 190.167.215.94.51278 > 190.167.215.93.69: udp 26

13: 08:48:01.508015 802.1Q vlan#2 P0 190.167.215.94.51278 > 190.167.215.93.69: udp 26

14: 08:48:13.586746 802.1Q vlan#2 P2 190.167.215.94.50378 > 190.167.215.93.69: udp 46

15: 08:48:14.597777 802.1Q vlan#2 P2 190.167.215.94.50338 > 190.167.215.93.69: udp 39

16: 08:49:49.716836 802.1Q vlan#2 P2 190.167.215.94.52691 > 190.167.215.93.69: udp 31

17: 08:49:49.896529 802.1Q vlan#2 P2 190.167.215.94.52456 > 190.167.215.93.69: udp 31

18: 08:49:50.315352 802.1Q vlan#2 P2 190.167.215.94.52937 > 190.167.215.93.69: udp 36

19: 08:51:12.513019 802.1Q vlan#2 P2 190.167.215.94.49193 > 190.167.215.93.69: udp 31

20: 08:51:12.694025 802.1Q vlan#2 P2 190.167.215.94.52397 > 190.167.215.93.69: udp 31

21: 08:51:13.063320 802.1Q vlan#2 P2 190.167.215.94.50318 > 190.167.215.93.69: udp 36

22: 08:54:04.372340 802.1Q vlan#2 P2 190.167.215.94.50883 > 190.167.215.93.69: udp 31

23: 08:54:04.532794 802.1Q vlan#2 P2 190.167.215.94.49627 > 190.167.215.93.69: udp 31

24: 08:54:04.912382 802.1Q vlan#2 P2 190.167.215.94.50552 > 190.167.215.93.69: udp 36

24 packets shown

asa# sh capture capin

19 packets captured

1: 08:42:59.515934 802.1Q vlan#1 P0 190.167.215.94.49153 > 192.168.21.252.69: udp 32

2: 08:43:11.139732 802.1Q vlan#1 P0 190.167.215.94.49154 > 192.168.21.252.69: udp 31

3: 08:43:12.181600 802.1Q vlan#1 P0 190.167.215.94.49155 > 192.168.21.252.69: udp 34

4: 08:43:21.625410 802.1Q vlan#1 P0 190.167.215.94.49156 > 192.168.21.252.69: udp 30

5: 08:43:25.404993 802.1Q vlan#1 P0 190.167.215.94.49157 > 192.168.21.252.69: udp 31

6: 08:43:40.521060 802.1Q vlan#1 P0 190.167.215.94.49158 > 192.168.21.252.69: udp 30

7: 08:43:44.370128 802.1Q vlan#1 P0 190.167.215.94.49159 > 192.168.21.252.69: udp 34

8: 08:47:54.278992 802.1Q vlan#1 P0 190.167.215.94.50922 > 192.168.21.252.69: udp 31

9: 08:47:54.695841 802.1Q vlan#1 P0 190.167.215.94.52314 > 192.168.21.252.69: udp 32

10: 08:47:57.308943 802.1Q vlan#1 P0 190.167.215.94.51278 > 192.168.21.252.69: udp 22

11: 08:48:01.508213 802.1Q vlan#1 P0 190.167.215.94.51278 > 192.168.21.252.69: udp 22

12: 08:48:13.587158 802.1Q vlan#1 P0 190.167.215.94.50378 > 192.168.21.252.69: udp 42

13: 08:48:14.598189 802.1Q vlan#1 P0 190.167.215.94.50338 > 192.168.21.252.69: udp 35

14: 08:49:49.896941 802.1Q vlan#1 P0 190.167.215.94.52456 > 192.168.21.252.69: udp 31

15: 08:49:50.315779 802.1Q vlan#1 P0 190.167.215.94.52937 > 192.168.21.252.69: udp 32

16: 08:51:12.694467 802.1Q vlan#1 P0 190.167.215.94.52397 > 192.168.21.252.69: udp 31

17: 08:51:13.063732 802.1Q vlan#1 P0 190.167.215.94.50318 > 192.168.21.252.69: udp 32

18: 08:54:04.533221 802.1Q vlan#1 P0 190.167.215.94.49627 > 192.168.21.252.69: udp 31

19: 08:54:04.912840 802.1Q vlan#1 P0 190.167.215.94.50552 > 192.168.21.252.69: udp 32

19 packets shown

PP: Received Data Block 15 from inside:CUCM85/58440 to outside:190.167.215.94/50 318

Received Block 15

PP: Acked Block #15 from 190.167.215.94/50318 to CUCM85/58440

Obtained process_node addr CUCM85

PP: Added ACL for 190.167.215.94 to outside:190.167.215.93/27467

PP: Added ACL for 190.167.215.94 to outside:190.167.215.93/35088

PP: Modifying to encrypted mode.

PP: Modifying to TLS as the transport layer protocol.

PP: Data Block 1 forwarded from 190.167.215.93/29073 to 190.167.215.94/50318

PP: Received ACK Block 1 from outside:190.167.215.94/50318 to inside:CUCM85

PP: Data Block 2 forwarded to 190.167.215.94/50318

PP: Received ACK Block 2 from outside:190.167.215.94/50318 to inside:CUCM85

PP: Data Block 3 forwarded to 190.167.215.94/50318

PP: Received ACK Block 3 from outside:190.167.215.94/50318 to inside:CUCM85

PP: Data Block 4 forwarded to 190.167.215.94/50318

PP: Received ACK Block 4 from outside:190.167.215.94/50318 to inside:CUCM85

PP: Data Block 5 forwarded to 190.167.215.94/50318

PP: Received ACK Block 5 from outside:190.167.215.94/50318 to inside:CUCM85

PP: Data Block 6 forwarded to 190.167.215.94/50318

PP: Received ACK Block 6 from outside:190.167.215.94/50318 to inside:CUCM85

PP: Data Block 7 forwarded to 190.167.215.94/50318

PP: Received ACK Block 7 from outside:190.167.215.94/50318 to inside:CUCM85

PP: Data Block 8 forwarded to 190.167.215.94/50318

PP: Received ACK Block 8 from outside:190.167.215.94/50318 to inside:CUCM85

PP: Data Block 9 forwarded to 190.167.215.94/50318

PP: Received ACK Block 9 from outside:190.167.215.94/50318 to inside:CUCM85

PP: Data Block 10 forwarded to 190.167.215.94/50318

PP: Received ACK Block 10 from outside:190.167.215.94/50318 to inside:CUCM85

PP: Data Block 11 forwarded to 190.167.215.94/50318

PP: Received ACK Block 11 from outside:190.167.215.94/50318 to inside:CUCM85

PP: Data Block 12 forwarded to 190.167.215.94/50318

PP: Received ACK Block 12 from outside:190.167.215.94/50318 to inside:CUCM85

PP: Data Block 13 forwarded to 190.167.215.94/50318

PP: Received ACK Block 13 from outside:190.167.215.94/50318 to inside:CUCM85

PP: Data Block 14 forwarded to 190.167.215.94/50318

PP: Received ACK Block 14 from outside:190.167.215.94/50318 to inside:CUCM85

PP: Data Block 15 forwarded to 190.167.215.94/50318

PP: Received ACK Block 15 from outside:190.167.215.94/50318 to inside:CUCM85

PP: TFTP session complete, all data sent

PP: Received Data Block 15 from inside:CUCM85/58440 to outside:190.167.215.94/50 318

Error: block # is 15, expecting 1

PP: Received Data Block 15 from inside:CUCM85/58440 to outside:190.167.215.94/50 318

Error: block # is 15, expecting 1

PP: Received Data Block 15 from inside:CUCM85/58440 to outside:190.167.215.94/50 318

Error: block # is 15, expecting 1

PP: Received Data Block 15 from inside:CUCM85/58440 to outside:190.167.215.94/50 318

Error: block # is 15, expecting 1

PP: Received Data Block 15 from inside:CUCM85/58440 to outside:190.167.215.94/50 318

Error: block # is 15, expecting 1

PP: Received Data Block 15 from inside:CUCM85/58440 to outside:190.167.215.94/50 318

Error: block # is 15, expecting 1

PP: 190.167.215.94/50883 requesting CTLSEP002497A89AD5.tlv

PP: opened 0x5139e026

PP: Data Block 1 forwarded from 190.167.215.93/62898 to 190.167.215.94/50883 ing ress ifc outside

PP: Received ACK Block 1 from outside:190.167.215.94/50883 to inside:CUCM85

PP: Data Block 2 forwarded to 190.167.215.94/50883

PP: Received ACK Block 2 from outside:190.167.215.94/50883 to inside:CUCM85

PP: Data Block 3 forwarded to 190.167.215.94/50883

PP: Received ACK Block 3 from outside:190.167.215.94/50883 to inside:CUCM85

PP: Data Block 4 forwarded to 190.167.215.94/50883

PP: Received ACK Block 4 from outside:190.167.215.94/50883 to inside:CUCM85

PP: Data Block 5 forwarded to 190.167.215.94/50883

PP: Received ACK Block 5 from outside:190.167.215.94/50883 to inside:CUCM85

PP: Data Block 6 forwarded to 190.167.215.94/50883

PP: Received ACK Block 6 from outside:190.167.215.94/50883 to inside:CUCM85

PP: Data Block 7 forwarded to 190.167.215.94/50883

PP: Received ACK Block 7 from outside:190.167.215.94/50883 to inside:CUCM85

PP: Data Block 8 forwarded to 190.167.215.94/50883

PP: Received ACK Block 8 from outside:190.167.215.94/50883 to inside:CUCM85

PP: Data Block 9 forwarded to 190.167.215.94/50883

PP: Received ACK Block 9 from outside:190.167.215.94/50883 to inside:CUCM85

PP: Data Block 10 forwarded to 190.167.215.94/50883

PP: Received ACK Block 10 from outside:190.167.215.94/50883 to inside:CUCM85

PP: TFTP session complete, all data sent

PP: 190.167.215.94/49627 requesting ITLSEP002497A89AD5.tlv

PP: opened 0x74942062

PP: 190.167.215.94/50552 requesting SEP002497A89AD5.cnf.xml.sgn

PP: opened 0x5fbcfbb2

PP: Received Data Block 1 from inside:CUCM85/41789 to outside:190.167.215.94/505 52

Received Block 1

PP: Acked Block #1 from 190.167.215.94/50552 to CUCM85/41789

PP: Received Data Block 2 from inside:CUCM85/41789 to outside:190.167.215.94/505 52

Received Block 2

PP: Acked Block #2 from 190.167.215.94/50552 to CUCM85/41789

PP: Received Data Block 3 from inside:CUCM85/41789 to outside:190.167.215.94/505 52

Received Block 3

PP: Acked Block #3 from 190.167.215.94/50552 to CUCM85/41789

PP: Received Data Block 4 from inside:CUCM85/41789 to outside:190.167.215.94/505 52

Received Block 4

PP: Acked Block #4 from 190.167.215.94/50552 to CUCM85/41789

PP: Received Data Block 5 from inside:CUCM85/41789 to outside:190.167.215.94/505 52

Received Block 5

PP: Acked Block #5 from 190.167.215.94/50552 to CUCM85/41789

PP: Received Data Block 6 from inside:CUCM85/41789 to outside:190.167.215.94/505 52

Received Block 6

PP: Acked Block #6 from 190.167.215.94/50552 to CUCM85/41789

PP: Received Data Block 7 from inside:CUCM85/41789 to outside:190.167.215.94/505 52

Received Block 7

PP: Acked Block #7 from 190.167.215.94/50552 to CUCM85/41789

PP: Received Data Block 8 from inside:CUCM85/41789 to outside:190.167.215.94/505 52

Received Block 8

PP: Acked Block #8 from 190.167.215.94/50552 to CUCM85/41789

PP: Received Data Block 9 from inside:CUCM85/41789 to outside:190.167.215.94/505 52

Received Block 9

PP: Acked Block #9 from 190.167.215.94/50552 to CUCM85/41789

PP: Received Data Block 10 from inside:CUCM85/41789 to outside:190.167.215.94/50 552

Received Block 10

PP: Acked Block #10 from 190.167.215.94/50552 to CUCM85/41789

PP: Received Data Block 11 from inside:CUCM85/41789 to outside:190.167.215.94/50 552

Received Block 11

PP: Acked Block #11 from 190.167.215.94/50552 to CUCM85/41789

PP: Received Data Block 12 from inside:CUCM85/41789 to outside:190.167.215.94/50 552

Received Block 12

PP: Acked Block #12 from 190.167.215.94/50552 to CUCM85/41789

PP: Received Data Block 13 from inside:CUCM85/41789 to outside:190.167.215.94/50 552

Received Block 13

PP: Acked Block #13 from 190.167.215.94/50552 to CUCM85/41789

PP: Received Data Block 14 from inside:CUCM85/41789 to outside:190.167.215.94/50 552

Received Block 14

PP: Acked Block #14 from 190.167.215.94/50552 to CUCM85/41789

PP: Received Data Block 15 from inside:CUCM85/41789 to outside:190.167.215.94/50 552

Received Block 15

PP: Acked Block #15 from 190.167.215.94/50552 to CUCM85/41789

Obtained process_node addr CUCM85

PP: Added ACL for 190.167.215.94 to outside:190.167.215.93/13374

PP: Added ACL for 190.167.215.94 to outside:190.167.215.93/47824

PP: Modifying to encrypted mode.

PP: Modifying to TLS as the transport layer protocol.

PP: Data Block 1 forwarded from 190.167.215.93/42303 to 190.167.215.94/50552

PP: Received ACK Block 1 from outside:190.167.215.94/50552 to inside:CUCM85

PP: Data Block 2 forwarded to 190.167.215.94/50552

PP: Received ACK Block 2 from outside:190.167.215.94/50552 to inside:CUCM85

PP: Data Block 3 forwarded to 190.167.215.94/50552

PP: Received ACK Block 3 from outside:190.167.215.94/50552 to inside:CUCM85

PP: Data Block 4 forwarded to 190.167.215.94/50552

PP: Received ACK Block 4 from outside:190.167.215.94/50552 to inside:CUCM85

PP: Data Block 5 forwarded to 190.167.215.94/50552

PP: Received ACK Block 5 from outside:190.167.215.94/50552 to inside:CUCM85

PP: Data Block 6 forwarded to 190.167.215.94/50552

PP: Received ACK Block 6 from outside:190.167.215.94/50552 to inside:CUCM85

PP: Data Block 7 forwarded to 190.167.215.94/50552

PP: Received ACK Block 7 from outside:190.167.215.94/50552 to inside:CUCM85

PP: Data Block 8 forwarded to 190.167.215.94/50552

PP: Received ACK Block 8 from outside:190.167.215.94/50552 to inside:CUCM85

PP: Data Block 9 forwarded to 190.167.215.94/50552

PP: Received ACK Block 9 from outside:190.167.215.94/50552 to inside:CUCM85

PP: Data Block 10 forwarded to 190.167.215.94/50552

PP: Received ACK Block 10 from outside:190.167.215.94/50552 to inside:CUCM85

PP: Data Block 11 forwarded to 190.167.215.94/50552

PP: Received ACK Block 11 from outside:190.167.215.94/50552 to inside:CUCM85

PP: Data Block 12 forwarded to 190.167.215.94/50552

PP: Received ACK Block 12 from outside:190.167.215.94/50552 to inside:CUCM85

PP: Data Block 13 forwarded to 190.167.215.94/50552

PP: Received ACK Block 13 from outside:190.167.215.94/50552 to inside:CUCM85

PP: Data Block 14 forwarded to 190.167.215.94/50552

PP: Received ACK Block 14 from outside:190.167.215.94/50552 to inside:CUCM85

PP: Data Block 15 forwarded to 190.167.215.94/50552

PP: Received ACK Block 15 from outside:190.167.215.94/50552 to inside:CUCM85

PP: TFTP session complete, all data sent

PP: Received Data Block 15 from inside:CUCM85/41789 to outside:190.167.215.94/50 552

Error: block # is 15, expecting 1

PP: Received Data Block 15 from inside:CUCM85/41789 to outside:190.167.215.94/50 552

Error: block # is 15, expecting 1

PP: Received Data Block 15 from inside:CUCM85/41789 to outside:190.167.215.94/50 552

Error: block # is 15, expecting 1

PP: Received Data Block 15 from inside:CUCM85/41789 to outside:190.167.215.94/50 552

Error: block # is 15, expecting 1

PP: Received Data Block 15 from inside:CUCM85/41789 to outside:190.167.215.94/50 552

Error: block # is 15, expecting 1

PP: Received Data Block 15 from inside:CUCM85/41789 to outside:190.167.215.94/50 552

Error: block # is 15, expecting 1

asa# sh capture capin
19 packets captured
   1: 08:42:59.515934 802.1Q vlan#1 P0 190.167.215.94.49153 > 192.168.21.252.69: udp 32
   2: 08:43:11.139732 802.1Q vlan#1 P0 190.167.215.94.49154 > 192.168.21.252.69: udp 31
   3: 08:43:12.181600 802.1Q vlan#1 P0 190.167.215.94.49155 > 192.168.21.252.69: udp 34
   4: 08:43:21.625410 802.1Q vlan#1 P0 190.167.215.94.49156 > 192.168.21.252.69: udp 30
   5: 08:43:25.404993 802.1Q vlan#1 P0 190.167.215.94.49157 > 192.168.21.252.69: udp 31
   6: 08:43:40.521060 802.1Q vlan#1 P0 190.167.215.94.49158 > 192.168.21.252.69: udp 30
   7: 08:43:44.370128 802.1Q vlan#1 P0 190.167.215.94.49159 > 192.168.21.252.69: udp 34
   8: 08:47:54.278992 802.1Q vlan#1 P0 190.167.215.94.50922 > 192.168.21.252.69: udp 31
   9: 08:47:54.695841 802.1Q vlan#1 P0 190.167.215.94.52314 > 192.168.21.252.69: udp 32
10: 08:47:57.308943 802.1Q vlan#1 P0 190.167.215.94.51278 > 192.168.21.252.69: udp 22
11: 08:48:01.508213 802.1Q vlan#1 P0 190.167.215.94.51278 > 192.168.21.252.69: udp 22
12: 08:48:13.587158 802.1Q vlan#1 P0 190.167.215.94.50378 > 192.168.21.252.69: udp 42
13: 08:48:14.598189 802.1Q vlan#1 P0 190.167.215.94.50338 > 192.168.21.252.69: udp 35
14: 08:49:49.896941 802.1Q vlan#1 P0 190.167.215.94.52456 > 192.168.21.252.69: udp 31
15: 08:49:50.315779 802.1Q vlan#1 P0 190.167.215.94.52937 > 192.168.21.252.69: udp 32
16: 08:51:12.694467 802.1Q vlan#1 P0 190.167.215.94.52397 > 192.168.21.252.69: udp 31
17: 08:51:13.063732 802.1Q vlan#1 P0 190.167.215.94.50318 > 192.168.21.252.69: udp 32
18: 08:54:04.533221 802.1Q vlan#1 P0 190.167.215.94.49627 > 192.168.21.252.69: udp 31
19: 08:54:04.912840 802.1Q vlan#1 P0 190.167.215.94.50552 > 192.168.21.252.69: udp 32
19 packets shown

Debugs:

PP: Received Data Block 15 from inside:CUCM85/58440 to outside:190.167.215.94/50 318

Received Block 15

PP: Acked Block #15 from 190.167.215.94/50318 to CUCM85/58440

Obtained process_node addr CUCM85

PP: Added ACL for 190.167.215.94 to outside:190.167.215.93/27467

PP: Added ACL for 190.167.215.94 to outside:190.167.215.93/35088

PP: Modifying to encrypted mode.

PP: Modifying to TLS as the transport layer protocol.

PP: Data Block 1 forwarded from 190.167.215.93/29073 to 190.167.215.94/50318

PP: Received ACK Block 1 from outside:190.167.215.94/50318 to inside:CUCM85

PP: Data Block 2 forwarded to 190.167.215.94/50318

PP: Received ACK Block 2 from outside:190.167.215.94/50318 to inside:CUCM85

PP: Data Block 3 forwarded to 190.167.215.94/50318

PP: Received ACK Block 3 from outside:190.167.215.94/50318 to inside:CUCM85

PP: Data Block 4 forwarded to 190.167.215.94/50318

PP: Received ACK Block 4 from outside:190.167.215.94/50318 to inside:CUCM85

PP: Data Block 5 forwarded to 190.167.215.94/50318

PP: Received ACK Block 5 from outside:190.167.215.94/50318 to inside:CUCM85

PP: Data Block 6 forwarded to 190.167.215.94/50318

PP: Received ACK Block 6 from outside:190.167.215.94/50318 to inside:CUCM85

PP: Data Block 7 forwarded to 190.167.215.94/50318

PP: Received ACK Block 7 from outside:190.167.215.94/50318 to inside:CUCM85

PP: Data Block 8 forwarded to 190.167.215.94/50318

PP: Received ACK Block 8 from outside:190.167.215.94/50318 to inside:CUCM85

PP: Data Block 9 forwarded to 190.167.215.94/50318

PP: Received ACK Block 9 from outside:190.167.215.94/50318 to inside:CUCM85

PP: Data Block 10 forwarded to 190.167.215.94/50318

PP: Received ACK Block 10 from outside:190.167.215.94/50318 to inside:CUCM85

PP: Data Block 11 forwarded to 190.167.215.94/50318

PP: Received ACK Block 11 from outside:190.167.215.94/50318 to inside:CUCM85

PP: Data Block 12 forwarded to 190.167.215.94/50318

PP: Received ACK Block 12 from outside:190.167.215.94/50318 to inside:CUCM85

PP: Data Block 13 forwarded to 190.167.215.94/50318

PP: Received ACK Block 13 from outside:190.167.215.94/50318 to inside:CUCM85

PP: Data Block 14 forwarded to 190.167.215.94/50318

PP: Received ACK Block 14 from outside:190.167.215.94/50318 to inside:CUCM85

PP: Data Block 15 forwarded to 190.167.215.94/50318

PP: Received ACK Block 15 from outside:190.167.215.94/50318 to inside:CUCM85

PP: TFTP session complete, all data sent

PP: Received Data Block 15 from inside:CUCM85/58440 to outside:190.167.215.94/50 318

Error: block # is 15, expecting 1

PP: Received Data Block 15 from inside:CUCM85/58440 to outside:190.167.215.94/50 318

Error: block # is 15, expecting 1

PP: Received Data Block 15 from inside:CUCM85/58440 to outside:190.167.215.94/50 318

Error: block # is 15, expecting 1

PP: Received Data Block 15 from inside:CUCM85/58440 to outside:190.167.215.94/50 318

Error: block # is 15, expecting 1

PP: Received Data Block 15 from inside:CUCM85/58440 to outside:190.167.215.94/50 318

Error: block # is 15, expecting 1

PP: Received Data Block 15 from inside:CUCM85/58440 to outside:190.167.215.94/50 318

Error: block # is 15, expecting 1

PP: 190.167.215.94/50883 requesting CTLSEP002497A89AD5.tlv

PP: opened 0x5139e026

PP: Data Block 1 forwarded from 190.167.215.93/62898 to 190.167.215.94/50883 ing ress ifc outside

PP: Received ACK Block 1 from outside:190.167.215.94/50883 to inside:CUCM85

PP: Data Block 2 forwarded to 190.167.215.94/50883

PP: Received ACK Block 2 from outside:190.167.215.94/50883 to inside:CUCM85

PP: Data Block 3 forwarded to 190.167.215.94/50883

PP: Received ACK Block 3 from outside:190.167.215.94/50883 to inside:CUCM85

PP: Data Block 4 forwarded to 190.167.215.94/50883

PP: Received ACK Block 4 from outside:190.167.215.94/50883 to inside:CUCM85

PP: Data Block 5 forwarded to 190.167.215.94/50883

PP: Received ACK Block 5 from outside:190.167.215.94/50883 to inside:CUCM85

PP: Data Block 6 forwarded to 190.167.215.94/50883

PP: Received ACK Block 6 from outside:190.167.215.94/50883 to inside:CUCM85

PP: Data Block 7 forwarded to 190.167.215.94/50883

PP: Received ACK Block 7 from outside:190.167.215.94/50883 to inside:CUCM85

PP: Data Block 8 forwarded to 190.167.215.94/50883

PP: Received ACK Block 8 from outside:190.167.215.94/50883 to inside:CUCM85

PP: Data Block 9 forwarded to 190.167.215.94/50883

PP: Received ACK Block 9 from outside:190.167.215.94/50883 to inside:CUCM85

PP: Data Block 10 forwarded to 190.167.215.94/50883

PP: Received ACK Block 10 from outside:190.167.215.94/50883 to inside:CUCM85

PP: TFTP session complete, all data sent

PP: 190.167.215.94/49627 requesting ITLSEP002497A89AD5.tlv

PP: opened 0x74942062

PP: 190.167.215.94/50552 requesting SEP002497A89AD5.cnf.xml.sgn

PP: opened 0x5fbcfbb2

PP: Received Data Block 1 from inside:CUCM85/41789 to outside:190.167.215.94/505 52

Received Block 1

PP: Acked Block #1 from 190.167.215.94/50552 to CUCM85/41789

PP: Received Data Block 2 from inside:CUCM85/41789 to outside:190.167.215.94/505 52

Received Block 2

PP: Acked Block #2 from 190.167.215.94/50552 to CUCM85/41789

PP: Received Data Block 3 from inside:CUCM85/41789 to outside:190.167.215.94/505 52

Received Block 3

PP: Acked Block #3 from 190.167.215.94/50552 to CUCM85/41789

PP: Received Data Block 4 from inside:CUCM85/41789 to outside:190.167.215.94/505 52

Received Block 4

PP: Acked Block #4 from 190.167.215.94/50552 to CUCM85/41789

PP: Received Data Block 5 from inside:CUCM85/41789 to outside:190.167.215.94/505 52

Received Block 5

PP: Acked Block #5 from 190.167.215.94/50552 to CUCM85/41789

PP: Received Data Block 6 from inside:CUCM85/41789 to outside:190.167.215.94/505 52

Received Block 6

PP: Acked Block #6 from 190.167.215.94/50552 to CUCM85/41789

PP: Received Data Block 7 from inside:CUCM85/41789 to outside:190.167.215.94/505 52

Received Block 7

PP: Acked Block #7 from 190.167.215.94/50552 to CUCM85/41789

PP: Received Data Block 8 from inside:CUCM85/41789 to outside:190.167.215.94/505 52

Received Block 8

PP: Acked Block #8 from 190.167.215.94/50552 to CUCM85/41789

PP: Received Data Block 9 from inside:CUCM85/41789 to outside:190.167.215.94/505 52

Received Block 9

PP: Acked Block #9 from 190.167.215.94/50552 to CUCM85/41789

PP: Received Data Block 10 from inside:CUCM85/41789 to outside:190.167.215.94/50 552

Received Block 10

PP: Acked Block #10 from 190.167.215.94/50552 to CUCM85/41789

PP: Received Data Block 11 from inside:CUCM85/41789 to outside:190.167.215.94/50 552

Received Block 11

PP: Acked Block #11 from 190.167.215.94/50552 to CUCM85/41789

PP: Received Data Block 12 from inside:CUCM85/41789 to outside:190.167.215.94/50 552

Received Block 12

PP: Acked Block #12 from 190.167.215.94/50552 to CUCM85/41789

PP: Received Data Block 13 from inside:CUCM85/41789 to outside:190.167.215.94/50 552

Received Block 13

PP: Acked Block #13 from 190.167.215.94/50552 to CUCM85/41789

PP: Received Data Block 14 from inside:CUCM85/41789 to outside:190.167.215.94/50 552

Received Block 14

PP: Acked Block #14 from 190.167.215.94/50552 to CUCM85/41789

PP: Received Data Block 15 from inside:CUCM85/41789 to outside:190.167.215.94/50 552

Received Block 15

PP: Acked Block #15 from 190.167.215.94/50552 to CUCM85/41789

Obtained process_node addr CUCM85

PP: Added ACL for 190.167.215.94 to outside:190.167.215.93/13374

PP: Added ACL for 190.167.215.94 to outside:190.167.215.93/47824

PP: Modifying to encrypted mode.

PP: Modifying to TLS as the transport layer protocol.

PP: Data Block 1 forwarded from 190.167.215.93/42303 to 190.167.215.94/50552

PP: Received ACK Block 1 from outside:190.167.215.94/50552 to inside:CUCM85

PP: Data Block 2 forwarded to 190.167.215.94/50552

PP: Received ACK Block 2 from outside:190.167.215.94/50552 to inside:CUCM85

PP: Data Block 3 forwarded to 190.167.215.94/50552

PP: Received ACK Block 3 from outside:190.167.215.94/50552 to inside:CUCM85

PP: Data Block 4 forwarded to 190.167.215.94/50552

PP: Received ACK Block 4 from outside:190.167.215.94/50552 to inside:CUCM85

PP: Data Block 5 forwarded to 190.167.215.94/50552

PP: Received ACK Block 5 from outside:190.167.215.94/50552 to inside:CUCM85

PP: Data Block 6 forwarded to 190.167.215.94/50552

PP: Received ACK Block 6 from outside:190.167.215.94/50552 to inside:CUCM85

PP: Data Block 7 forwarded to 190.167.215.94/50552

PP: Received ACK Block 7 from outside:190.167.215.94/50552 to inside:CUCM85

PP: Data Block 8 forwarded to 190.167.215.94/50552

PP: Received ACK Block 8 from outside:190.167.215.94/50552 to inside:CUCM85

PP: Data Block 9 forwarded to 190.167.215.94/50552

PP: Received ACK Block 9 from outside:190.167.215.94/50552 to inside:CUCM85

PP: Data Block 10 forwarded to 190.167.215.94/50552

PP: Received ACK Block 10 from outside:190.167.215.94/50552 to inside:CUCM85

PP: Data Block 11 forwarded to 190.167.215.94/50552

PP: Received ACK Block 11 from outside:190.167.215.94/50552 to inside:CUCM85

PP: Data Block 12 forwarded to 190.167.215.94/50552

PP: Received ACK Block 12 from outside:190.167.215.94/50552 to inside:CUCM85

PP: Data Block 13 forwarded to 190.167.215.94/50552

PP: Received ACK Block 13 from outside:190.167.215.94/50552 to inside:CUCM85

PP: Data Block 14 forwarded to 190.167.215.94/50552

PP: Received ACK Block 14 from outside:190.167.215.94/50552 to inside:CUCM85

PP: Data Block 15 forwarded to 190.167.215.94/50552

PP: Received ACK Block 15 from outside:190.167.215.94/50552 to inside:CUCM85

PP: TFTP session complete, all data sent

PP: Received Data Block 15 from inside:CUCM85/41789 to outside:190.167.215.94/50 552

Error: block # is 15, expecting 1

PP: Received Data Block 15 from inside:CUCM85/41789 to outside:190.167.215.94/50 552

Error: block # is 15, expecting 1

PP: Received Data Block 15 from inside:CUCM85/41789 to outside:190.167.215.94/50 552

Error: block # is 15, expecting 1

PP: Received Data Block 15 from inside:CUCM85/41789 to outside:190.167.215.94/50 552

Error: block # is 15, expecting 1

PP: Received Data Block 15 from inside:CUCM85/41789 to outside:190.167.215.94/50 552

Error: block # is 15, expecting 1

PP: Received Data Block 15 from inside:CUCM85/41789 to outside:190.167.215.94/50 552

Error: block # is 15, expecting 1

Configuring UC-Proxy on ASA version 8.0

Julio Carvajal — Thu, 26 Jan 2012 17:14:55 GMT

Hello,

On the captures we are not seeing the TFTP server responding to the phone, that seems to be the issue,

Regards,

Julio

Configuring UC-Proxy on ASA version 8.0

guigonza — Thu, 23 Feb 2012 16:22:48 GMT

Finally ... The problem was related to DNS configuration in ASA and CM server.

We configure the CM by IP address and this fix the situation.

Thanks for Help ...