11 Aug
2006
11 Aug
'06
12:57 p.m.
Hello,
please send me your config file. It seems that is a bit different than
the one on voip-info.org. The re-INVITE is managed via nathelper, but
the force_rtp_proxy() is called twice, the re-invite sent by openser
contains:
c=IN IP4 192.168.39.54192.168.39.54 and a=nortpproxy:yes..a=nortpproxy:yes..
This is a bug in the configuration file.
Cheers,
Daniel
U 2006/08/11 14:31:59.615113 192.168.39.54:5060 -> 192.168.39.50:5060
INVITE sip:400@192.168.39.50:5060 SIP/2.0..Record-Route:
<sip:192.168.39.54;lr=on;ftag=0-13c4-44dc5c97-4ee1e80-548d>..From:
<sip:500@19
2.168.39.54>;tag=0-13c4-44dc5c97-4ee1e80-548d..To:
<sip:anonymous@anonymous.com>;tag=0-13c4-44dc5c97-4ee1e30-4451..Call-ID:
c8ece4-0-13
c4-44dc5c97-4ee1e30-26db@anonymous.com..CSeq: 1 INVITE..Via:
SIP/2.0/UDP 192.168.39.54;branch=z9hG4bK9017.79c65191.0..Via: SIP/2.0/UDP
192.168.39.50:5060;rport=5060;branch=z9hG4bK-44dc5c9d-4ee37f8-7b90..Max-Forwards:
69..Supported: 100rel..User-Agent: SIP-RG..Contact: <
sip:500@192.168.39.50:5060;nat=yes>..Content-Type:
application/sdp..Content-Length: 372..P-hint:
rr-enforced....v=0..o=SIP-N-TA 0 0 IN
IP4 192.168.39.50..s=C0A82732 0000 C0A82732 0000 01 0..c=IN IP4
192.168.39.50..t=0 0..m=image 3503835038 udptl t38..c=IN IP4
192.168.39.54192.168.39.54..a=T38FaxVersion:0..a=T38MaxBitRate:14400..a=T38FaxFillBitRemoval:0..a=T38FaxTranscodingMMR:0..a=T38FaxTranscodingJBIG
:0..a=T38FaxRateManagement:transferredTCF..a=nortpproxy:yes..a=nortpproxy:yes..
On 08/11/06 13:31, Pavel D. Kuzin wrote:
[...]