Update:

This seem to happen only the first time mod_python is invoked and session object is used, no mater the script.The other python scripts will work after one (anyone) is used.
As said before, after session object is accessed once, after a restart (giving back the error), everything starts working again.

Looking forward to hear from you.

Best Regards,

--

Nuno Miguel Reis | Unified Communication Systems
M. +351 913907481 | nreis@wavecom.pt

WAVECOM-Soluções Rádio, S.A.
Cacia Park | Rua do Progresso, Lote 15

3800-639 AVEIRO | Portugal

T. +351 309 700 225 | F. +351 234 919 191

GPS | www.wavecom.pt

Description: Description: WavecomSignature

Publicity




On Mon, Aug 18, 2014 at 7:12 AM, Nuno Reis <nreis@wavecom.pt> wrote:
Hi guys.

I'm experiencing a weird behavior with the new FS 1.4. Everytime i call a python script in the dialplan after a reboot i always got an error similar to this:

2014-08-18 07:03:26.341145 [ERR] mod_python.c:293 Error calling python script
2014-08-18 07:03:26.341145 [ERR] mod_python.c:164 Python Error by calling script "stable.disa": <type 'exceptions.AttributeError'>
Message: 'PySwigObject' object has no attribute 'sleep'

This only happens with the first call after a restart. After that everything works fine.
I never saw this in FS 1.2

Any ideas on why?
Thanks.

Note: I'm using FS Version 1.4.8  64bit

Cheers,

--

Nuno Miguel Reis | Unified Communication Systems
M. +351 913907481 | nreis@wavecom.pt

WAVECOM-Soluções Rádio, S.A.
Cacia Park | Rua do Progresso, Lote 15

3800-639 AVEIRO | Portugal

T. +351 309 700 225 | F. +351 234 919 191

GPS | www.wavecom.pt

Description: Description: WavecomSignature

Publicity