Btw, afaik this just means it didn’t get RTP setup properly. You’d need a full PCAP to diagnose. (Though Vitelity should be able to grab any SIP PCAP on demand.)

From: freeswitch-users-bounces@lists.freeswitch.org [mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Sean Devoy
Sent: Friday, 4 December, 2015 15:17
To: FreeSWITCH Users Help <freeswitch-users@lists.freeswitch.org>
Subject: [Freeswitch-users] Vitelity Calls failing on my server - Ideas

Hi!

My VOIP provider is Vitelity.  A few hours ago SOME of my customers reported phone failures – Rings no answer for the caller.

I understand this is NOT a FreeSwitch problem, but I thought someone here may be able to identify the problem quickly.  I would greatly appreciate it if you could read the rest and comment if you know something that might help get me back online.

I have debugged what I know.  I have identical calls wioth logs to 2 different numbers that are handled identically on my freeswitch server (going to an IVR).

The critical difference I see in the logs is here:

EXECUTE sofia/external_noauth/4108084699@66.241.96.237 ivr(estabrook_attendant_1)

2015-12-04 15:16:10.628821 [DEBUG] switch_ivr_menu.c:721 switch_ivr_menu_stack_xml_add binding 'menu-exit'

… ivr continues

2015-12-04 15:16:10.628821 [DEBUG] switch_ivr_play_say.c:1314 Codec Activated L16@8000hz 1 channels 20ms

2015-12-04 15:16:10.698805 [DEBUG] switch_rtp.c:3757 Correct ip/port confirmed.

2015-12-04 15:16:19.448558 [DEBUG] switch_core_session.c:1016 Send signal sofia/external_noauth/4108084699@66.241.96.237 [BREAK]

On the calls that are failing the debug line “switch_rtp.c:3757 Correct ip/port confirmed” does not happen.  Instead I eventually get “[DEBUG] switch_ivr_menu.c:643 IVR menu 'bfis_attendant_1' no input detected”, all the while the line is ringing on caller end.

If someone understands what that means and I could tell them, it might get my customers back online quicker.

Thanks for your time,

Sean