2006/5/3, Marco Mouta <<a href="mailto:marco.mouta@gmail.com">marco.mouta@gmail.com</a>>:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div style="direction: ltr;"><a href="http://www.voip-info.org/wiki-Asterisk+config+zapata.conf" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://www.voip-info.org/wiki-Asterisk+config+zapata.conf
</a><br><br>I've made some tests using this in Portugal and seems to work:<br><br>-------------------------------------------------------------------------------
<br>switchtype=qsig ; you may try this in your zapata.conf<br>------------------------------------------------------------------------------<br><br>I suppose you are using PRI access.<br><br>But i've also red that qsig is not fully compliant in Asterisk. I've found some PRI states not recognized in asterisk sending CAUSECODE=98 to my legaccy PBX when it seems to me that Asterisk should handle it...
<br><br>Any ways it seems to work in a standardt architecture:<br>PSTN--E1---LegacyPBX---QSIG---Asterisk<br><br><br>I hope it helps,<br><br><br>Marco Mouta<br><br></div></blockquote></div>For curiosity, what sort of benefit were you after using QSIG ?
<br>Most vendors tout SIP as interoperability protocol.<br>Did you use QSIG as a way, for instance, to provide Message Waiting Indicator to digital phones ?<br><br>Cheers<br>