[Serusers] Call expires after 30 seconds with SER + MEDIAPROXY +VOVIDA B2BUA

[Greger V. Teigre]

Only B2BUA can generate a BYE, so it's definitely not SER. However, there 
may be something else that causes Vovida to generate it. I would start in 
that end. I don't know Vovida, so I wouldn't know where to start...
g-)

Alberto Cruz wrote:
> Does anybody have SER running with MEDIAPROXY and Vovida B2BUA at the
> same machine?
>
> I'm having a little trouble with the calls: They are finishing after
> 30 seconds.
>
> After I have reviewed the NGREP sniffing I can detect that the B2BUA
> is sending a BYE to the SER as you can see:
>
> U 2005/06/26 22:59:29.210454 200.67.33.247:61767 -> 200.94.75.6:5060
> ACK sip:018183324166 at 200.94.75.6:5060 SIP/2.0.
> Via: SIP/2.0/UDP 172.31.253.127:5060;branch=z9hG4bK-4413ed9d.
> From: 8183651723
> <sip:8183651723 at sipsrv.conecta-te.com>;tag=d96bd682df5aa957o0.
> To: <sip:018183324166 at sipsrv.conecta-te.com>;tag=71eb8754.
> Call-ID: 1a18e21e-eaa9b26b at 172.31.253.127.
> CSeq: 101 ACK.
> Max-Forwards: 70.
> Route: <sip:018183324166 at 200.94.75.6:5065>.
> Contact: 8183651723 <sip:8183651723 at 172.31.253.127:5060>.
> User-Agent: Linksys/PAP2-2.0.12(LS).
> Content-Length: 0.
> .
>
> #
> U 2005/06/26 22:59:29.213193 200.94.75.6:5060 -> 200.94.75.6:5065
> ACK sip:018183324166 at 200.94.75.6:5065 SIP/2.0.
> Record-Route: <sip:200.94.75.6;ftag=d96bd682df5aa957o0;lr=on>.
> Via: SIP/2.0/UDP 200.94.75.6;branch=0.
> Via: SIP/2.0/UDP
> 172.31.253.127:5060;rport=61767;received=200.67.33.247;branch=z9hG4bK-4413ed9d.
> From: 8183651723
> <sip:8183651723 at sipsrv.conecta-te.com>;tag=d96bd682df5aa957o0.
> To: <sip:018183324166 at sipsrv.conecta-te.com>;tag=71eb8754.
> Call-ID: 1a18e21e-eaa9b26b at 172.31.253.127.
> CSeq: 101 ACK.
> Max-Forwards: 16.
> Contact: 8183651723 <sip:8183651723 at 172.31.253.127:5060>.
> User-Agent: Linksys/PAP2-2.0.12(LS).
> Content-Length: 0.
> P-hint: rr-enforced.
> .
>
> #
> U 2005/06/26 22:59:29.214421 200.94.75.6:5065 -> 200.94.75.6:5060
> ACK sip:018183324166 at 200.94.75.6:5060 SIP/2.0.
> Via: SIP/2.0/UDP 200.94.75.6:5065.
> To: <sip:018183324166 at sipsrv.conecta-te.com>;tag=33F1FB80-B96.
> From: 8183651723
> <sip:8183651723 at sipsrv.conecta-te.com>;tag=d96bd682df5aa957o0.
> Call-ID: 8c9da6de70b56114b926f823b1173c3a at 200.94.75.6.
> CSeq: 101 ACK.
> Max-Forwards: 70.
> Route: <sip:018183324166 at 200.94.75.1:5060>.
> Content-Length: 0.
> .
>
> #
> U 2005/06/26 22:59:29.218000 200.94.75.6:5060 -> 200.94.75.1:5060
> ACK sip:018183324166 at 200.94.75.1:5060 SIP/2.0.
> Record-Route: <sip:200.94.75.6;ftag=d96bd682df5aa957o0;lr=on>.
> Via: SIP/2.0/UDP 200.94.75.6;branch=0.
> Via: SIP/2.0/UDP 200.94.75.6:5065.
> To: <sip:018183324166 at sipsrv.conecta-te.com>;tag=33F1FB80-B96.
> From: 8183651723
> <sip:8183651723 at sipsrv.conecta-te.com>;tag=d96bd682df5aa957o0.
> Call-ID: 8c9da6de70b56114b926f823b1173c3a at 200.94.75.6.
> CSeq: 101 ACK.
> Max-Forwards: 16.
> Content-Length: 0.
> P-hint: rr-enforced.
> .
>
> ##
> U 2005/06/26 23:00:05.104387 200.94.75.6:5065 -> 200.94.75.6:5060
> BYE sip:018183324166 at 200.94.75.6:5060;lr=on SIP/2.0.
> Via: SIP/2.0/UDP 200.94.75.6:5065.
> To: 8183651723
> <sip:8183651723 at sipsrv.conecta-te.com>;tag=d96bd682df5aa957o0.
> From: <sip:018183324166 at sipsrv.conecta-te.com>;tag=71eb8754.
> Call-ID: 1a18e21e-eaa9b26b at 172.31.253.127.
> CSeq: 102 BYE.
> Max-Forwards: 16.
> Route: <sip:8183651723 at 200.94.75.6:61767>.
> Record-Route: <sip:200.94.75.6;ftag=d96bd682df5aa957o0;lr=on>.
> Contact: 8183651723 <sip:8183651723 at 172.31.253.127:5060>.
> User-Agent: Linksys/PAP2-2.0.12(LS).
> Content-Length: 0.
> P-hint: rr-enforced.
>
> Does anybody know if this is a problem with the VOVIDA B2BUA or the
> SER? Any idea?
>
> Thanks
>
> Alberto Cruz
>
> _______________________________________________
> Serusers mailing list
> serusers at lists.iptel.org
> http://lists.iptel.org/mailman/listinfo/serusers