Summary:ASTERISK-05925: [patch] don't send 180 and 183 together when progressinband=yes
Reporter:adomjan (adomjan)Labels:
Date Opened:2005-12-29 07:40:22.000-0600Date Closed:2006-02-13 16:59:31.000-0600
Versions:Frequency of
Environment:Attachments:( 0) no-180-183.patch
Description:I had problems with Thomson THG520 SIP MTA, when asterisk sent 180 Ringing and 183 Session Progress togheter.
Asterisk had sent 180 ringing first.
Asterisk sent 183 when got inband progress indication from pstn.
The mta started to generate own ringing tone after the 180.
When mta got 183, it mixed it the previusly started ringing tone.

I think should't use the 180 and 183 together.

I'm not sure my patch is the perfect solution, but works for me...
Comments:By: Matt O'Gorman (mogorman) 2006-01-11 17:56:28.000-0600

can some sip expert declare if this is really a bug or not... oej im looking at you.

By: Russell Bryant (russell) 2006-01-12 10:26:01.000-0600

from the discussion in ASTERISK-3071 ...


When "RING" event is requested, always send 180 Ringing (if it hasn't been sent yet) followed by 183 and in-band audio


Send "180 Ringing" if 183 has not yet been sent establishing audio path. If audio path *is* established already (with 183) then send in-band ringing (this is the way asterisk historically behaved because of buggy phones like polycom)


Whenever ringing occurs, send "180 ringing" as long as "200 OK" has not yet been sent.

It appears you should not have progressinband turned on.  Please set this to "never" and you will probably get the behavior that you want.

By: Russell Bryant (russell) 2006-01-12 10:29:12.000-0600

Note that inband progress is not usually desired, because it requires extra Asterisk resources to run a generator to generate the inband ringing.  If the endpoint is generating its own, then there is no need to tell Asterisk to do it.

By: adomjan (adomjan) 2006-01-12 10:44:58.000-0600

When I get inband progress from pstn have to forward to ata.
I'm in Hungary, lot of ata can generate us ringing tone only.
It's a workaround...

By: Kevin P. Fleming (kpfleming) 2006-02-13 16:59:31.000-0600

This is bug in your ATA. When we send 183, that means 'inband progress' is available. That does _not_ necessarily mean that it is ringing, it could be any sort of progress tone, or even audio from an IVR. If your ATA does not stop its own ringing generator and start forwarding the audio, it is broken.