Re: [Sip-implementors] Two provisional responses in one dialog: 180 Ringing and 183 Session Progress

2015-09-01 Thread Andrea Rizzi
al Message- From: Franz Edler [mailto:franz.ed...@kabsi.at] Sent: lunedì 31 agosto 2015 18:41 To: 'Paul Kyzivat'; sip-implementors@lists.cs.columbia.edu Subject: Re: [Sip-implementors] Two provisional responses in one dialog: 180 Ringing and 183 Session Progress Hi Paul, > I don&#

Re: [Sip-implementors] Two provisional responses in one dialog: 180 Ringing and 183 Session Progress

2015-08-31 Thread Franz Edler
Hi Paul, > I don't know ISUP, so I'll ask some followup questions. > > > we have a nasty situation in case of interworking SIP to ISUP. > > The INVITE request is mapped to ISUP/IAM, that's as expected. > > But then on the ISUP side we have a colored ringback tone service. > > This causes in an

Re: [Sip-implementors] Two provisional responses in one dialog: 180 Ringing and 183 Session Progress

2015-08-31 Thread Paul Kyzivat
On 8/31/15 12:41 PM, Franz Edler wrote: The 180 doesn't mean that you should generate ringback instead of playing in-band ringback. You should treat the 180 as meaning: generate ringback if you are not receiving in-band media. O.k. understood, but the " ... if you are not receiving in-band med

Re: [Sip-implementors] Two provisional responses in one dialog: 180 Ringing and 183 Session Progress

2015-08-31 Thread Paul Kyzivat
On 8/30/15 3:18 PM, Franz Edler wrote: Dear SIP-ISUP experts, I don't know ISUP, so I'll ask some followup questions. we have a nasty situation in case of interworking SIP to ISUP. The INVITE request is mapped to ISUP/IAM, that's as expected. But then on the ISUP side we have a colored ringb

[Sip-implementors] Two provisional responses in one dialog: 180 Ringing and 183 Session Progress

2015-08-30 Thread Franz Edler
Dear SIP-ISUP experts, we have a nasty situation in case of interworking SIP to ISUP. The INVITE request is mapped to ISUP/IAM, that's as expected. But then on the ISUP side we have a colored ringback tone service. This causes in an ISUP ACM message with both flags set: - Backward Call Indicator: