The BYE message should include an ISUP REL message, and the BYE should receive a 200 OK response with an ISUP RLC message.
That said; I know certain vendors don't generate all of the standard ISUP messages, even though they say they are following the SIP-I/SIP-T standards. Metaswitch is notorious for only sending the IAM in the INVITE, and doesn't give any other ISUP message bodies through the progression of the dialog. YMMV :) Joel Gerber Eastlink -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Paul Kyzivat Sent: December-13-12 3:04 PM To: [email protected] Subject: Re: [Sip-implementors] Content header : application/isup On 12/13/12 2:02 PM, Vivek Singla wrote: > Hi, > I have a call flow where the Invite is sent using content header : > application/isup. > In the message body IAM is present. > I get back 180 ringing, 183 call progress and also 200ok with the ISUP > messages in the message body. > > But when I get the BYE, this BYE does not have the ISUP message body. > This message does not have any content header. > > My server discards this BYE message. > > Is that ok? No, it is not ok to discard the BYE message, assuming it is otherwise correctly formed. Regardless of the presence or absence of the ISUP body it still terminates the dialog. If you discard it then you will be maintaining the dialog when the other end thinks it is gone. I'm not knowledgeable about the isup extensions. So I don't know if something bad has been done by not including an ISUP body in the BYE. But in any case you should take appropriate action to end the ISUP connection, because there is no longer any SIP connection. Thanks, Paul _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
