Problem with elastix Call Center

[asterisk]

Hi all,
I have a problem using the elastix outgoing call-center in particular I view in the console the agent login elapsed time but when I make the call there is not in the fop2 console the called number.
Someone can help me to resolve the problem ?

Thank you in advance.

Bye

[nicolas]

I think I once patched the elastix dialer so the number was shown, but I really do not remember what I did. But I do know it was a patch in elastix dialer, not in fop2 (to setup the callerid most probably when doing the call origination).

[asterisk]

Hi, thank you for the help, i finally patched the elastix call center to set correct callerid as you suggested, but I have another question: at the end of the call the called number persist, the line won't become Inactive what can be the problem ?

Bye

[nicolas]

Most probably there is a missing event in AMI. How did you patch the elastix dialer? Can you post your modifications? Perhaps the patch is creating the problem somehow?

[asterisk]

I don't think the patch have created the problem I only modified the Originate call in Dialerprocess.class.php setting the called number as callerid:
It was:
$resultado = $this->_astConn->Originate(
$sCanalTrunk, $infoCampania->queue, $infoCampania->context, 1,
NULL, NULL, NULL,
(isset($datosTrunk['CID']) ? $datosTrunk['CID'] : NULL),
$sCadenaVar,
NULL,
TRUE, $sKey);

became:
$resultado = $this->_astConn->Originate(
$sCanalTrunk, $infoCampania->queue, $infoCampania->context, 1,
NULL, NULL, NULL,$tupla->phone,
$sCadenaVar,
NULL,
TRUE, $sKey);

[nicolas]

What fop2 version do you have ?

/usr/local/fop2/fop2_server -v

[asterisk]

I have the 2.25

bye

[nicolas]

Do you have "all" in /etc/asterisk/manager.conf read/write lines ?

[asterisk]

I setup all for read and write to all in manager.conf without success.
Below the AMI events for hangup:

Event: Newexten
Privilege: dialplan,all
Channel: SIP/05832585252-00000023
Context: appoggiocc
Extension: h
Priority: 1
Application: Hangup
AppData:
Uniqueid: 1343571184.47

Event: MusicOnHold
Privilege: call,all
State: Start
Channel: SIP/41-00000021
UniqueID: 1343556484.44
Class: default

Event: Hangup
Privilege: call,all
Channel: Agent/2001
Uniqueid: 1343571184.48
CallerIDNum: 05832585252
CallerIDName: <unknown>
ConnectedLineNum: 3332528989
ConnectedLineName: <unknown>
Cause: 0
Cause-txt: Unknown

Event: VarSet
Privilege: dialplan,all
Channel: SIP/05832585252-00000023
Variable: RTPAUDIOQOS
Value: ssrc=272022469;themssrc=1968036758;lp=0;rxjitter=0.000389;rxcount=1849;txjitter=0.000000;txcount=1828;rlp=0;rtt=0.000000
Uniqueid: 1343571184.47

Event: VarSet
Privilege: dialplan,all
Channel: SIP/05832585252-00000023
Variable: RTPAUDIOQOSJITTER
Value: minrxjitter=0.000000;maxrxjitter=0.000000;avgrxjitter=0.000000;stdevrxjitter=0.000000;reported_minjitter=0.000000;reported_maxjitter=0.000000;reported_avgjitter=0.000000;reported_stdevjitter=0.000000;
Uniqueid: 1343571184.47

Event: VarSet
Privilege: dialplan,all
Channel: SIP/05832585252-00000023
Variable: RTPAUDIOQOSLOSS
Value: minrxlost=0.000000;maxrxlost=0.000000;avgrxlost=0.000000;stdevrxlost=0.000000;reported_minlost=0.000000;reported_maxlost=0.000000;reported_avglost=0.000000;reported_stdevlost=0.000000;
Uniqueid: 1343571184.47

Event: VarSet
Privilege: dialplan,all
Channel: SIP/05832585252-00000023
Variable: RTPAUDIOQOSRTT
Value: minrtt=0.000000;maxrtt=0.000000;avgrtt=0.000000;stdevrtt=0.000000;
Uniqueid: 1343571184.47

Event: VarSet
Privilege: dialplan,all
Channel: SIP/05832585252-00000023
Variable: RTPAUDIOQOS
Value: ssrc=272022469;themssrc=1968036758;lp=0;rxjitter=0.000389;rxcount=1849;txjitter=0.000000;txcount=1828;rlp=0;rtt=0.000000
Uniqueid: 1343571184.47

Event: Hangup
Privilege: call,all
Channel: SIP/05832585252-00000023
Uniqueid: 1343571184.47
CallerIDNum: 3332528989
CallerIDName: <unknown>
ConnectedLineNum: 05832585252
ConnectedLineName: <unknown>
Cause: 16
Cause-txt: Normal Clearing

[nicolas]

As you are using chan agent, the best config possible for FOP2 would be to use Agent/xxxx for the button configuration. But you will have to do that manually. You could try to do that, at least with a couple of agents and see if you experience the same issue or not. Agent/Agentlogin are better tracked with Agent/xxx buttons, although normal device buttons should work also with no issues.