Here's an interesting issue I ran into with an FXO card (an X100P clone by Diginetworks; it claims to be an X101P, but whatever), where it was giving me a silly complaint:
ozmod_analog.c: 761 process_event() Why bother changing state on 1:1 from UP to UP
It turns out that this warning was actually a consequence of the codepath that was being traversed when an FXS interface was getting a RING_START event. See, FXS interfaces (the interfaces that a telco has connected towards your house) are never supposed to get rings, since FXO interfaces (the interfaces that your phones have connected towards the telco) are never supposed to send rings. (When you call somebody, the telco's FXS interface to the other guy rings towards his phone's FXO interface, so his phone beeps at him. However, your phone never sends a ring to the telco. The telco automatically answers the line (with a long "beeeeeeeeeeeeeeeeeeeep") as soon as you pick up the phone.)
Anthony added another error now, to make things a bit clearer:
ozmod_analog.c:723 process_event() Cannot get a RING_START event on a non-fxo channel, please check your config.
The solution is to go into your openzap.conf file, and fix the fxs-channel into an fxo-channel:
[span zt] name => OpenZAP number => 1 fxo-channel => 1
Please note that this is only for FreeSWITCH, not Asterisk, and not the ZapTel driver itself. (The latter two still require you to say fxs, since your FXO card is listening for FXS signalling. On the other hand, FreeSWITCH tries to "unconfuse" you by having you specify fxo if you're using an FXO card.) Here's /etc/zaptel.conf, for example:
fxsks=1 loadzone=us defaultzone=us
I hope this helps you to avoid a long trip to #openzap ;-)