Re: Sent 18x with 'require:100rel' but no PRACK recieved
<[email protected]> Fri, 19 Aug 2011 15:42:42 +0530
| Newsgroups | gmane.ietf.sip |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format. --===============6634366669325947060== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CC5E59.27DCEDFF" This is a multi-part message in MIME format. ------_=_NextPart_001_01CC5E59.27DCEDFF Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi , =20 First of all , please use "sip-implementers ([email protected])" forum for the answer of this query.=20 =20 As per SIP RFC3262, you must reject the call in SIP side with 5xx ( provided you had SDP in reliable 18x ). You can reject ISUP side with a RELEASE message. =20 But if you want to relax your software compliance a bit here , you can do that, but remember your early media negotiation may be in trouble. If you are sure that on ISUP side the call is answered ( ANM is received ) you can proceed for sending 200 to SIP side. =20 Regards Honsha=20 =20 From: [email protected] [mailto:[email protected]] On Behalf Of etherchen Sent: Friday, August 19, 2011 8:48 AM To: sip Subject: [Sip] Sent 18x with 'require:100rel' but no PRACK recieved =20 Hi: =20 I'm facing a ISUP - SIP interworking issue recently. =20 =20 I receive INVITE from remote SIP server and send IAM to ISUP side, ISUP reply ACM/CPG and then I send 18x with 100rel out, but I did not receive any PRACK from remote SIP server, and I re-send 18x to them. During this period, ISUP side send ANM to me.=20 =20 If connect the call, but my end haven't receive PRACK yet, it become a unreliable call. If disconnect the call, I should not base on ANM to release a call. If continue 18x re-transmission untill time-out, it will have charging issue. Because ISUP side start billing base on ANM already, but my SIP side haven't start charging because not answer. =20 Thanks. ------_=_NextPart_001_01CC5E59.27DCEDFF Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <html xmlns:v=3D"urn:schemas-microsoft-com:vml" = xmlns:o=3D"urn:schemas-microsoft-com:office:office" = xmlns:w=3D"urn:schemas-microsoft-com:office:word" = xmlns:x=3D"urn:schemas-microsoft-com:office:excel" = xmlns:p=3D"urn:schemas-microsoft-com:office:powerpoint" = xmlns:a=3D"urn:schemas-microsoft-com:office:access" = xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" = xmlns:s=3D"uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" = xmlns:rs=3D"urn:schemas-microsoft-com:rowset" xmlns:z=3D"#RowsetSchema" = xmlns:b=3D"urn:schemas-microsoft-com:office:publisher" = xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadsheet" = xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" = xmlns:odc=3D"urn:schemas-microsoft-com:office:odc" = xmlns:oa=3D"urn:schemas-microsoft-com:office:activation" = xmlns:html=3D"http://www.w3.org/TR/REC-html40" = xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" = xmlns:rtc=3D"http://microsoft.com/officenet/conferencing" = xmlns:D=3D"DAV:" xmlns:Repl=3D"http://schemas.microsoft.com/repl/" = xmlns:mt=3D"http://schemas.microsoft.com/sharepoint/soap/meetings/" = xmlns:x2=3D"http://schemas.microsoft.com/office/excel/2003/xml" = xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" = xmlns:ois=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" = xmlns:dir=3D"http://schemas.microsoft.com/sharepoint/soap/directory/" = xmlns:ds=3D"http://www.w3.org/2000/09/xmldsig#" = xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint/dsp" = xmlns:udc=3D"http://schemas.microsoft.com/data/udc" = xmlns:xsd=3D"http://www.w3.org/2001/XMLSchema" = xmlns:sub=3D"http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/"= xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#" = xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" = xmlns:sps=3D"http://schemas.microsoft.com/sharepoint/soap/" = xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance" = xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/soap" = xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" = xmlns:udcp2p=3D"http://schemas.microsoft.com/data/udc/parttopart" = xmlns:wf=3D"http://schemas.microsoft.com/sharepoint/soap/workflow/" = xmlns:dsss=3D"http://schemas.microsoft.com/office/2006/digsig-setup" = xmlns:dssi=3D"http://schemas.microsoft.com/office/2006/digsig" = xmlns:mdssi=3D"http://schemas.openxmlformats.org/package/2006/digital-sig= nature" = xmlns:mver=3D"http://schemas.openxmlformats.org/markup-compatibility/2006= " xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" = xmlns:mrels=3D"http://schemas.openxmlformats.org/package/2006/relationshi= ps" xmlns:spwp=3D"http://microsoft.com/sharepoint/webpartpages" = xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/2006/types"= = xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/2006/messag= es" = xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/= " = xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortalServer/Pub= lishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" = xmlns:st=3D"" xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META = HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; = charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 12 = (filtered medium)"><style><!-- /* Font Definitions */ @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4;} @font-face {font-family:Tahoma; panose-1:2 11 6 4 3 5 4 4 2 4;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0in; margin-bottom:.0001pt; font-size:12.0pt; font-family:"Times New Roman","serif";} a:link, span.MsoHyperlink {mso-style-priority:99; color:blue; text-decoration:underline;} a:visited, span.MsoHyperlinkFollowed {mso-style-priority:99; color:purple; text-decoration:underline;} span.EmailStyle17 {mso-style-type:personal-reply; font-family:"Calibri","sans-serif"; color:#1F497D;} .MsoChpDefault {mso-style-type:export-only;} @page WordSection1 {size:8.5in 11.0in; margin:1.0in 1.0in 1.0in 1.0in;} div.WordSection1 {page:WordSection1;} --></style><!--[if gte mso 9]><xml> <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" /> </xml><![endif]--><!--[if gte mso 9]><xml> <o:shapelayout v:ext=3D"edit"> <o:idmap v:ext=3D"edit" data=3D"1" /> </o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue = vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span = style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497= D'>Hi ,<o:p></o:p></span></p><p class=3DMsoNormal><span = style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497= D'><o:p> </o:p></span></p><p class=3DMsoNormal><span = style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497= D'>First of all , please use "sip-implementers = ([email protected])" forum for the answer of this = query. <o:p></o:p></span></p><p class=3DMsoNormal><span = style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497= D'><o:p> </o:p></span></p><p class=3DMsoNormal><span = style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497= D'>As per SIP RFC3262, you must reject the call in SIP side with 5xx ( = provided you had SDP in reliable 18x ). You can reject ISUP side with a = RELEASE message.<o:p></o:p></span></p><p class=3DMsoNormal><span = style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497= D'><o:p> </o:p></span></p><p class=3DMsoNormal><span = style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497= D'>But if you want to relax your software compliance a bit here , you = can do that, but remember your early media negotiation may be in = trouble. If you are sure that on ISUP side the call is answered ( ANM is = received ) you can proceed for sending 200 to SIP = side.<o:p></o:p></span></p><p class=3DMsoNormal><span = style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497= D'><o:p> </o:p></span></p><p class=3DMsoNormal><span = style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497= D'>Regards<o:p></o:p></span></p><p class=3DMsoNormal><span = style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497= D'>Honsha <o:p></o:p></span></p><p class=3DMsoNormal><span = style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497= D'><o:p> </o:p></span></p><div = style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in = 0in 0in'><p class=3DMsoNormal><b><span = style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>= </b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> = [email protected] [mailto:[email protected]] <b>On Behalf Of = </b>etherchen<br><b>Sent:</b> Friday, August 19, 2011 8:48 = AM<br><b>To:</b> sip<br><b>Subject:</b> [Sip] Sent 18x with = 'require:100rel' but no PRACK recieved<o:p></o:p></span></p></div><p = class=3DMsoNormal><o:p> </o:p></p><div><p = class=3DMsoNormal>Hi:<o:p></o:p></p></div><div><p = class=3DMsoNormal> <o:p></o:p></p></div><div><p = class=3DMsoNormal> I'm facing a ISUP - SIP interworking issue = recently. <o:p></o:p></p></div><div><p = class=3DMsoNormal> <o:p></o:p></p></div><div><p = class=3DMsoNormal> I receive INVITE from remote SIP = server and send IAM to ISUP side, ISUP reply ACM/CPG and then = I send 18x with 100rel out, but I did not receive any = PRACK from remote SIP server, and I re-send 18x to them. = During this period, ISUP side send ANM to me. = <o:p></o:p></p></div><div><p = class=3DMsoNormal> <o:p></o:p></p></div><div><p = class=3DMsoNormal> If connect the call, but my = end haven't receive PRACK yet, it become a unreliable = call.<o:p></o:p></p></div><div><p class=3DMsoNormal> If disconnect = the call, I should not base on ANM to release a = call.<o:p></o:p></p></div><div><p class=3DMsoNormal> If continue = 18x re-transmission untill time-out, it will have charging issue. = Because ISUP side start billing base on ANM already, but my SIP side = haven't start charging because not answer.<o:p></o:p></p></div><div><p = class=3DMsoNormal> <o:p></o:p></p></div><div><p = class=3DMsoNormal> Thanks.<o:p></o:p></p></div></div></body></html> ------_=_NextPart_001_01CC5E59.27DCEDFF-- --===============6634366669325947060== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Sip mailing list https://www.ietf.org/mailman/listinfo/sip This list is essentially closed and only used for finishing old business. Use [email protected] for questions on how to develop a SIP implementation. Use [email protected] for new developments on the application of sip. Use [email protected] for issues related to maintenance of the core SIP specifications. --===============6634366669325947060==--