GetVarAction Timeout

[BuilovAlexey]

Hello.

I successfully used this lib (but earlier version maybe 2 years old version) with Asterisk 1.2, 1.6. But after updating asterisk.net lib now (master branch) - i get timeout for GetVarAction for all version of Asterisk (1.6, 13, 15) and ami (1.3, 2.10, 4.0).

This code:

method(DialEvent e)
ManagerResponse responseSrc;
String valueSrc = " ";
try {
    GetVarAction getVarActioneSrc = new GetVarAction(e.Channel, "CALLERID(num)");
    responseSrc = asteriskManagerConnection.SendAction(getVarActioneSrc, 8000);
    if (responseSrc.IsSuccess())
        valueSrc = responseSrc.GetAttribute("Value");
} catch (Exception ex){
     valueSrc = e.CallerIdName;
} 

After executing command SendAction I got ex = {"Timeout waiting for response to GetVar"}" (System.Collections.ListListDictionaryInternal type)

I checked GetVarAction with "CALLERID(all)", "UNIQUEID" and another Variable, which work fine in telnet - same result.

RedirectAction, HangupAction, OriginateAction - work fine.

This is debug. I got exception and check the same command in telnet - success:

What can it may?

[Deantwo]

Is this still an issue?

[BuilovAlexey]

I do not know, you tell me :)
The bug was reproduced in November 2017. Did you fix it in new commits? Did you check it?

[skrusty]

@BuilovAlexey with respect, we're not here to do everything, this is an open source project. Your input on if an issue has been fixed or not would be greatly appreciated, but if you're unable or not willing to, then we will close the issue until it's either reported again, or something is willing to review it.

[Deantwo]

I am just going through a few old issues.

I don't quite understand this issue so I don't know if it was fixed or if you found a workaround.

[BuilovAlexey]

@skrusty No, I did not correct this bug in this project. I just went back to the earlier version of the project, where there was not this error.
You do not close issue if it is not solved by anyone? So let it be open I think. And other developers could see it and do not ask again

[skrusty]

@BuilovAlexey My point is you don't need to be rude to other contributors, simply saying you're unaware if the issue is fixed, or pointing to how you resolved it by using an older version would be useful.

[Deantwo]

So you found a workaround by downgrading, ok.
Would be nice to know which version the issue was in and which version you last had it working in.

From the date of the issue, I guess your master branch version was b3cd107?
Which version did you downgrade to?

[Deantwo]

@BuilovAlexey, which version did you downgrade to?

[Deantwo]

I can get this to timeout on the current version, but I haven't a clue about how it SHOULD work or in which version it did work.

[Deantwo]

@BuilovAlexey, did you want to help solve this issue? At least tell us which version you downgraded to so we know when it broke?