NO JOY Inbound callers not hearing ringback

[rylen]

My inbound callers are not hearing a ring tone.
--
I'm set up w/ FreePBX 12.0.76.2 (the most recent update). It has been working well for a long while but incoming callers have suddenly stopped hearing a ring when they call in while they wait for someone to pick up. The phone still rings on our side and goes to voice mail if not answered, but the caller gets no feedback that something is happening. So far I've confirmed it as a problem for T-Mobile and Verizon phones in my area. I've been in touch with my VoIP folks, Callcentric; they dialed my number and heard rings. Calling internally (from 101 -> 102), I hear a ring.

The first incident I've heard about was about a week ago, though I've just now learned of it.

I read that "Inbound Routes->Signal RINGING" would help. I tried checking that box for my inbound routes, but it had no effect so I reverted it.

I've also tried simple things like running "amportal chown" and rebooting the PBX.

I've read that the caller's phone company is responsible for the tone. (http://community.freepbx.org/t/no-ringing-for-the-person-whos...) I'm not sure how to track that down, find out what changes they made, or how to signal them to provide the ringback.

I appreciate your help.

 

[briankelly63]

This is most often a provider - incoming route issue on THEIR side. It also depends where the call originates from so them calling and hearing a ring doesn't mean anything. Often this can be simulated by calling from a voip line tagged with a particular areacode and exchange in a spoofed caller-id scenerio. With one caller-id it will work and another it won't. Because they are taking different routes. Set up a random DID from another provider and see what happens. This is why I like Anveo Direct. I like to be able to get SIP traces from THEIR side.

There are ways to make the ringtone come from the PBX to the outside caller but that usually involves answering the call first and then providing ringtone. In the old days there would be a talk path even on an unsupervised (un-answered)call but not any more.

 

[rylen]

This is most often a provider - incoming route issue on THEIR side. It also depends where the call originates from so them calling and hearing a ring doesn't mean anything. Often this can be simulated by calling from a voip line tagged with a particular areacode and exchange in a spoofed caller-id scenerio. With one caller-id it will work and another it won't. Because they are taking different routes. Set up a random DID from another provider and see what happens. This is why I like Anveo Direct. I like to be able to get SIP traces from THEIR side.

There are ways to make the ringtone come from the PBX to the outside caller but that usually involves answering the call first and then providing ringtone. In the old days there would be a talk path even on an unsupervised (un-answered)call but not any more.

I'm not sure how to do any of that.

Also, I've now learned that it does not have a ringback for an AT&T cellphone calling from another state. (Caller is in Alabama and I'm in South Carolina.)

 

[briankelly63]

PM me and give me some of the numbers involved and what number they are calling and I'll see what I find.

 

[rylen]

Probably not a cause -- bad housekeeping.

I was looking at my Asterisk logs. I recently got rid of a different account that also came to my PBX but had not deleted it as an inbound route. I don't see how this would create the problem but the timing works. I've since deleted that route with no change.

 

[rylen]

Verdict: somehow my server went wrong.

I installed an X-Lite softphone, connected directly to Callcentric (after turning off my PBX), and calling in from my cell phone had a ringback.

 

[briankelly63]

As discussed Callcentric must have been waiting for a SIP message it wasn't getting

 

[atsak]

Sometimes adding progressinband=yes to sip settings seems to help this problem . . .

 

[rylen]

Callcentric had me add these lines to the trunk:

prematuremedia=no
progressinband=yes​

It didn't work.

 

[briankelly63]

It's not an inband issue. Setting up wireshark is no easy task if you set it up on a mirrored port of a switch but it would show you the message dialog happening between callcentric and the softphone or the pbx. Better to just set up a did from another provider and see if that works.

 

[briankelly63]

is callcentric seeing this from you? maybe they could send you a trace. You can see if Asterisk is sending it by going into the CLI turning on sip debug and watching as you call in

Would look like this:
/*<<<|61.240.32.229:5060 @ 2016-04-18 20:13:56 */
SIP/2.0 180 Ringing

/*<<<|61.240.32.229:5060 @ 2016-04-18 20:13:56 */
SIP/2.0 183 Session Progress
Via: SIP/2.0/UDP 50.22.101.14:5060;branch=z9hG4bK57e24d31f06f6518fd6645ed2fd75578;received=50.22.101.14;rport=5060


21.1.2 180 Ringing


The UA receiving the INVITE is trying to alert the user. This
response MAY be used to initiate local ringback.


21.1.5 183 Session Progress


The 183 (Session Progress) response is used to convey information
about the progress of the call that is not otherwise classified. The
Reason-Phrase, header fields, or message body MAY be used to convey
more details about the call progress.

 

[rylen]

Today in unexpected developments ... I updated the PiaF server that I've kept in use while I tried to get the Incredible PBX running and ringbacks are now working again.