cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1355
Views
0
Helpful
7
Replies

Cisco 50x-30x big problem with Hold

Diego Betancor
Level 1
Level 1

Hi,

We are a voip provider that recommends to its customers Cisco/SPA. The problem is that when a call is placed in hold (sends a=sendonly in a re-INVITE and receives a a=recvonly in the 200 OK) it is ok for about 1 minute when unholding it (sends and receives a=sendrecv), the phone resume sending and processing RTP packets.

But if the call if place in hold for more that 1 minute (the time varies), when unholding it the phone does not send RTP or proccess the received (tdpdump).

 

I have tried everything, changing firmware (older 7.4.9, middle 7.5.5 and the latest 7.6.2), Hold Package, RFC 2543 Call Hold:, increasing the re-INVITE timer and never sending a 200 OK, but just a 100 Trying (when unholding the phone sends a BYE). Whe have tried in 303, 504 y 508.

 

This seams to me a serious bug with the phone. Yealink phones act perfectly.

 

Thank you, Diego Betancor

 

 

1 Accepted Solution

Accepted Solutions

Glad to hear you solved it. Use "correct answer" button associated with your's previous post to claim this thread solved.

View solution in original post

7 Replies 7

Diego Betancor
Level 1
Level 1

I cannot see any difference in the logs when you hear or not

HOLD
Sep 27 13:45:00 spa508g [14]CC:NewCallState 15/13
Sep 27 13:45:00 spa508g
Sep 27 13:45:00 spa508g [3:34907]->130.117.91.34:16080{728)  re-INVITE
Sep 27 13:45:00 spa508g
Sep 27 13:45:00 spa508g SIP_tsClientEventProc ts:0x94946d90 event 27 state:1
Sep 27 13:45:00 spa508g start TMR K
Sep 27 13:45:00 spa508g [3:34907]<<130.117.91.34:16080  100
Sep 27 13:45:00 spa508g
Sep 27 13:45:00 spa508g [3:34907]<<130.117.91.34:16080  200 OK
Sep 27 13:45:00 spa508g
Sep 27 13:45:00 spa508g [14]CC:NewCallState 14/15
Sep 27 13:45:00 spa508g
Sep 27 13:45:00 spa508g [3:34907]->130.117.91.34:16080{452)  ack

 

UNHOLD
Sep 27 13:46:29 spa508g [CMXHTTP] force stop wav
Sep 27 13:46:29 spa508g [14]CC:NewCallState 16/14
Sep 27 13:46:29 spa508g
Sep 27 13:46:29 spa508g [3:34907]->130.117.91.34:16080{732)
Sep 27 13:46:29 spa508g
Sep 27 13:46:29 spa508g SIP_tsClientEventProc ts:0x9493e2e0 event 27 state:1
Sep 27 13:46:29 spa508g start TMR K
Sep 27 13:46:29 spa508g [3:34907]<<130.117.91.34:16080
Sep 27 13:46:29 spa508g
Sep 27 13:46:29 spa508g [3:34907]<<130.117.91.34:16080
Sep 27 13:46:29 spa508g
Sep 27 13:46:29 spa508g [14]CC:NewCallState 13/16
Sep 27 13:46:29 spa508g
Sep 27 13:46:29 spa508g [3:34907]->130.117.91.34:16080{452)

tcpdump host 192.168.0.18 and udp and port not 1024 -n

 

 

When works

14:12:30.174305 IP 192.168.0.18.36022 > 130.117.91.35.47260: UDP, length 252
14:12:30.204329 IP 192.168.0.18.36022 > 130.117.91.35.47260: UDP, length 252
14:12:30.220316 IP 130.117.91.35.47260 > 192.168.0.18.36022: UDP, length 252
14:12:30.234275 IP 192.168.0.18.36022 > 130.117.91.35.47260: UDP, length 252
14:12:30.250756 IP 130.117.91.35.47260 > 192.168.0.18.36022: UDP, length 252
14:12:30.264422 IP 192.168.0.18.36022 > 130.117.91.35.47260: UDP, length 252
14:12:30.280276 IP 130.117.91.35.47260 > 192.168.0.18.36022: UDP, length 252
14:12:30.294378 IP 192.168.0.18.36022 > 130.117.91.35.47260: UDP, length 252
14:12:30.310634 IP 130.117.91.35.47260 > 192.168.0.18.36022: UDP, length 252
14:12:30.340224 IP 130.117.91.35.47260 > 192.168.0.18.36022: UDP, length 252

 

HOLD -- UNHOLD  23 sc

14:12:53.290757 IP 130.117.91.35.47260 > 192.168.0.18.36022: UDP, length 252
14:12:53.320341 IP 130.117.91.35.47260 > 192.168.0.18.36022: UDP, length 252
14:12:53.350714 IP 130.117.91.35.47260 > 192.168.0.18.36022: UDP, length 252
14:12:53.374677 IP 192.168.0.18.36022 > 130.117.91.35.47260: UDP, length 252
14:12:53.380269 IP 130.117.91.35.47260 > 192.168.0.18.36022: UDP, length 252
14:12:53.404605 IP 192.168.0.18.36022 > 130.117.91.35.47260: UDP, length 252
14:12:53.410633 IP 130.117.91.35.47260 > 192.168.0.18.36022: UDP, length 252
14:12:53.434492 IP 192.168.0.18.36022 > 130.117.91.35.47260: UDP, length 252
14:12:53.440395 IP 130.117.91.35.47260 > 192.168.0.18.36022: UDP, length 252
14:12:53.464508 IP 192.168.0.18.36022 > 130.117.91.35.47260: UDP, length 252
14:12:53.470737 IP 130.117.91.35.47260 > 192.168.0.18.36022: UDP, length 252
14:12:53.494655 IP 192.168.0.18.36022 > 130.117.91.35.47260: UDP, length 252
14:12:53.500464 IP 130.117.91.35.47260 > 192.168.0.18.36022: UDP, length 252
14:12:53.524646 IP 192.168.0.18.36022 > 130.117.91.35.47260: UDP, length 252
14:12:53.530657 IP 130.117.91.35.47260 > 192.168.0.18.36022: UDP, length 252
14:12:53.554522 IP 192.168.0.18.36022 > 130.117.91.35.47260: UDP, length 252
14:12:53.560230 IP 130.117.91.35.47260 > 192.168.0.18.36022: UDP, length 252
14:12:53.584507 IP 192.168.0.18.36022 > 130.117.91.35.47260: UDP, length 252



When it doesn't
14:15:37.315336 IP 192.168.0.18.36022 > 130.117.91.35.47260: UDP, length 252
14:15:37.336150 IP 130.117.91.35.47260 > 192.168.0.18.36022: UDP, length 252
14:15:37.345323 IP 192.168.0.18.36022 > 130.117.91.35.47260: UDP, length 252
14:15:37.361152 IP 130.117.91.35.47260 > 192.168.0.18.36022: UDP, length 252
14:15:37.375489 IP 192.168.0.18.36022 > 130.117.91.35.47260: UDP, length 252
14:15:37.391447 IP 130.117.91.35.47260 > 192.168.0.18.36022: UDP, length 252
14:15:37.421242 IP 130.117.91.35.47260 > 192.168.0.18.36022: UDP, length 252
14:15:37.451531 IP 130.117.91.35.47260 > 192.168.0.18.36022: UDP, length 252

HOLD -- UNHOLD  3 minutes

14:18:36.983390 IP 192.168.0.18.36022 > 130.117.91.35.47260: UDP, length 252
14:18:37.013269 IP 192.168.0.18.36022 > 130.117.91.35.47260: UDP, length 252
14:18:37.043341 IP 192.168.0.18.36022 > 130.117.91.35.47260: UDP, length 252
14:18:37.073280 IP 192.168.0.18.36022 > 130.117.91.35.47260: UDP, length 252
14:18:37.103321 IP 192.168.0.18.36022 > 130.117.91.35.47260: UDP, length 252
14:18:37.133239 IP 192.168.0.18.36022 > 130.117.91.35.47260: UDP, length 252
14:18:37.163249 IP 192.168.0.18.36022 > 130.117.91.35.47260: UDP, length 252
14:18:37.193278 IP 192.168.0.18.36022 > 130.117.91.35.47260: UDP, length 252
14:18:37.223245 IP 192.168.0.18.36022 > 130.117.91.35.47260: UDP, length 252
14:18:37.253273 IP 192.168.0.18.36022 > 130.117.91.35.47260: UDP, length 252
14:18:37.283374 IP 192.168.0.18.36022 > 130.117.91.35.47260: UDP, length 252
14:18:37.313272 IP 192.168.0.18.36022 > 130.117.91.35.47260: UDP, length 252
14:18:37.343241 IP 192.168.0.18.36022 > 130.117.91.35.47260: UDP, length 252
14:18:37.373338 IP 192.168.0.18.36022 > 130.117.91.35.47260: UDP, length 252
14:18:37.403244 IP 192.168.0.18.36022 > 130.117.91.35.47260: UDP, length 252

 

 

Full capture, please. RTP packets together with SIP packets and log messages. Also just list of packets is not enough, disclose packets with content. Save tcpdump into file (option -w), don't forget to use '-s 2000' or so and attach resulting file here. Please disclose where in the network topology you grab packets (PBX side, phone side). Don't forget to describe overall network topology between phone and PBX (router, NAT, firewall). Be patient, I will not respond before Saturday. But someone else may respond if required information for issue analysis will be available.

 

By the way, as just blind shot, I suspect NAT or stateful firewall to be cause.

The log is so brief.And we don't know they are from successful resume attempt or from the unsuccessful one.

 

Increase log level to maximum, turn on debug messages as well and catch all log and debug messages sent by phone. Also, catch all SIP and RTP packets sent/received by phone.

Also, describe network topology between phone and PBX (is there router ? NAT ? firewall ? ). It may help us to advise something valuable. All I can tell you now is - it just works for me.

 

This post contain information related to other's site thus it may contain information considered Sensitive or Confidential.

Hi, before wasting your time I am going to check the NAT during the weekend (taking the phone home and trying it there and in other locations). If I think it is the NAT I will see why the yealink works and not the Cisco's and try to fix it. I will report during next week.

 

Thank you to all.

 

Diego

 

Hi,

the problem was indeed in the router that was doing some firewalling by itself. We disabled the firewall and everything works fine.

 

Thank you. Diego

Glad to hear you solved it. Use "correct answer" button associated with your's previous post to claim this thread solved.

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: