Hi Mark,
Glad to hear you made it all work! Looks like it was a real challenge.
Good luck,
Stas
On Wed, Aug 26, 2020 at 8:47 AM Mark Allen wrote:
> Hi Stas - thanks for getting back to me. That helped me move forward a lot
> - particularly where you included what you see in the Path field -
Hi Stas - thanks for getting back to me. That helped me move forward a lot
- particularly where you included what you see in the Path field - it
helped to exclude a range of possible causes for the issues I was seeing.
> If you do not have "path" set in your case the problem is probably there.
On 26.08.2020 15:24, Vitaliy Aleksandrov wrote:
Your suggestion with async(sleep(), resume) is really cool.
Hey, Vitaliy!
I know, right? All programming textbooks say: "sleep() is bad", "Avoid
synchronizing with sleep()", "sleep() is hackish", etc. But, for this
use case, async(sleep())
Hi Liviu,
Your suggestion with async(sleep(), resume) is really cool. I use
async(wait_for_event(), resume) a bit differently and pause a call for
another type of event that is generated upon reception of an external
notification (SIP or clusterer) and had to patch event_routing, add a
timer
Hi, Denys!
Yes, the upstream proxy should create two different transactions, hence
two different dialogs will be created on the current proxy side.
Best regards,
Răzvan Crainea
OpenSIPS Core Developer
http://www.opensips-solutions.com
On 8/25/20 11:07 PM, Denys Pozniak wrote:
Hello!
Could
