FOP2 Community Forum

I am not using the kannel, but now there is the best service of sending the bulk of SMS through SMPP

Hello again, Thanks for your answer. It turns out it was a permission issue as suspected. After granting the fop2 user access to the asteriskcdrdb database with the following command: GRANT ALL PRIVILEGES ON asteriskcdrdb.* to fop2@'localhost' identified by 'password'; it now works perfectly! Best regards, Carlos

There is nothing impossible in this world ! I did it with some asterisk routing manipulating. If we can't filter traffic we must create trunk only for proper user. So i created SIP/trunk_user1 duplicated SIP/trunk_1, created user1 context in asterisk with outgoing rule routing to this new trunk_user1. After we have to add channel=SIP/trunk_user1 in extension button and... we can monitor and record remote users on the other PBX ! P.S. I still think it's possible to filter trunk channels by called numbers. We have field 'extension' in AMI channel definition, so we can announce this variable and have something like Channel=SIP/trunkxxx&exten=xxx or Channel=SIP/trunkxxx||yyy where yyy dialed extension. P.P.S. I noticed that only one extension in all buttons can display channel=SIP/trunk_1 information. i want to say If we add record channel=SIP/trunk_1 to SIP/user1 and to SIP/user2 extensions in button.cfg file than only one extension will show status of trunk_1. Is there a possibility to see status on both extensions ? Best regards, Sergio.

broadcast It is not a group chat, but broadcasting individual chats to a group.

Thnks for live help proposal, but it's a little bit difficult because of time zone difference - when you're up, It's a night in Moscow and viceversa ! On the current moment i solved my problem by migrating to Linux SuSe 11.4 and FOP works well with it. The last post just FYI and for some other SuSe based Linux users. Best regards, Sergio.

Fixing the group names broke the group chat, it is fixed now. thanks for the feedback.

Thanks for the feedback, I understand your need, and you have fixed it already to suit you. Anyways, I think that in regular cases, the "admin" user should be limited by panel context, as the panel context is thought to be used in multi tenant setups, and the admin granting access to other contexts is indeed a bug/problem. Be sure you backup your recordings.php file so it does not get overwritten if you upgrade fop2 in the future! Best regards,

Edit /var/www/html/fop2/js/presence.js and set var noExtenInLabel = true;