<div>Cause i = 0x80E018 - Mandatory information element missing </div>
<div>Cause i = 0x80E27D - Message not compatible with call state or not implemented </div><div>Cause i = 0x82E5 - Message not compatible with call state<br><br>Those messages indicate to me that you're sending q931 messages that the far end switch doesn't like, or that youre getting messages that you don't like. A sure fire indication at the far end isdn switch type is not configured the same as your local isdn switch type.<br>
<br>If you're set to primary-qsig, are you positive that your provider is also set to primary-qsig?<br><br>This may not be causing the problem you reported below, but I can only fix the problems I see error messages for, and those errors tell me your switch type is mismatched.<br>
<br>For the problem with the call disconnect it would be helpful to get relevant debugs (SIP, Q931) from each device involved.<br></div><br><br><div class="gmail_quote">On Fri, Jun 5, 2009 at 5:47 AM, Ratko Dodevski <span dir="ltr"><<a href="mailto:rade239@gmail.com">rade239@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Thanks for replying,<br>PRI switch-type is set as primary-qsig. I should mention that when i make phone calls to PSTN or GSM network trough the IPPBX it works just fine, but i can't make calls with phones that are registerd with the IPPBX (which i think is some Israelian AIRSPAN). <br>
<br><br>Ratko<div><div></div><div class="h5"><br><br><div class="gmail_quote">On Fri, Jun 5, 2009 at 4:58 AM, Jason Burns <span dir="ltr"><<a href="mailto:burns.jason@gmail.com" target="_blank">burns.jason@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
It sounds like your PRI Switch Type is set incorrectly based on the type of q931 errors you're getting. Is it NI2, 5ESS, DMS100?<br><br><div class="gmail_quote"><div><div></div><div>On Thu, Jun 4, 2009 at 6:30 PM, Ratko Dodevski <span dir="ltr"><<a href="mailto:rade239@gmail.com" target="_blank">rade239@gmail.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><div></div><div>Hi, i have question (obviously :) ) <br clear="all">
<div>I have big troubles connecting a TDM PBX to a IPPBX through SBC via SIP. When I do <i>debug isdn q931 </i>I keep getting this massages:</div>
<div>Cause i = 0x80E018 - Mandatory information element missing </div>
<div>Cause i = 0x80E27D - Message not compatible with call state or not implemented </div><div>Cause i = 0x82E5 - Message not compatible with call state</div><div><br></div><div>Called number is ringing but when i pick-up it gives me busy dial and if i hung-up it rings again. On the SBC I can see that after picking router sends BYE signal with "Bearer capability not implemented" and instantly sending 2 more invites for call. </div>
<div>I tried with setting bearer-cap Speech and i use the command isdn incoming-voice voice.</div><div><br></div><div>Tried many combinations... Any ideas ????</div><div><br></div><div>Thanks <br></div>-- <br><font color="#888888">Ratko<br>
</font><br></div></div>_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br></blockquote></div><br>
</blockquote></div><br><br clear="all"><br></div></div>-- <br><font color="#888888">Ratko<br>
</font></blockquote></div><br>