search

faucamp / python-gsmmodem

Python module to control a GSM modem attached to the system: send/receive SMS messages, handle calls, etc
GNU Lesser General Public License v3.0
384 stars 302 forks source link

CLIP identification fails with higher baud rates #64

Open vaclavstepan opened 8 years ago

vaclavstepan commented 8 years ago

I'd appreciate any help how to deal with the following issue: I've a CLIP capable modem, I'm trying to setup a SMS response on call script.

When connected at baudrate 9600, incomming call leads to:

 notification: ['+CRING: VOICE', '+CLIP: "+420123456789",145,,,,0']

This is then correctly handled (the CLIP is matched).

However, on higher baud rates, an incoming call results in two separate notifications, one for the call, one for the CLIP. This is however handled wrongly - the CLIP never gets matched to the call.

2015-11-29 13:23:29,354 [DEBUG] (Thread-3  ) notification: ['+CRING: VOICE']
2015-11-29 13:23:29,354 [DEBUG] (Thread-4  ) Handling incoming call
2015-11-29 13:23:29,355 [INFO] (Thread-4  ) New incoming call, waiting for CLIP.
2015-11-29 13:23:29,359 [DEBUG] (Thread-3  ) notification: ['+CLIP: "+420123456789",145,,,,0']
2015-11-29 13:23:29,360 [DEBUG] (Thread-5  ) Unhandled unsolicited modem notification: ['+CLIP: "+420777642401",145,,,,0']

Any idea how to proceed on this, please?

morettigiorgio commented 4 years ago

I too have a similar problem. My baudrate is always at 9600 but in my case, ['+CRING: VOICE'] and ['+CLIP: "+xxxxxxxxxx",145,"",128,"",0'] are always in separate lines and a "Unhandled unsolicited modem notification" is raise. The result is that nothing number puts in call callback

Any idea?