Documente Academic
Documente Profesional
Documente Cultură
Problems
While the following is not an all-incl"sive list, it presents the highest-priority iss"es as deter!ined by the Tas( +ro"p. 1. Triggering of T.38 s,itc1o.er #roble!s T38 does not indicate which party ,#arty 3 or #arty 6- is responsible for detecting that a *37 trans!ission is being atte!pted and initiating the switch fro! a"dio !ode to T.38 !ode. In practice, this res"lts in so!e co!!on scenarios8 3 2eceiving +ateway !ay initiate T.38 after detecting 95$03/) tones generated by the #arty 6 endpoint. 3 2eceiving +ateway !ay initiate T.38 after detecting the :.&1 1$;9 flags ,prea!blegenerated by the party 6 endpoint. 3 2eceiving +ateway !ay initiate T.38 after detecting 9/+ tone generated by the #arty 3 5ndpoint. 3n 5!itting +ateway !ay initiate T.38 after detecting 9/+ tone generated by the #arty 3 endpoint.
In so!e cases, gateways !ay atte!pt to detect tones generated by the far endpoint, which !ay be "nreliable if the a"dio connection between the endpoints is "sing a highly co!pressed voice codec. While it is generally accepted that the 2eceiving +ateway sho"ld initiate the switch to T.38, and it sho"ld only do this after detecting the :.&1 1$;9 flags generated by the endpoint it services ,to ens"re that the answering device is in fact a facsi!ile endpoint, and not a data !ode! or other device that !ight also generate 95$03/) tones-, in practice this is not the case, and act"al devices !ay act in any of the fashions listed above. This can easily res"lt in <glare<, where both gateways atte!pt to switch to T.38 ,nearlyCopyright 2 ! SIP Forum" #ll rights reserve$" %%%"sip&orum"org