# adl\_callSetup and call handler and no SIM

**URL:** <https://forum.sierrawireless.com/t/adl-callsetup-and-call-handler-and-no-sim/1642>\
**Category:** Open AT\
**Created:** [October 11, 2007, 5:59am UTC](https://forum.sierrawireless.com/t/adl-callsetup-and-call-handler-and-no-sim/1642 "2007-10-11T05:59:38Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![JoParker](https://avatars.discourse-cdn.com/v4/letter/j/ac91a4/32.png) [@JoParker](https://forum.sierrawireless.com/u/JoParker)\
**Post date:** [October 11, 2007, 5:59am UTC](https://forum.sierrawireless.com/t/adl-callsetup-and-call-handler-and-no-sim/1642/1 "2007-10-11T05:59:38Z")

</div>

Has anybody else had trouble with adl\_callSetup not resulting in a SIM error in the absence of a SIM card?

I am having difficulties with the call handler and adl\_callSetup. I subscribe to the call handler on initialisation, then sometime during my program I call adl\_callSetup with an ordinary phone number. If there is no SIM card inserted, the handler never receives any events and my call is lost (even though adl\_callSetup returns OK). I would expect the handler to receive ADL\_CALL\_EVENT\_SETUP\_ERROR\_NO\_SIM.

Does this mean I should not assume that the handler will always capture an event after I call adl\_callSetup? Even when adl\_callSetup returns OK?

Should I be checking for things like SIM presence and network registration before using adl\_callSetup? I would have expected the call handler to provide me with this information after I try to make a call.

Thanks

---

<div class="post-metadata">

**Author:** ![awneil](https://avatars.discourse-cdn.com/v4/letter/a/49beb7/32.png) [@awneil](https://forum.sierrawireless.com/u/awneil)\
**Post date:** [October 11, 2007, 6:44am UTC](https://forum.sierrawireless.com/t/adl-callsetup-and-call-handler-and-no-sim/1642/2 "2007-10-11T06:44:53Z")

</div>

What firmware version do you have?  
What Open-AT version are you using?

> [@JoParker](#):
>
> Has anybody else had trouble with adl\_callSetup not resulting in a SIM error in the absence of a SIM card?

I haven’t come across this one, but I have seen another anomoly (or was it anomolies?) in call events - see: [wavecom.com/modules/movie/sc … ight=event](http://www.wavecom.com/modules/movie/scenes/forums/viewtopic.php?t=709&highlight=event)

> [@](#):
>
> Does this mean I should not assume that the handler will always capture an event after I call adl\_callSetup? Even when adl\_callSetup returns OK?

It does seem that you need to provide your own timeouts and/or other means to ensure that you can never get stuck in an “unexpected” state… 😢

> [@](#):
>
> I would have expected the call handler to provide me with this information after I try to make a call.

As I noted in that other thread, the v3.03 documentation was very poor on what exactly you should (and should not) expect from the various events. 😢

The latest version (v4.20) has not improved. 😠

---

<div class="post-metadata">

**Author:** ![JoParker](https://avatars.discourse-cdn.com/v4/letter/j/ac91a4/32.png) [@JoParker](https://forum.sierrawireless.com/u/JoParker)\
**Post date:** [October 11, 2007, 10:57pm UTC](https://forum.sierrawireless.com/t/adl-callsetup-and-call-handler-and-no-sim/1642/3 "2007-10-11T22:57:27Z")

</div>

Firmware version 662  
Open-AT version 4.20

Agreed about the documentation on call events – very minimal.

It might be worth noting that I get the same result whether running in RTE or target mode. When the SIM card is in it all works nicely.

Sounds like a more sophisticated method for governing calls is in order…

Thanks.