[Freeswitch-users] Fwd: mod_opal - call charged before H.225 connect

[Tihomir Culjaga]

> TC>
> TC>it is gonna be easier to track.
> TC>
> TC>Tomorrow i will test on 1.0.4 but please lets move to trunk.
>
> i make it a bit later, to move tickets to jira and source to svn i
> need some time to undertand how this system is works, especially jira.
>
>
audio issue is better now :)

however i have a few questions:

1. can we control codec framing size via config file setting (e.g. PCMA:20,
PCMU:20)?
2. can we control tunneling via config file setting?
3. can we control mediaWaitForConnect flag within setup message via config
file setting?


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.

Here is a tshark:

  5.242526    10.4.62.7 -> 10.4.4.254   H.225.0 CS: setup OpenLogicalChannel

  5.243982   10.4.4.254 -> 10.4.62.7    H.225.0 CS: callProceeding
 10.512617   10.4.4.254 -> 10.4.62.7    H.225.0 CS: progress
 10.983697   10.4.4.254 -> 10.4.62.7    H.225.0 CS: alerting
 20.002796   10.4.4.254 -> 10.4.62.7    H.225.0 CS: connect
 20.002981   10.4.4.254 -> 10.4.62.7    H.225.0/H.245 CS: facility
terminalCapabilitySet
 20.003210   10.4.4.254 -> 10.4.62.7    H.225.0/H.245 CS: facility
masterSlaveDetermination
 31.472362   10.4.4.254 -> 10.4.62.7    H.225.0/H.245 CS: releaseComplete
endSessionCommand


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.


your behavior should be like this:

  5.242526    10.4.62.7 -> 10.4.4.254   H.225.0 CS: setup
OpenLogicalChannel  g711A with 30 ms
  5.243982   10.4.4.254 -> 10.4.62.7    H.225.0 CS: callProceeding
 10.512617   10.4.4.254 -> 10.4.62.7    H.225.0 CS: progress

                     10.4.62.7 -> 10.4.4.254    H.225.0/H.245 CS: facility
terminalCapabilitySet
                     10.4.62.7 -> 10.4.4.254    H.225.0/H.245 CS: facility
masterSlaveDetermination

                     10.4.4.254 -> 10.4.62.7    H.225.0/H.245 CS: facility
terminalCapabilitySet
                     10.4.4.254 -> 10.4.62.7    H.225.0/H.245 CS: facility
masterSlaveDetermination

                     10.4.4.254 -> 10.4.62.7    H.225.0/H.245 CS: facility
terminalCapabilitySetAck
                     10.4.4.254 -> 10.4.62.7    H.225.0/H.245 CS: facility
masterSlaveDeterminationAck

                     10.4.62.7 -> 10.4.4.254    H.225.0/H.245 CS: facility
terminalCapabilitySetAck
                     10.4.62.7 -> 10.4.4.254    H.225.0/H.245 CS: facility
masterSlaveDeterminationAck

                     10.4.62.7 -> 10.4.4.254    H.225.0/H.245 CS: facility
openlogicalchannel (g711A)
                     10.4.4.254 -> 10.4.62.7    H.225.0/H.245 CS: facility
openlogicalchannel (g711A)

                     10.4.62.7 -> 10.4.4.254    H.225.0/H.245 CS: facility
openlogicalchannelAck
                     10.4.4.254 -> 10.4.62.7    H.225.0/H.245 CS: facility
openlogicalchannelAck

                       <now you can start pre_answer!>

 10.983697   10.4.4.254 -> 10.4.62.7    H.225.0 CS: alerting
...
...
...
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20091023/6c7dfe3d/attachment-0002.html