Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Freeswitch 8.0 #59

Closed
wants to merge 12 commits into from
Closed

Freeswitch 8.0 #59

wants to merge 12 commits into from

Conversation

treveradams
Copy link

This is 8.0 with freeswitch_click2dial and freeswitch_click2dial_crm. These are not tested. I do not have an Odoo 8.0 install. I have matched the changes to the rest of the code, so they should work.

@treveradams treveradams force-pushed the freeswitch-8.0 branch 5 times, most recently from 4bb6550 to f292430 Compare September 30, 2015 13:58
@treveradams
Copy link
Author

The remaining errors seem to be some formatting complaints, the fact that ESL module is only available if you build it as part of a FreeSWITCH installation, and complaining that geocoder isn't used when it is. Except for:

freeswitch_click2dial/freeswitch_click2dial.py:227:22: E901 SyntaxError: invalid syntax

This same line exists in the 7.0 version and doesn't give an error. I am not sure what is wrong and would appreciate any help in fixing it.

@treveradams
Copy link
Author

The import but not used in the integration tests is not accurate. Import not at top of file is either because it is below a the start of file comment block, or in one case, is an optimization for the common case.

@treveradams
Copy link
Author

The complaint about the really long line is about a comment where I thought the line should remain as is.

@blessendor
Copy link

Thanks to Trevor's quick responses and fixes, I have working integrated FreeSWITCH (with FusionPBX configurator) and OpenERP/odoo 8 as platform of my web site and CRM system.

@treveradams
Copy link
Author

Alex, thank you so much for your help in tracking down the problems you found. Hopefully this is now useful to many more people and is more flexible in the environments it will work in.

@lattoh
Copy link

lattoh commented Sep 2, 2017

Hello,
I have Grandstream IPPBX 6202, and would like to know if this connecteur can work with.

Thanks and regards

@treveradams
Copy link
Author

@lattoh, it works with FreeSWITCH. Any sip, verto (with some extensions), etc. end points/clients should work. If not, please let me know.

Formatting fixups.
Add FreeSWITCH ESL Python module to travis config.
* FreeSWITCH channel types better defined.
* Better demo data.
…act ${dialed_user}@${dialed_domain}} to the default dial string for the directory the user is in).

* Further move things from Asterisk to FreeSWITCH in code, documentation, etc.
* Remove import of sys.
* Clean up code.
* Allow suppression of debugging output.
* Better follow coding style guidelines.
* Fix originate to handle Unicode via UTF-8.
* Fix Open Caller to handle more situations and channel types.
* get_caller_name.py and pop-up functionality now handle invalid numbers properly.
* Fix test connection.
@treveradams treveradams force-pushed the freeswitch-8.0 branch 3 times, most recently from ff75ea9 to 0395f89 Compare September 3, 2017 01:48
Cleanup file copyrights as suggested by Eric Caudal.
get_caller_name.py should handle Unicode results properly.
@lattoh
Copy link

lattoh commented Sep 3, 2017

Hello,

Ok, I install telephony connector on Odoo 8 on Ubuntu server16.04 LTS.

I have Grandstream IPPBX UCM 6202 base on Asterisk and some ipphone Grandstream on my network.

But only call from dial buttom on partner form work, other function such as showing name of partner on my ipphone and opening partner form do not work.

Please can you help me for that ??

Thanks and regards,

@lattoh
Copy link

lattoh commented Sep 3, 2017

Juste to tell you that I have AMI 2.7.0 on my IPPBX UCM 6202, and I do not know if my problem come from version of AMI.

Thanks

@github-actions
Copy link

github-actions bot commented Dec 5, 2021

There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this PR to never become stale, please ask a PSC member to apply the "no stale" label.

@github-actions github-actions bot added the stale PR/Issue without recent activity, it'll be soon closed automatically. label Dec 5, 2021
@github-actions github-actions bot closed this Jan 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale PR/Issue without recent activity, it'll be soon closed automatically.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants