Buy or Renew
Buy or Renew
Cisco + Splunk: It’s a new day for your data. Learn more.
 
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
4331
Views
0
Helpful
16
Replies

3rd party SIP phone loses traffic after INVITE

Teo7810TSG6
Level 1
Level 1

‎03-04-2016 08:09 AM - edited ‎06-04-2019 02:22 AM

Hi!  We are having a problem with our phones initiating a call.  They register with no problem, but when I try to make a call from them, the Cisco server ceases traffic.  It doesn't close the TCP connection, it just ceases traffic.

I noticed in the server settings that the phone is reported as not being "trusted."  Is there a setting to change to mark the phone as trusted?

Cisco server: 10.10.20.1

Teo SIP phone: 192.168.100.4

37 16.823472       192.168.100.4 10.10.20.1      SIP 685     Request: REGISTER sip:10.10.20.1:5060;transport=tcp (1 binding) |

40 17.004746 10.10.20.1      192.168.100.4 SIP     368     Status: 100 Trying |

42 17.005352       10.10.20.1 192.168.100.4   SIP 490     Status: 401 Unauthorized |

44 17.026869       192.168.100.4 10.10.20.1      SIP 887     Request: REGISTER sip:10.10.20.1:5060;transport=tcp (1 binding) |

48 17.250811 10.10.20.1      192.168.100.4 SIP     368     Status: 100 Trying |

49 17.252388 10.10.20.1      192.168.100.4 SIP     506     Status: 200 OK  (1 binding) |

50 17.253516 10.10.20.1      192.168.100.4 SIP     594     Request: NOTIFY sip:1090@192.168.100.4:5060;transport=tcp |

52 17.353075       192.168.100.4 10.10.20.1      SIP 694     Status: 200 OK |

198 83.101543       192.168.100.4 10.10.20.1      SIP/SDP 1221 Request: INVITE sip:1094@10.10.20.1:5060;user=phone |

202 83.287388 10.10.20.1      192.168.100.4 SIP     392     Status: 100 Trying |

203 83.287671 10.10.20.1      192.168.100.4 SIP     539     Status: 401 Unauthorized |

205 83.303909       192.168.100.4 10.10.20.1      SIP 396     Request: ACK sip:1094@10.10.20.1:5060;user=phone |

206 83.315357       192.168.100.4 10.10.20.1      SIP/SDP 1425 Request: INVITE sip:1094@10.10.20.1:5060;user=phone |

Labels:
0 Helpful
16 Replies 16

jokearns1
Cisco Employee
Cisco Employee

‎03-04-2016 08:15 AM

Hi Chuck,

Can you outline your call flow? what endpoint are you trying to call? How many SIP phones do you connected to the router on your side?

Also, can you connect a PC to the router and browse to the CUCM? make sure you can login and see the GUI. I just want to make sure you don't have an MTU issue on your VPN tunnel.

Regards,

Joe

0 Helpful

Teo7810TSG6
Level 1
Level 1
In response to jokearns1

‎03-04-2016 08:25 AM

Our configuration has three Cisco phones, and four Teo phones.  The Teo phones can register to 10.10.20.1.  The Cisco 7965 can register, and make calls to the Teo phones.  The Teo phones receive calls with no problems, and voice traffic sounds fine.

I can browse the CUCM through the router.  That's how I set up the phones.

0 Helpful

jokearns1
Cisco Employee
Cisco Employee
In response to Teo7810TSG6

‎03-04-2016 08:30 AM

Chuck,

I see your phones have media termination point checked? is this correct?

Joe

0 Helpful

Teo7810TSG6
Level 1
Level 1
In response to jokearns1

‎03-04-2016 08:35 AM

Yes, media termination point is checked.

0 Helpful

jokearns1
Cisco Employee
Cisco Employee
In response to jokearns1

‎03-04-2016 08:40 AM

Can you verify that the other no registered cisco phones are getting an IP address from the router? is the TFTP set to 10.10.20.1?

0 Helpful

dstaudt
Cisco Employee
Cisco Employee
In response to Teo7810TSG6

‎03-04-2016 08:32 AM

My suspicion would be that at some point in the call, CUCM starts attempting to send SIP signaling to the phone's 192.168.x.x address, and this isn't making it back to the phone.  Are both Cisco and Teo phones registering with 192.168.x.x addresses?

As it looks like there is a NAT in the scenario somewhere, maybe either the Cisco phones are doing something slightly different in the SIP messaging for it to work, or perhaps the VPN router is fixing up SIP signaling for the Cisco phones via packet inspection...?

0 Helpful

Teo7810TSG6
Level 1
Level 1
In response to dstaudt

‎03-04-2016 08:41 AM

The Cisco phones are configured to use SCCP.  The Teo phones will respond to a call made from the Cisco 7965 phone.  The 7960 and 7975 phones can contact 10.10.20.1, but seem to have a problem with the provisioning.

0 Helpful

jokearns1
Cisco Employee
Cisco Employee
In response to Teo7810TSG6

‎03-04-2016 09:03 AM

I don't see the other cisco phones getting an IP address displayed on the CUCM interface. Perhaps you can reset the settings on those phones and reboot them.

Joe

0 Helpful

Teo7810TSG6
Level 1
Level 1
In response to jokearns1

‎03-04-2016 03:45 PM

I think that the issue with the Teo phones is the server designates the 3rd-party SIP device as, "Device is not trusted."  I configured the 7960 manually for SIP, and it can make and receive SIP calls.  The Teo phones can receive calls, but can't make them.

What is the server setting to mark the device as trusted?

0 Helpful

Teo7810TSG6
Level 1
Level 1
In response to jokearns1

‎03-07-2016 01:57 PM

The following is a trace from a call between a Cisco 7960 and a Teo phone.

Server: 10.10.20.1

Cisco 7960, caller: 192.168.100.9

Teo, receiver: 192.168.100.4

  1   0.000000   192.168.100.4 -> 10.10.20.1   SIP     887   Request: REGISTER sip:10.10.20.1:5060;transport=tcp  (1 binding) | 
  2   0.224263   10.10.20.1 -> 192.168.100.4   SIP     368   Status: 100 Trying | 
  3   0.226091   10.10.20.1 -> 192.168.100.4   SIP     505   Status: 200 OK  (1 binding) | 
  4  10.203288   192.168.100.9 -> 10.10.20.1   SIP/SDP 824   Request: INVITE sip:1090@10.10.20.1 | 
  5  10.387322   10.10.20.1 -> 192.168.100.9   SIP     383   Status: 100 Trying | 
  6  10.409053   10.10.20.1 -> 192.168.100.4   SIP/SDP 1114  Request: INVITE sip:1090@192.168.100.4:5060;transport=tcp | 
  7  10.421123   192.168.100.4 -> 10.10.20.1   SIP     410   Status: 100 Trying | 
  8  10.446648   192.168.100.4 -> 10.10.20.1   SIP     769   Status: 180 Ringing | 
  9  10.647761   10.10.20.1 -> 192.168.100.9   SIP     708   Status: 180 Ringing | 
 10  11.785233   192.168.100.4 -> 10.10.20.1   SIP/SDP 1085  Status: 200 OK | 
 11  11.971925   10.10.20.1 -> 192.168.100.4   SIP     512   Request: ACK sip:1090@192.168.100.4:5060;transport=tcp;transport=tcp | 
 12  11.988737   10.10.20.1 -> 192.168.100.9   SIP/SDP 989   Status: 200 OK | 
 13  12.253308   192.168.100.9 -> 10.10.20.1   SIP     413   Request: ACK sip:1090@10.10.20.1:5060 | 
 14  14.920416   192.168.100.4 -> 10.10.20.1   SIP     657   Request: BYE sip:1010@10.10.20.1:5060;transport=tcp | 
 15  15.145007   10.10.20.1 -> 192.168.100.4   SIP     424   Status: 200 OK | 
 16  15.145932   10.10.20.1 -> 192.168.100.9   SIP     503   Request: BYE sip:1010@192.168.100.9:5060 | 
 17  15.364620   192.168.100.9 -> 10.10.20.1   SIP     490   Status: 200 OK |

According to what I see in the data, the Cisco phone gives a basic REGISTER and INVITE, while the Teo phone must provide full authentication for REGISTER and INVITE, and the connection gets dropped after initiating an INVITE.

0 Helpful

dstaudt
Cisco Employee
Cisco Employee
In response to Teo7810TSG6

‎03-07-2016 02:04 PM

The 'trusted' indicator has to do with secure signaling/media configuration, and shouldn't have any effect on general non-secure calls/operations.

The ability of the 7960 to register with digest authentication credentials is due to use of a proprietary Cisco SIP extension parameter in the Contact header, which functions to uniquely identify the device by its MAC rather than by the digest auth user identify.  I don't think this should effect basic SIP calling dynamics either...

Unless there is in fact a NAT in play, or Joe otherwise thinks this could be due to networking configuration, you  may need to go ahead and open a DevNet Developer Support ticket to get a detailed analysis of what's happening with this scenario via the CUCM-side logs:

https://developer.cisco.com/site/devnet/support/

0 Helpful

Teo7810TSG6
Level 1
Level 1
In response to dstaudt

‎03-08-2016 09:03 AM

For grins and giggles, I configured our phones to use UDP, instead of TCP.  Lo and behold, they can ring a Cisco phone!  But then when I tried to call a Teo phone from another Teo phone, I got an error.  The server is trying to establish a TCP connection to a phone registered with a UDP connection.

  1   0.000000   192.168.100.6 -> 10.10.20.1   SIP 362  Request: OPTIONS sip:1092@10.10.20.1:5060 | 
  2   0.180997   10.10.20.1 -> 192.168.100.6   SIP 573  Status: 200 OK | 
  3   7.278450   192.168.100.6 -> 10.10.20.1   SIP/SDP 1144  Request: INVITE sip:1010@10.10.20.1:5060;user=phone | 
  4   7.462708   10.10.20.1 -> 192.168.100.6   SIP     380  Status: 100 Trying | 
  5   7.463277   10.10.20.1 -> 192.168.100.6   SIP     527  Status: 401 Unauthorized | 
  6   7.479969   192.168.100.6 -> 10.10.20.1   SIP     378  Request: ACK sip:1010@10.10.20.1:5060;user=phone | 
  7   7.490415   192.168.100.6 -> 10.10.20.1   SIP/SDP 1348  Request: INVITE sip:1010@10.10.20.1:5060;user=phone | 
  8   7.675676   10.10.20.1 -> 192.168.100.6   SIP     380  Status: 100 Trying | 
  9   8.585408   10.10.20.1 -> 192.168.100.6   SIP     705  Status: 180 Ringing | 
 10   8.973000   10.10.20.1 -> 192.168.100.6   SIP/SDP 986  Status: 200 OK | 
 11   8.982327   10.10.20.1 -> 192.168.100.6   RTP     214  PT=ITU-T G.711 PCMU, SSRC=0x69F, Seq=1695, Time=160, Mark
 12   9.002136   10.10.20.1 -> 192.168.100.6   RTP     214  PT=ITU-T G.711 PCMU, SSRC=0x69F, Seq=1696, Time=320
 13   9.002139   192.168.100.6 -> 10.10.20.1   SIP     607  Request: ACK sip:1010@10.10.20.1:5060 | 
 14   9.022062   10.10.20.1 -> 192.168.100.6   RTP     214  PT=ITU-T G.711 PCMU, SSRC=0x69F, Seq=1697, Time=480
...
215  11.041810   10.10.20.1 -> 192.168.100.6   RTP     214  PT=ITU-T G.711 PCMU, SSRC=0x69F, Seq=1798, Time=16640
216  11.055009   10.10.20.1 -> 192.168.100.6   SIP     503  Request: BYE sip:1092@192.168.100.6:5060;transport=udp | 
217  11.056974   192.168.100.6 -> 10.10.20.1   RTP     214  PT=ITU-T G.711 PCMU, SSRC=0x10F4ACE8, Seq=30803, Time=240453258
218  11.061820   10.10.20.1 -> 192.168.100.6   RTP     214  PT=ITU-T G.711 PCMU, SSRC=0x69F, Seq=1799, Time=16800
219  11.062801   192.168.100.6 -> 10.10.20.1   SIP     570  Status: 200 OK | 
220  11.081896   10.10.20.1 -> 192.168.100.6   RTP     214  PT=ITU-T G.711 PCMU, SSRC=0x69F, Seq=1800, Time=16960
221  11.101830   10.10.20.1 -> 192.168.100.6   RTP     214  PT=ITU-T G.711 PCMU, SSRC=0x69F, Seq=1801, Time=17120
222  11.135030   10.10.20.1 -> 192.168.100.6   ICMP    242  Destination unreachable (Port unreachable)
223  11.155566   10.10.20.1 -> 192.168.100.6   ICMP    242  Destination unreachable (Port unreachable)
224  11.177083   10.10.20.1 -> 192.168.100.6   ICMP    242  Destination unreachable (Port unreachable)
225  11.195021   10.10.20.1 -> 192.168.100.6   ICMP    242  Destination unreachable (Port unreachable)
226  11.215100   10.10.20.1 -> 192.168.100.6   ICMP    242  Destination unreachable (Port unreachable)
227  11.234999   10.10.20.1 -> 192.168.100.6   ICMP    242  Destination unreachable (Port unreachable)
228  13.996262   TeoTechn_ee:14:ad -> CiscoInc_a3:07:a4 ARP 60  Who has 192.168.100.1? Tell 192.168.100.6
229  13.996596   CiscoInc_a3:07:a4 -> TeoTechn_ee:14:ad ARP 60  192.168.100.1 is at fc:99:47:a3:07:a4
230  17.644254   192.168.100.6 -> 10.10.20.1   SIP/SDP 1141  Request: INVITE sip:1090@10.10.20.1:5060;user=phone | 
231  17.660087   192.168.100.4 -> 10.10.20.1   SIP     368  Request: OPTIONS sip:1090@10.10.20.1:5060 | 
232  17.829219   10.10.20.1 -> 192.168.100.6   SIP     380  Status: 100 Trying | 
233  17.829872   10.10.20.1 -> 192.168.100.6   SIP     527  Status: 401 Unauthorized | 
234  17.841039   10.10.20.1 -> 192.168.100.4   SIP     579  Status: 200 OK | 
235  17.845822   192.168.100.6 -> 10.10.20.1   SIP     378  Request: ACK sip:1090@10.10.20.1:5060;user=phone | 
236  17.855347   192.168.100.6 -> 10.10.20.1   SIP/SDP 1345  Request: INVITE sip:1090@10.10.20.1:5060;user=phone | 
237  18.039380   10.10.20.1 -> 192.168.100.6   SIP     380  Status: 100 Trying | 
238  18.056529   10.10.20.1 -> 192.168.100.4   TCP 74  42704 → 5060 [SYN] Seq=0 Win=14600 Len=0 MSS=1380 SACK_PERM=1 TSval=538973502 TSecr=0 WS=128
239  18.056836   192.168.100.4 -> 10.10.20.1   TCP 60  5060 → 42704 [RST, ACK] Seq=1 Ack=1 Win=0 Len=0
240  18.238116   10.10.20.1 -> 192.168.100.6   SIP     498  Status: 503 Service Unavailable | 
241  18.243883   192.168.100.6 -> 10.10.20.1   SIP     419  Request: ACK sip:1090@10.10.20.1:5060;user=phone | 
242  18.271020   192.168.100.6 -> 10.10.20.1   SIP     863  Request: REGISTER sip:10.10.20.1:5060;transport=udp  (1 binding) | 
243  18.453126   10.10.20.1 -> 192.168.100.6   SIP     356  Status: 100 Trying | 
244  18.454275   10.10.20.1 -> 192.168.100.6   SIP     494  Status: 200 OK  (1 binding) | 
245  18.465797   192.168.100.6 -> 10.10.20.1   SIP     362  Request: OPTIONS sip:1092@10.10.20.1:5060 | 
246  18.646657   10.10.20.1 -> 192.168.100.6   SIP     572  Status: 200 OK | 
247  22.655914   TeoTechn_00:18:4e -> CiscoInc_a3:07:a4 ARP 60  Who has 192.168.100.1? Tell 192.168.100.4
248  22.656266   CiscoInc_a3:07:a4 -> TeoTechn_00:18:4e ARP 60  192.168.100.1 is at fc:99:47:a3:07:a4
249  47.960865   192.168.100.4 -> 10.10.20.1   SIP     368  Request: OPTIONS sip:1090@10.10.20.1:5060 | 
250  48.142528   10.10.20.1 -> 192.168.100.4   SIP     579  Status: 200 OK | 
251  49.528340   192.168.100.6 -> 10.10.20.1   SIP     362  Request: OPTIONS sip:1092@10.10.20.1:5060 | 
252  49.709342   10.10.20.1 -> 192.168.100.6   SIP     573  Status: 200 OK | 
253  49.983048   192.168.100.4 -> 10.10.20.1   SIP     869  Request: REGISTER sip:10.10.20.1:5060;transport=udp  (1 binding) | 
254  50.165053   10.10.20.1 -> 192.168.100.4   SIP     362  Status: 100 Trying | 
255  50.166450   10.10.20.1 -> 192.168.100.4   SIP     500  Status: 200 OK  (1 binding) | 
256  50.180282   192.168.100.4 -> 10.10.20.1   SIP     368  Request: OPTIONS sip:1090@10.10.20.1:5060 | 
257  50.361451   10.10.20.1 -> 192.168.100.4   SIP     577  Status: 200 OK | 
258  54.524545   TeoTechn_ee:14:ad -> CiscoInc_a3:07:a4 ARP 60  Who has 192.168.100.1? Tell 192.168.100.6
259  54.524906   CiscoInc_a3:07:a4 -> TeoTechn_ee:14:ad ARP 60  192.168.100.1 is at fc:99:47:a3:07:a4

At packet 238, the server tries to contact the Teo phone using TCP instead of UDP.  You can see the Teo phone at 192.168.100.4 chattering with the server on UDP, and reregistering itself.  At first I thought that something in the server just needed to be flushed out, but it's still the same overnight.  I'm going to try deleting and readding the phones.

Server: 10.10.20.1

Teo phone: 192.168.100.4

Teo phone: 192.168.100.6

Cisco phone not shown.

0 Helpful

Teo7810TSG6
Level 1
Level 1
In response to Teo7810TSG6

‎03-08-2016 03:43 PM

I was informed to retry TCP, so I switched the Teo configuration back to TCP, and use the "Third-party SIP Device Basic - Standard SIP Non-Secure Profile" security profile.
The phone had been working OK for a while with UDP.  The following is what I got trying TCP.

The Teo phone registers using TCP.

Then I called the Teo phone.

The server attempts to establish a UDP session, while specifying that its transport is TCP!

No. Source          Dest            Protocol    Length  Information
1   192.168.100.6   10.10.20.1      SIP TCP     665     Request: REGISTER sip:10.10.20.1:5060;transport=tcp  (1 binding) | 
2   10.10.20.1      192.168.100.6   SIP TCP     348     Status: 100 Trying | 
3   10.10.20.1      192.168.100.6   SIP TCP     486     Status: 200 OK  (1 binding) | 
4   192.168.100.6   10.10.20.1      SIP TCP     665     Request: REGISTER sip:10.10.20.1:5060;transport=tcp  (1 binding) | 
5   10.10.20.1      192.168.100.6   SIP UDP     555     Request: NOTIFY sip:1092@192.168.100.6:5060;transport=tcp | 
6   192.168.100.6   10.10.20.1      ICMP        576     Destination unreachable (Port unreachable)
7   10.10.20.1      192.168.100.6   SIP UDP     555     Request: NOTIFY sip:1092@192.168.100.6:5060;transport=tcp | 
8   192.168.100.6   10.10.20.1      ICMP        576     Destination unreachable (Port unreachable)
9   10.10.20.1      192.168.100.6   SIP UDP     555     Request: NOTIFY sip:1092@192.168.100.6:5060;transport=tcp | 
10  192.168.100.6   10.10.20.1      ICMP        576     Destination unreachable (Port unreachable)
11  10.10.20.1      192.168.100.6   SIP UDP     555     Request: NOTIFY sip:1092@192.168.100.6:5060;transport=tcp | 
12  192.168.100.6   10.10.20.1      ICMP        576     Destination unreachable (Port unreachable)
13  10.10.20.1      192.168.100.6   SIP UDP     555     Request: NOTIFY sip:1092@192.168.100.6:5060;transport=tcp | 
14  192.168.100.6   10.10.20.1      ICMP        576     Destination unreachable (Port unreachable)
15  10.10.20.1      192.168.100.6   SIP UDP     555     Request: NOTIFY sip:1092@192.168.100.6:5060;transport=tcp | 
16  192.168.100.6   10.10.20.1      ICMP        576     Destination unreachable (Port unreachable)
17  10.10.20.1      192.168.100.6   SIP UDP     555     Request: NOTIFY sip:1092@192.168.100.6:5060;transport=tcp | 
18  192.168.100.6   10.10.20.1      ICMP        576     Destination unreachable (Port unreachable)
19  10.10.20.1      192.168.100.6   SIP UDP     555     Request: NOTIFY sip:1092@192.168.100.6:5060;transport=tcp | 
20  192.168.100.6   10.10.20.1      ICMP        576     Destination unreachable (Port unreachable)
21  10.10.20.1      192.168.100.6   SIP UDP     555     Request: NOTIFY sip:1092@192.168.100.6:5060;transport=tcp | 
22  192.168.100.6   10.10.20.1      ICMP        576     Destination unreachable (Port unreachable)
23  10.10.20.1      192.168.100.6   SIP UDP     555     Request: NOTIFY sip:1092@192.168.100.6:5060;transport=tcp | 
24  192.168.100.6   10.10.20.1      ICMP        576     Destination unreachable (Port unreachable)
25  10.10.20.1      192.168.100.6   SIP UDP     555     Request: NOTIFY sip:1092@192.168.100.6:5060;transport=tcp | 
26  192.168.100.6   10.10.20.1      ICMP        576     Destination unreachable (Port unreachable)
27  10.10.20.1      192.168.100.6   SIP/SDP UDP 1075    Request: INVITE sip:1092@192.168.100.6:5060;transport=tcp | 
28  192.168.100.6   10.10.20.1      ICMP        576     Destination unreachable (Port unreachable)
29  10.10.20.1      192.168.100.6   SIP/SDP UDP 1075    Request: INVITE sip:1092@192.168.100.6:5060;transport=tcp | 
30  192.168.100.6   10.10.20.1      ICMP        576     Destination unreachable (Port unreachable)
31  10.10.20.1      192.168.100.6   SIP/SDP UDP 1075    Request: INVITE sip:1092@192.168.100.6:5060;transport=tcp | 
32  192.168.100.6   10.10.20.1      ICMP        576     Destination unreachable (Port unreachable)
33  10.10.20.1      192.168.100.6   SIP/SDP UDP 1075    Request: INVITE sip:1092@192.168.100.6:5060;transport=tcp | 
34  192.168.100.6   10.10.20.1      ICMP        576     Destination unreachable (Port unreachable)
35  10.10.20.1      192.168.100.6   SIP/SDP UDP 1075    Request: INVITE sip:1092@192.168.100.6:5060;transport=tcp | 
36  192.168.100.6   10.10.20.1      ICMP        576     Destination unreachable (Port unreachable)
37  10.10.20.1      192.168.100.6   SIP/SDP UDP 1075    Request: INVITE sip:1092@192.168.100.6:5060;transport=tcp | 
38  192.168.100.6   10.10.20.1      ICMP        576     Destination unreachable (Port unreachable)
39  192.168.100.6   10.10.20.1      SIP TCP     665     Request: REGISTER sip:10.10.20.1:5060;transport=tcp  (1 binding) |
0 Helpful

dstaudt
Cisco Employee
Cisco Employee

‎03-04-2016 08:21 AM

How is the SIP phone connected to the UCM?  I note that the phone and CUCM IP addresses are 10.10.x.x and 192.168.x.x addresses - normally this are not routable to each other...I would expect the phone and CUCM to both be using 10.10.x.x addresses.

As Joe mentions, can you provide details on the connectivity - VPNs, routers, NATs, etc...?

0 Helpful
Customers Also Viewed These Support Documents