On Wed, Jul 8, 2009 at 9:10 AM, Melcon Moraes <span dir="ltr"><<a href="mailto:melcon@gmail.com">melcon@gmail.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
The difference is how the call is supposed to be billed/processed by the far end. You can accept or reject calls according to its category.<br><br>I think that most of the available categories are not used anymore, just a few ones, depending on the country practices.<br>
<br>This is MF signaling, not CAS. The seize timeout is CAS related and happens way before the category exchange.</blockquote><div><br>As Melcon pointed out, that parameter does not affect the seize behavior and no, there is nothing you can do from a configuration point of view, in terms of tcp connections is like doing "telnet <a href="http://telco.host.com">telco.host.com</a>" and after a few seconds getting connection timed out. What can you do from telnet prespective? nothing, the problem is either in the network (your cabling) or the far end.<br>
<br></div></div>-- <br>Moises Silva<br>Software Developer<br>Sangoma Technologies Inc. | 50 McIntosh Drive, Suite 120, Markham ON L3R 9T3 Canada<br>t. 1 905 474 1990 x 128 | e. <a href="mailto:moy@sangoma.com">moy@sangoma.com</a><br>