Solved Analog GW forwarded to IVR

[AWS2P]

Hi,
I'd like to know if you already encountered this behavior :

on a pbx I have a old SPA3102 used as generic trunk on PBX side, and incoming calls are forwarded to a first standard IVR with 3 choices.
One on a RG
2ND to an extension
3rd other extension

when I call the public GW number I hear properly IVR choices, forwarding seems to work but from APP extension on android, extension turns yellow like in call but never give a chance to answer with a button or notification and few time after caller goes on extension VM.

Just to say , App works properly when test call are done without using the GW (notification to answer is displayed in others cases)

Also, when there is no choice in IVR and call is forwarded to a deskphone extension, then it works.

Could it be a bug with couple IVR/APP?

 

[leejor]

when I call the public GW number I hear properly IVR choices, forwarding seems to work but from APP extension on android, extension turns yellow like in call but never give a chance to answer with a button or notification and few time after caller goes on extension VM.

Just so I'm clear....incoming calls from the Gateway, to the IVR, all work correctly, but, calls to the IVR number directly, using a 3CX extension, as an App, are having the issue? If that is not it, then exactly what is the App calling if not the number of the IVR? And...if it is dialling the IVR directly, does this happen when calling other IVRs on the system ?

 

[AWS2P]

Thanks Leejor, for new tracks to follow
SPA and PBX were working on Saturday, now when I call Public phone number going through GW , I reach IVR and hear choices with no problem, but when choice is done call should go to an APP on Android smartphone, but on APP callee extension is yellow and display already on call.
App never display any button to answer nor notifications and finally call goes to VM when timeout.

Like you asked me , now I need to test internal calls directly to IVR and see if it behave the same.

Nota: PBX is running on a PI, both have been rebooted with no change.

 

[AWS2P]

Ok so internal test call to IVR works fine on app, so most probably this is a problem with generic trunk coupled to IVR and APP ?

 

[leejor]

OK, so I think I'm a bit more clear. the issue is that the IVR call, to an extension, which happens to be an Android App cannot be answered and goes direct to voicemail, is this correct?

If that is the case, then I would check to see if any other calls to the IVR (another incoming trunk...SIP?) behaves the same. I would also check the Activity log to see what 3CX sees as the status of the App extension when a call to it is attempted. 3Cx can only send a call if it sees the extension as available. Compare this log with a working call. Substitute an actual deskset extension, for the App, and see if it does the same thing on calls from the 3102.

...or another Android phone (extension) altogether. Perhaps it is a Push issue.

 

[AWS2P]

OK, so I think I'm a bit more clear. the issue is that the IVR call, to an extension, which happens to be an Android App cannot be answered and goes direct to voicemail, is this correct?

Yes, Leejor, you properly understood the problem.
This is a test PBX so for now there's no SIP trunk just that SPA3102 GW, no deskphones , only Android APP and webclient.
Internal Calls between app are working fine, even out of LAN

For Android push do we always need to open specific ports ? but not sure it can be a push problem as when calls are out of Trunk GW they are working fine with same smartphone on same extensions.

For now , no more test until tomorrow morning for us, so Thanks for help , stay tuned for next step .

 

[AWS2P]

Finally I catch an explaination, phone numbers were added as spam (don't know why), but after removing them everything works normally.
Thanks Leejor for Assistance, appreciate.