<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;"><br>
<br>
Handling of fastStart in CallProceeding is commented out in h323plus library,<br>
this is exploration from h323plus developers about this:<br>
<br>
<br>
Yes that should be mera.<br>
<br>
The problem is that Callproceeding does not always come from the remote it<br>
may be generated by the gatekeeper. </blockquote><div><br>this is a feature .. called force_callproceeding. It means MERA will send a provisional CallProceeding in order not to timeout on calls that don't respond with that message on time. If this message contains a faststart element it is certanly a bug and it has to be reported to them.<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">MERA where sending fast start elements<br>
in the Call proceeding and connect. The call proceeding where not valid and<br>
causing the media to fail. </blockquote><div><br>well if there is a correct faststart element within a connect message (or alerting or facility or progress), the originator should adjust the media resources accordingly. Here what could went wrong is just the media before the next faststart element in the row.<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Normally (although valid) EP's do not set Fast<br>
Start in Call proceeding so the code was disabled to resolve the MERA issue.<br>
<br></blockquote><div><br>well, this is unlikely as fast start element can be included in call proceeding message. The developer's task is to determine whether a call proceeding message is to be trusted or not.<br>Also, provisional call proceeding messages don't have faststart element included! There are equipment (Cisco PGW / HSI) that are sending call proceeding with faststart element and h245Controll (OLC + TCS/MSD) that has to be treated correctly. Unfortunately, just disabling handling of callproceeding faststart element is not a real option...<br>
<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
if you wont read "bugs" file in mod_h323, there is explaned how to enable it.<br></blockquote><div><br><br>of course i can enable it during build time but this will not solve interop issues later we can encounter...<br>
<br><br><br><br>Do you maybe have some sniffs/traces of the wrong call proceeding message ?<br><br><br><br>...anyhow this is the expected behaviour when a GK/Proxy sends a provisional Call Proceding to the terminator and later it receives the real Call Proceeding carring faststart and h245Controll element within.<br>
<br>Entities in the signalling path shall also use the Facility message or the Progress message to convey<br>any new information (such as Q.931 information elements, CallProceeding-UUIE fields, tunnelled<br>non-H.323 protocols, and encapsulated H.245 messages) received in a Call Proceeding message to<br>
the other endpoint if the entity has already sent a Call Proceeding message. This will allow the<br>entity, for example, to transmit the fastStart element to facilitate proper establishment of a Fast<br>Connect call and/or a Progress Indicator to indicate the presence of in-band tones and<br>
announcements. When using the Facility message to carrying such information extracted from the<br>Call Proceeding message, the reason in the Facility should be set to forwardedElements.<br><br><br><br>in other words:<br><br>
<span style="font-family: courier new,monospace;">ORIG GK TERM</span><br>-------------------------------------------------------------------------------------------------------------<br style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;">Setup OLC =></span><br style="font-family: courier new,monospace;"><span style="font-family: courier new,monospace;">Call proceeding (prov) <=</span><br style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;"> Setup OLC =></span><br style="font-family: courier new,monospace;"><span style="font-family: courier new,monospace;"> Call proceeding (OLC+TCS/MSD) <= </span><br style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;">Facility (OLC+TCS/MSD) <=</span><br style="font-family: courier new,monospace;"><br style="font-family: courier new,monospace;"><br style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;"><----------- normal call establishment scenario follows -----------></span><br> <br><br><br></div></div><br><br>