Summary:ASTERISK-13874: 183 response although progressinband=never when routed to PRI
Reporter:Martin Vit (festr)Labels:
Date Opened:2009-04-01 02:27:56Date Closed:2011-06-07 14:07:58
Versions:Frequency of
Description:hi, I've a similiar problem as bug ASTERISK-12346

Incoming call - SIP/SDP Request: INVITE sip:xx@yy, with session description and asterisk responds with 183 with SDP although there is progressinabnd=never

This call (INVITE) is routed to Zap/g1 PRI euroISDN

on pri debug:
Message type: CALL PROCEEDING (2)
(after 2 seconds)
Message type: ALERTING (1)

after received ALERTING, asterisk sends 180 RING but asterisk is not generating alert inside RTP SDP although it sends RTP (with silence) so the far end is not generating alert although 180 RING was sended by us. Thats because right after INVITE asterisk sended early 183 with SDP and RFC says that if we are sending 183 with SDP, far and is not generating RING.

I'm not sure that i've explain it clear. If any question, logs or so, tell me.

(I've made small hacks inside channel_sip.c to not send 183 with SDP in any situation) and it works for me in this installation. But it should be fixed somehow.

and the question - asterisk does not can generate its own alert (tones) when ALERT without PROGRESS INBAND is received on the PRI?


More detailed debug on PRI

Progress does not contain PROGRESS IE

CLI> pri debug span 1

   -- Called g1/xxxx
< Protocol Discriminator: Q.931 (8) len=5
< Call Ref: len= 2 (reference 2/0x2) (Terminator)
< Message type: CALL PROCEEDING (2)
q931.c:3683 q931_receive: call 32770 on channel 1 enters state 3 (Outgoing call Proceeding)
[Mar 29 17:58:28] DEBUG[16573]: chan_dahdi.c:9576 pri_dchannel: Queuing frame from PRI_EVENT_PROCEEDING on channel 0/1 span 1
   -- Zap/1-1 is proceeding passing it to SIP/xxx-yyy

< Protocol Discriminator: Q.931 (8) len=5
< Call Ref: len= 2 (reference 2/0x2) (Terminator)
< Message type: ALERTING (1)
q931.c:3596 q931_receive: call 32770 on channel 1 enters state 4 (Call Delivered)
[Mar 29 17:58:34] DEBUG[16573]: chan_dahdi.c:1780 dahdi_enable_ec: Enabled echo cancellation on channel 1
   -- Zap/1-1 is ringing
Comments:By: Leif Madsen (lmadsen) 2009-07-13 10:41:12

Is this still an issue?

By: Olle Johansson (oej) 2009-09-10 14:20:22

Can you still try with the latest version of 1.4 in SVN. I just committed some fixes related to these issues. Check the prematuremedia option in sip.conf,sample - where you can turn off the ghost 183's.

THanks for testing this!

By: Leif Madsen (lmadsen) 2009-09-30 09:43:45

I'm closing this issue as it has been waiting on feedback for more than 2 weeks. If the reporter has additional information that can be submitted, than they are welcome to reopen the issue. Thanks!