<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;">
TC><br>
TC>it is gonna be easier to track.<br>
TC><br>
TC>Tomorrow i will test on 1.0.4 but please lets move to trunk.<br>
<br>
i make it a bit later, to move tickets to jira and source to svn i<br>
need some time to undertand how this system is works, especially jira.<br>
<div><div></div><div class="h5"><br>
</div></div></blockquote></div><br>audio issue is better now :)<br><br>however i have a few questions:<br><br>1. can we control codec framing size via config file setting (e.g. PCMA:20, PCMU:20)?<br>2. can we control tunneling via config file setting?<br>
3. can we control mediaWaitForConnect flag within setup message via config file setting?<br><br><br>Now, when i can test more and place outgoing calls to different equipment, i found that there is an issue when we get h.225 progress without a fastStart element. <br>
<br>Here is a tshark:<br><br> 5.242526 10.4.62.7 -> 10.4.4.254 H.225.0 CS: setup OpenLogicalChannel <br> 5.243982 10.4.4.254 -> 10.4.62.7 H.225.0 CS: callProceeding <br> 10.512617 10.4.4.254 -> 10.4.62.7 H.225.0 CS: progress <br>
10.983697 10.4.4.254 -> 10.4.62.7 H.225.0 CS: alerting <br> 20.002796 10.4.4.254 -> 10.4.62.7 H.225.0 CS: connect <br> 20.002981 10.4.4.254 -> 10.4.62.7 H.225.0/H.245 CS: facility terminalCapabilitySet <br>
20.003210 10.4.4.254 -> 10.4.62.7 H.225.0/H.245 CS: facility masterSlaveDetermination <br> 31.472362 10.4.4.254 -> 10.4.62.7 H.225.0/H.245 CS: releaseComplete endSessionCommand <br><br><br>the terminating GW didn't include a faststart element within a returning h.225 message we didn't match the capabilities (framing of them) in our setup (and you are waiting an open LC to start pre_answer).... so now, the terminator is waiting for the originator to start exchanging TCS/MSD. As tunneling is true, this should be done using h.225 Facility messages.<br>
<br><br>your behavior should be like this:<br><br> 5.242526 10.4.62.7 -> 10.4.4.254 H.225.0 CS: setup OpenLogicalChannel g711A with 30 ms<br>
5.243982 10.4.4.254 -> 10.4.62.7 H.225.0 CS: callProceeding <br>
10.512617 10.4.4.254 -> 10.4.62.7 H.225.0 CS: progress <br><br> 10.4.62.7 -> 10.4.4.254 H.225.0/H.245 CS: facility terminalCapabilitySet <br> 10.4.62.7 -> 10.4.4.254 H.225.0/H.245 CS: facility masterSlaveDetermination <br>
<br> 10.4.4.254 -> 10.4.62.7 H.225.0/H.245 CS: facility terminalCapabilitySet <br> 10.4.4.254 -> 10.4.62.7 H.225.0/H.245 CS: facility masterSlaveDetermination <br><br> 10.4.4.254 -> 10.4.62.7 H.225.0/H.245 CS: facility terminalCapabilitySetAck <br>
10.4.4.254 -> 10.4.62.7 H.225.0/H.245 CS: facility masterSlaveDeterminationAck<br><br> 10.4.62.7 -> 10.4.4.254 H.225.0/H.245 CS: facility terminalCapabilitySetAck<br> 10.4.62.7 -> 10.4.4.254 H.225.0/H.245 CS: facility masterSlaveDeterminationAck<br>
<br> 10.4.62.7 -> 10.4.4.254 H.225.0/H.245 CS: facility openlogicalchannel (g711A)<br> 10.4.4.254 -> 10.4.62.7 H.225.0/H.245 CS: facility openlogicalchannel (g711A) <br>
<br> 10.4.62.7 -> 10.4.4.254 H.225.0/H.245 CS: facility openlogicalchannelAck<br>
10.4.4.254 -> 10.4.62.7 H.225.0/H.245 CS: facility openlogicalchannelAck<br><br> <now you can start pre_answer!><br><br>
10.983697 10.4.4.254 -> 10.4.62.7 H.225.0 CS: alerting <br>...<br>...<br>...<br><br><br><br><br><br>