X-ECN Telecoms-MailScanner-Information: Contact ECN Telecoms
X-ECN Telecoms-MailScanner: Found to be clean
X-ECN Telecoms-MailScanner-SpamCheck: not spam, SpamAssassin (not cached,
score=-103.361, required 6, autolearn=not spam, ALL_TRUSTED -1.80,
AWL 1.04, BAYES_00 -2.60, USER_IN_WHITELIST -100.00)
X-ECN Telecoms-MailScanner-From: [EMAIL PROTECTED]
X-Spam-Status: No
On Thu, 2008-01-17 at 04:57 -0800, David wrote:
> Hello,
>
> I have the following problem:
> 1. A fax call is sent to my CW server.
> 2. As defined by our call-flow (extensions.conf), it is first answered
> in G.729 and then we send a reINVITE for T.38.
> 3. The source/destination RTP port on the remote server is changed (in
> the OK message) to another port (+2) than the one originally used.
> 4. CW sends three T.38 packets to the correct new port (after
> acknowledging the new destination), but then, in the next bunch, it
> start sending the packets to the old port again, so the fax fails.
>
> How can I debug/fix it?
You haven't explained much.
Do you Answer() and then SipT38SwitchOver(), or just call RxFAX()? Try
to just call RxFAX(), or at least Wait() a bit between Answer() and
SipT38SwitchOver().
You say the RTP port is changed, but don't you mean the T.38 port is
changed?
Do you have nat=yes and/or a NAT?
Does anything happen between when callweaver sends the 3 correct packets
and when it starts to send the incorrect ones, like a SIP/RTP/T.38
packet from the other side?
A tcpdump would also help.
> Your help would be much appreciated.
>
> David
>
>
>
> ______________________________________________________________________
> Looking for last minute shopping deals? Find them fast with Yahoo!
> Search.
> _______________________________________________
> Callweaver-users mailing list
> [email protected]
> http://lists.callweaver.org/mailman/listinfo/callweaver-users
Damjan
_______________________________________________
Callweaver-users mailing list
[email protected]
http://lists.callweaver.org/mailman/listinfo/callweaver-users
