Microsoft Teams Integration
Hikvision Intercom Integration
ISDN Switch-off Migration
All materials to evaluate Yeastar as a PBX vendor on products, solutions, partner program, support, learning resources, etc.
We have problem with CallBack functionality in MyPBX-Standars V4 equipped by FW 2.18.0.22. Functional part is this: "MyPBX allows caller A to dial an inbound route number, and after hearing the ring, A can hang up the call, then mPBX will call A with this number." Non-functional part is this: "When A pick up the call, A can dial the number he wants to call; mPBX will call the number with its outbound route." When we pick up the phone, MyPBX just ends a call. There is no prompt, no other action. What we do wrong?
Date
Votes
7 comments
-
Oscar Colka What is your inbound route destination? What the PBX would action depends on your inbound route's destination.
If you would like to be able to dial out through outbound route, you may need to setup the inbound route's destination as Outbound Route.
I would suggest you to try different distinatioin and see the difference results.
-
Marek Sinkora Inbound Route destination works for everything which is inside of MyPBX, i.e. extension, voicemail, IVR, queues, etc. However, if I use outbound route to the same VoIP trunk, I create a loop at the provider as it came in on the provider trunk, left the MyPBX on the provider trunk, but had the same number FROM and TO (it is a DID number of extension 599 I have called from my cell phone to request the CallBack). As a consequence, the same call came back in to the MyPBX until the provider call path is filled at which point the provider could not handle more calls and send a 403 to get me to stop and the 200 OK is received for each call (in my case 20 billed calls during 2 seconds until provider disconnect me from registration). There is no chance to put any number on the cell phone when MyPBX call me back and I pick up the call. So what is wrong in outbound route definition and why MyPBX behaves in this way?
This is how the Outbound Route looks like:
-
Oscar Colka Please check if you have enable callback on inbound route page. See below screenshot:
-
Oscar Colka Sorry, the screenshot I post was captured from version 14.19.0.48, it might be different from that of 2.18.0.22(I guess this is version 1 Yeastar MyPBX?), not sure if 2.18.0.22 has this option or not.
-
Marek Sinkora I have the Callback option in version 2.18.0.22 for Inbound Routes and it is certainly enabled. Otherwise, the callback probably should not work. A problem is a second part - you have the Destination to "pstnout" so it is different trunk (pathway SIP trunk -> PSTN trunk). I have destination to the same SIP trunk (pathway SIP trunk -> SIP trunk). I bet this could be done since the same SIP trunk can handle many calls. However, MyPBX probably uses the same Caller ID in the same SIP trunk so that the same number calls the same number. In other words, fields To: and From: have the same Caller IDs. I need to avoid this somehow.
-
Oscar Colka Got you, probably would caused by the Caller ID. Could you please provide some asterisk CLI logs? If you could, please enable SIP debug and check if the Caller ID is set properly before call back.
-
Marek Sinkora There is no way how DID can be changed because it must go through provider credentials security. Unfortunately, MyPBX always passes original DID through Callback and there is no way how to change it. This ends up in a loop where called number is the same as caller number if using the same trunk. This type of functional connection is impossible in classic telephony but apparently allowed using MyPBX.
In any case and fortunately, I have found resolution thanks to helpful person and I am surprised that I did not find an answer over internet. I just used DISA for routing and it is working like a charm.
Please sign in to leave a comment.