FOP2 with Yeastar S300

[buntaran]

Dial, Transfer, Pickup button not working with Yeastar S300.
Only **Hangup **button is working.

On Asterisk side (Yeastar S300) has configured on manager_custom.conf.
/etc/asterisk/manager_custom.conf
[fop2]
secret = fop222
deny = 0.0.0.0/0.0.0.0
permit = 127.0.0.1/255.255.255.0
read = all
write = all
writetimeout = 1000
eventfilter=!Event: RTCP*
eventfilter=!Event: VarSet
eventfilter=!Event: Cdr
eventfilter=!Event: DTMF
eventfilter=!Event: AGIExec
eventfilter=!Event: ExtensionStatus
eventfilter=!Event: ChannelUpdate
eventfilter=!Event: ChallengeSent
eventfilter=!Event: SuccessfulAuth
eventfilter=!Event: DeviceStateChange
eventfilter=!Event: RequestBadFormat
eventfilter=!Event: MusicOnHoldStart
eventfilter=!Event: MusicOnHoldStop
eventfilter=!Event: NewAccountCode
eventfilter=!Event: DeviceStateChange
But the 3 buttons still not functioning.

[nicolas]

Hi,
The only way to see what is happening is start FOP2 in full debug mode and inspect the output when you try those actions. Most probably the problem is permission related on the AMI side, or button misconfiguration in FOP2 side.

[buntaran]

Hi Nicolas,

As per attach is the full Debug from FOP2. Please have a look. Please let me know if we can resolve this issue. Thanks
Buntaran Lawrence

[nicolas]

Hi,
From your log it seems you have misconfigured buttons, although is hard to tell as you did not explain what action was performed in the FOP2 panel when you captured the log.

Be careful when posting this kind of log here, as it might contain sensitive information. In order to analyze better, I need to know about your FOP2 button configuration and what you did on FOP2 exactly.

I am online now at the live help if you want to chat.

Best regards,

[buntaran]

Hi Nicolas,

Thanks for the update. Please have a look at the buttons_custom.cfg file below.
We were using the dial, transfer action. and the logs was in FULL debug mode.

[PJSIP/10205]
type=extension
extension=10205
context=DLPN_DialPlan10205
label=Mr.Lai
mailbox=10205@default
extenvoicemail=*1002@from-internal
external=5551234@from-internal
privacy=clid
queuechannel=Local/1002@from-queue/n|Penalty=1|MemberName=Nicolas|StateInterface=SIP/620
customastdb=CF/1002
autoanswerheader=__SIPADDHEADER51=Call-Info=answer-after=0.001
originatevariables=FROM_USER=23,OTHER_VARIABLE=test

[PJSIP/1000]
type=extension
extension=1000
context=from-internal
label=RECEPTIONIST
mailbox=1000@default
extenvoicemail=*621@from-internal
external=5554444@from-internal
privacy=monitor
cssclass=someExtraCSSClass
customastdb=CF/621

[PJSIP/1003]
type=extension
extension=1003
context=from-internal
label=Mary
mailbox=1003@default
extenvoicemail=*621@from-internal
external=5554444@from-internal
privacy=monitor
cssclass=someExtraCSSClass
customastdb=CF/621

[PJSIP/1004]
type=extension
extension=1004
context=from-internal
label=Steve
mailbox=1004@default

[PJSIP/1005]
type=extension
extension=1005
context=from-internal
label=John
mailbox=1005@default

[PJSIP/1006]
type=extension
extension=1006
context=from-internal
label=Frank
mailbox=1006@default

[PJSIP/1007]
type=extension
extension=1007
context=from-internal
label=BOSS
mailbox=1007@default

[PJSIP/1008]
type=extension
extension=1008
context=from-internal
label=DAVID
mailbox=1008@default

[PJSIP/1009]
type=extension
extension=1009
context=from-internal
label=CHLOE
mailbox=1009@default

[SIP/622]
type=extension
extension=622
context=from-internal
label=John
mailbox=622@default
extenvoicemail=*622@from-internal
privacy=all
cssclass=someExtraCSSClass
tags=sales

[PJSIP/10203]
type=extension
extension=10203
context=DLPN_DialPlan10203
label=ABCDEQ
mailbox=10203@default
extenvoicemail=*623@from-internal
tags=sales

Thanks

Buntaran Lawrence

[nicolas]

How did you perform the dial action? Can you describe the actual mouse clicks and things done on FOP2? Could it be that you just clicked dial without anything else being done before? The dial action in FOP2 requires you first select a target extension to dial, was that done? What target extension did you select? Same for transfer, if you are on a call, then you must click the target and then you click the transfer button (not before).

Best regards,

[buntaran]

Yes, i chosen the target extension first before click "Dial" or "Transfer" button.
The extension is 10005 & 10205.
I will be online later 11PM - 3AM (GMT+8), maybe can we have a live chat or remote session?
Thanks
Buntaran Lawrence

[nicolas]

Writing here for future users running into issues, here is a correct button configuration for Yeastar S Series, that you must add in buttons_custom.cfg

[PJSIP/10001]
type=extension
extension=10001
context=DLPN_DialPlan10001
label=RECEPTIONIST 1
mailbox=10001@default
autoanswerheader=__SIPADDHEADER51=Call-Info=answer-after=0.001

[PJSIP/10002]
type=extension
extension=10002
context=DLPN_DialPlan10002
label=John Doe
mailbox=10002@default
autoanswerheader=__SIPADDHEADER51=Call-Info=answer-after=0.001

Also a reminder on FOP2 usage: to perform actions, you must log with a user (defined in the users section in the FOP2 Manager) that has a button visible with the same extension=x header in its config. Taking the above example, you can create users 10001 and 10002 and log as any of them. Then you will be able to perform actions from their respective device.

In this case, button config was incorrect, user attempted to log with user "100" and there was no device with such extensions, but it did have a queue configured with extension=100.. So action buttons appearead, but actions did not work, as it was not logged as a valid user.

In the next release I will add a script that will be available for now in the config_generatos directory that will connect to the yeastar box and generate the proper buttons_custom.cfg file in one swoop.

Best regards,