get_cid_name.py might rely on timeout to terminate
Bug #1009072 reported by
daemon dog
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenERP-Asterisk360 Modules |
Incomplete
|
Undecided
|
Unassigned | ||
Bug Description
Whilst testing I noticed that get_cid_name.py may hang at the point reactor.run is called. I'm guessing its waiting for a response back or something to close the connection. This doesn't happen if I exclude the web socket connection at the end and use a different secondary lookup after the inital xmlrpc call (I was testing how to divert personal calls away from OpenERP). If a longer timeout than the default 1s is required this may not be ideal. If I get a chance I'll see if I can find out whats happening.
Revision history for this message
| ValdecDev (valdec-dev) wrote | #1 |
| Changed in openerp-asterisk360: | |
| status: | New → Incomplete |
To post a comment you must log in.
Do you have any further information on this one at all?