10 Oct
2005
10 Oct
'05
7:55 a.m.
Hello all,
I am using ser 0.9.4 + rtpproxy. now when our SSW INVITEs SER, SER sends
100-trying to the udp-source-port where SER should reply with connection
information in via or contact headers. (probably via header)
Please comment.
Thank you
--
Atif
10 Oct
10 Oct
1:16 p.m.
Maybe you force symmetric signaling via force-rport() or the client
forces it via the rport parameter in the Via header
regards
klaus
Atif Rasheed wrote:
Hello all,
I am using ser 0.9.4 + rtpproxy. now when our SSW INVITEs SER, SER sends
100-trying to the udp-source-port where SER should reply with connection
information in via or contact headers. (probably via header)
Please comment.
Thank you
--
Atif
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
2:08 p.m.
Thank you for your comments, let me explain in detail.
working scenario is:
SSW (10.0.2.14) -----> SER (10.0.2.99)
now you can see in the traces below that SER is replying/sending
100-trying on the UDP-Source Port of INVITE, where it should reply at
ip:port mentioned in Via Header in INVITE.
below is traced INVITE from SSW to SER :
User Datagram Protocol, Src Port: 5062 (5062), Dst Port: 5060 (5060)
Session Initiation Protocol
Request-Line: INVITE sip:0214130525@10.0.2.99:5060 SIP/2.0
Message Header
Call-ID:AAcmbQAADCIAABeyCgACAw@xener.com
Content-Length:157
CSeq:1 INVITE
Contact:<sip:0514100857@10.0.2.14:5060>
Content-Type:application/sdp
From:sip:0514100857@10.0.2.14:5060;tag=t06i00a0001909x0001909
Max-Forwards:69
To:sip:0214130525@10.0.2.99:5060
Record-Route:<sip:10.0.2.14:5060;lr>
Via:SIP/2.0/UDP
10.0.2.14:5060;branch=z9hG4bKhsig0000010442AAcpZQAADCIAABeyCgACAwa1909
Message body
100-trying message from SER to SSW:
User Datagram Protocol, Src Port: 5060 (5060), Dst Port: 5062 (5062)
Session Initiation Protocol
Status-Line: SIP/2.0 100 trying -- your call is important to us
Message Header
Call-ID:AAcmbQAADCIAABeyCgACAw@xener.com
CSeq:1 INVITE
From:sip:0514100857@10.0.2.14:5060;tag=t06i00a0001909x0001909
To:sip:0214130525@10.0.2.99:5060
Via:SIP/2.0/UDP
10.0.2.14:5060;branch=z9hG4bKhsig0000010442AAcpZQAADCIAABeyCgACAwa1909;rport=5062
Server: Sip EXpress router (0.9.4 (i386/linux))
Content-Length: 0
Warning: 392 10.0.2.99:5060 "Noisy feedback tells: pid=19179
req_src_ip=10.0.2.14 req_src_port=5062
in_uri=sip:0214130525@10.0.2.99:5060
out_uri=sip:16414701378@66.33.147.150:5110 via_cnt==1"
best Regards,
--
Atif
On Mon, 2005-10-10 at 19:16 +0200, Klaus Darilion wrote:
Maybe you force symmetric signaling via force-rport()
or the client
forces it via the rport parameter in the Via header
regards
klaus
Atif Rasheed wrote:
Hello all,
I am using ser 0.9.4 + rtpproxy. now when our SSW INVITEs SER, SER sends
100-trying to the udp-source-port where SER should reply with connection
information in via or contact headers. (probably via header)
Please comment.
Thank you
--
Atif
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
6839
days inactive
6839
days old
2 comments
2 participants
participants (2)
-
Atif Rasheed -
Klaus Darilion