asterisk users - Jul 2004 - Indications missing on Cisco FXO -> ATA-186 (SIP)

Calling from a Cisco FXO port to an ATA-186 (SIP 3.1 image) via * 
(either CVS-HEAD-06/28/04-11:43:41 or CVS-HEAD-07/12/04-15:49:58)
I didn't hear any ringing sound & get the following on the console:

-- Called 5503
-- SIP/5503-f6b5 is ringing
WARNING[-1323201616]: channel.c:1375 ast_indicate: Unable to handle 
indication 3 for 'SIP/10.10.2.250-9903'
-- SIP/5503-f6b5 answered SIP/10.10.2.250-9903

Looking at channel.c, I can see that this means that 'condition' is 
neither of 'AST_CONTROL_PROGRESS' or 'AST_CONTROL_PROCEEDING'.
Presumably it's 'AST_CONTROL_RINGING', so why is this not handled?

(NB Calls go through fine - all ulaw currently)

Thanks a lot,
Fran.

> Calling from a Cisco FXO port to an ATA-186 (SIP 3.1 image) via * 
> (either CVS-HEAD-06/28/04-11:43:41 or CVS-HEAD-07/12/04-15:49:58)
> I didn't hear any ringing sound & get the following on the console:
> 
> -- Called 5503
> -- SIP/5503-f6b5 is ringing
> WARNING[-1323201616]: channel.c:1375 ast_indicate: Unable to handle 
> indication 3 for 'SIP/10.10.2.250-9903'
> -- SIP/5503-f6b5 answered SIP/10.10.2.250-9903
> 
> Looking at channel.c, I can see that this means that 'condition' is
> neither of 'AST_CONTROL_PROGRESS' or
'AST_CONTROL_PROCEEDING'.
> Presumably it's 'AST_CONTROL_RINGING', so why is this not
handled?
> 
> (NB Calls go through fine - all ulaw currently)
Someone else just had that same problem in the last day or two.
I don't have their response, but it had something to do with setting
the Audiomode to different value to take advantage of a codec or
something to that effect. Search the archives...

Fran Boon wrote:
> Calling from a Cisco FXO port to an ATA-186 (SIP 3.1 image) via * 
> (either CVS-HEAD-06/28/04-11:43:41 or CVS-HEAD-07/12/04-15:49:58)
> I didn't hear any ringing sound & get the following on the console:
> -- Called 5503
> -- SIP/5503-f6b5 is ringing
> WARNING[-1323201616]: channel.c:1375 ast_indicate: Unable to handle 
> indication 3 for 'SIP/10.10.2.250-9903'
> -- SIP/5503-f6b5 answered SIP/10.10.2.250-9903
> Looking at channel.c, I can see that this means that 'condition' is
> neither of 'AST_CONTROL_PROGRESS' or
'AST_CONTROL_PROCEEDING'.
> Presumably it's 'AST_CONTROL_RINGING', so why is this not
handled?
> (NB Calls go through fine - all ulaw currently)
Further to this, I have done more digging - it's not related to the ATA 
at all, but is due to the Cisco FXO port.
(Calls to ATA from Firefly/IAX work fine, Calls from FXO to Firefly/IAX 
give this same error)

I have looked at Cisco's docs & they talk about using progress_ind to 
tune which IE is sent, but this only works for H.323, not SIP:
http://cisco.com/en/US/products/sw/iosswrel/ps1839/products_command_reference_chapter09186a00800b350f.html#999970

Anyone using Cisco FXO ports & SIP with * & getting indications?
Anyone using H.323 & having better luck? (If so, chan_h323 or chan_oh323?)

It looks to me like a bug in * as to why this IE isn't being handled, 
but I could be wrong.

Comments welcome :)

F