What is the definitive story on hairpin T.38 calls? I've been told that it may not be allowed and the way my systems are behaving seems to bear this out. However, searching on the web seems to contradict this and I want to be sure that there isn't something either I or my proxy provider can do to solve this problem before going to a far less elegant solution.
Basically, here's my situation: I use TxFAX via a .call script to initiate a fax call to SIP/[EMAIL PROTECTED] 19998887777 is registered to me so the proxy tries to set up a call with my system. During the setup process the proxy generates a "488 Not Acceptable Here" response. By this time, the RxFAX dialplan for 19998887777 is in full gear and it eventually times out with a "The call dropped prematurely". Now I know that I can successfully send and receive T.38 calls because I have two systems with identical setups and I can send from one to the other through the same proxy in either direction with no troubles. In other words, the only thing I change in my .call script to go from a working fax transmission between machines to a non-working hairpin is the number in the channel specification. FYI, on both machines I am using callweaver 1.2.0.1 general release modified to work with spandsp0.0.5pre4. So, can I do this? If not, why not? (needed to fully understand the situation). _______________________________________________ Callweaver-users mailing list [email protected] http://lists.callweaver.org/mailman/listinfo/callweaver-users
