Cannot recieve calls or SMS after losing network coverage.

[Stunts]

After passing somewhere where I lose network coverage, I cannot receive any calls or SMS, even after the phone is reporting that network is now available again.
This does not happen every time, so I cannot describe steps to reproduce, but maybe I can post some log that will help me narrow it down.
The only way to receive calls or SMS again is to either reboot the phone or try to make a call. When I do this, the call takes quite a while to start (I have to wait about 20-30sec before I hear the calling signal).
Like I said, this does not happen every time I lose network coverage, but still happens quite frequently, and it is *really* annoying when it does as I become pretty much in-contactable while this lasts, even though the phone displays network signal.
I hope I was clear, but please request any more information if required.

Phone: BQ Aquaris E4.5
OS Version: 15.04 (r23) [Although the issue was present on previous versions as well]
Network provider: Uzo (uses MEO network)

[Tony Espy (awe)]

@Stunts

If you can reproduce again, there are a couple of things you could provide that would help us better understand the problem...

 * attach the file /var/log/syslog from the phone

 * paste the output of the following commands:

    - /usr/share/ofono/scripts/list-contexts

   - /usr/share/ofono/scripts/list-modems

[Stunts (f-pinamartins)]

@Tony Espy:
Thanks.
I will add that information to the notes on the phone and when it happens again I will get the logs and outputs and report them here.
Hopefully it will help narrow down the problem.

[eviweb (eviweb)]

Hi,
I've just linked this issue to this one : https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1588533
It seems they have similarities.

Eric

[Stunts (f-pinamartins)]

I have not been able to reproduce the issue in quite a while.
In fact, the last time this has happened must have been before I reported the bug.
At least from my part, I'd say this can be safely closed. If I am able to reproduce the issue I'll ask for the bug to be reopened.