Re: [OpenSIPStack] RTP Issue - opensipstack 1.1.5
Brought to you by:
joegenbaclor
Menu
▾
▴
Re: [OpenSIPStack] RTP Issue - opensipstack 1.1.5
|
From: Gaurav K. <gkh...@is...> - 2007-08-07 10:47:39
|
Joegen,
Thanks for your reply. I'm planning to upgrade to the latest version. Is
there a release note/ README which captures the changes/ differences =
between
stable releases of the stack & sbc. E.g. Difference between 1.1.5 & =
1.1.7
(latest & greatest) versions of opensipstack
Thanks in advance for your reply.
Regards,
Gaurav
> -----Original Message-----
> From: Joegen E. Baclor [mailto:joe...@gm...]
> Sent: Tuesday, August 07, 2007 11:53 AM
> To: Gaurav Kheterpal
> Cc: ope...@li...; ag...@de...
> Subject: Re: RTP Issue - opensipstack 1.1.5
>=20
> Inline,
>=20
> Gaurav Kheterpal wrote:
> >
> > Hello,
> >
> > I=92m facing an issue with RTP on OpenSBC 1.1.2. My network
> > configuration is:-
> >
> > Xlite UA (Outbound) (.64) =DF----=E0 OpenSBC (.115) =DF-------=E0 =
FreeSwitch
> > (.57) =DF------=E0 Xlite UA (Inbound) (.57)
> >
> > * Outbound UA is registered on OpenSBC
> >
> > * Inbound UA is registered on FreeSwitch
> >
> > * A route exists from OpenSBC to FreeSwitch
> >
> > I am using:-
> >
> > Opensipstack 1.1.5
> >
> > Opensbc 1.1.2
> >
> > I=92m seeing the following errors in Level 5 log files:-
> >
> > 2007/08/07 10:46:33.745 OpalMediaThread:af4eb8 Info RTP_UDP Started
> > Media Stream
> >
> > 2007/08/07 10:46:34.877 OpalMediaThread:aed1f8 Info RTP Abnormal
> > change of sequence numbers, adjusting to expect 7614 ssrc=3D41
> >
> > 2007/08/07 10:46:35.097 OpalMediaThread:aed1f8 Info RTP Abnormal
> > change of sequence numbers, adjusting to expect 7644 ssrc=3D41
> >
> > 2007/08/07 10:46:35.387 OpalMediaThread:aed1f8 Info RTP Abnormal
> > change of sequence numbers, adjusting to expect 7694 ssrc=3D41
> >
> > 2007/08/07 10:46:35.698 OpalMediaThread:aed1f8 Info RTP Abnormal
> > change of sequence numbers, adjusting to expect 7744 ssrc=3D41
> >
> > 2007/08/07 10:46:36.018 OpalMediaThread:aed1f8 Info RTP Abnormal
> > change of sequence numbers, adjusting to expect 7793 ssrc=3D41
> >
> > 2007/08/07 10:46:36.299 OpalMediaThread:aed1f8 Info RTP Abnormal
> > change of sequence numbers, adjusting to expect 7842 ssrc=3D41
> >
> > 2007/08/07 10:46:36.689 OpalMediaThread:aed1f8 Info RTP Abnormal
> > change of sequence numbers, adjusting to expect 7893 ssrc=3D41
> >
> > 2007/08/07 10:46:36.980 OpalMediaThread:aed1f8 Info RTP Abnormal
> > change of sequence numbers, adjusting to expect 7942 ssrc=3D41
> >
> > 2007/08/07 10:46:37.390 OpalMediaThread:aed1f8 Info RTP Abnormal
> > change of sequence numbers, adjusting to expect 7992 ssrc=3D41
> >
> > 2007/08/07 10:46:37.761 OpalMediaThread:aed1f8 Info RTP Abnormal
> > change of sequence numbers, adjusting to expect 8041 ssrc=3D41
> >
> > 2007/08/07 10:46:52.100 OpalMediaThread:aed1f8 Info RTP Abnormal
> > change of sequence numbers, adjusting to expect 8092 ssrc=3D41
> >
> > 2007/08/07 10:46:52.400 OpalMediaThread:aed1f8 Info RTP Abnormal
> > change of sequence numbers, adjusting to expect 8141 ssrc=3D41
> >
> > 2007/08/07 10:46:53.692 Call Info *** DESTROYED *** SIPTimer Manager
> >
> > The Level 5 Log & Ethereal capture on OpenSBC is attached. I=92m =
able to
> > hear audio at both ends.
> >
> > I looked up the code & found the following in rtp.cxx:-
> >
> > // Check for Cisco bug where sequence numbers suddenly start
> incrementing
> >
> > // from a different base.
> >
> > if (++consecutiveOutOfOrderPackets > 10) {
> >
> > expectedSequenceNumber =3D (WORD)(sequenceNumber + 1);
> >
> > PTRACE(1, "RTP\tAbnormal change of sequence numbers, adjusting to
> > expect " << expectedSequenceNumber << " ssrc=3D" << syncSourceIn);
> >
> > }
> >
> > Is it a known issue or something which has been fixed in 1.1.7?
> >
> Of course an upgrade is always a good idea.
>=20
> This is not a bug at all. One cause might be RTP packets are lost
> between FreeSwitch and OpenSBC. OpenSBC is expecting the sequence =
number
> to increase by one. See excerpts from RFC3550 below
>=20
> sequence number: 16 bits
> The sequence number increments by one for each RTP data =
packet
> sent, and may be used by the receiver to detect packet loss =
and
> to
> restore packet sequence. The initial value of the sequence
> number
> SHOULD be random (unpredictable) to make known-plaintext =
attacks
> on encryption more difficult, even if the source itself does =
not
> encrypt according to the method in Section 9.1, because the
> packets may flow through a translator that does. Techniques =
for
> choosing unpredictable numbers are discussed in [17].
>=20
>=20
>=20
> If the sequence received by OpenSBC is greater than what it is
> expecting, it would be spitting out the warning traces you have just
> pasted.
>=20
>=20
> > Moreover, when I press DTMF, I see it in Ethereal capture on OpenSBC
> > but OpenSBC does not seem to be detecting it. That=92s a different =
issue
> > from the one reported above.
> >
>=20
> OpenSBC relays DTMF as any normal RTP packets. It does not have to
> detect it.
> >
> > I=92ll be thankful for any guidance on what=92s going wrong.
> >
> > Regards,
> > Gaurav
> >
> > =
------------------------------------------------------------------------
> >
> > 2007/08/07 10:46:32.463 Proxy Info -->> From:
> sip:102@192.168.96.115 Target: INVITE
> sip:101@192.168.96.115:65062;method=3D"INVITE"
> > 2007/08/07 10:46:32.834 UserAgent Info Using remote
> XML-RPC registrar at http://localhost:5678/RPC2
> > 2007/08/07 10:46:32.934 HTTP Service:ad7198 Info
> Registrar.FindRegistration
> > 2007/08/07 10:46:32.954 UserAgent Info No
> Registration found
> > 2007/08/07 10:46:33.745 OpalMediaThread:aed1f8 Info RTP_UDP
> Started Media Stream
> > 2007/08/07 10:46:33.745 OpalMediaThread:af4eb8 Info RTP_UDP
> Started Media Stream
> > 2007/08/07 10:46:34.877 OpalMediaThread:aed1f8 Info RTP
Abnormal
> change of sequence numbers, adjusting to expect 7614 ssrc=3D41
> > 2007/08/07 10:46:35.097 OpalMediaThread:aed1f8 Info RTP
Abnormal
> change of sequence numbers, adjusting to expect 7644 ssrc=3D41
> > 2007/08/07 10:46:35.387 OpalMediaThread:aed1f8 Info RTP
Abnormal
> change of sequence numbers, adjusting to expect 7694 ssrc=3D41
> > 2007/08/07 10:46:35.698 OpalMediaThread:aed1f8 Info RTP
Abnormal
> change of sequence numbers, adjusting to expect 7744 ssrc=3D41
> > 2007/08/07 10:46:36.018 OpalMediaThread:aed1f8 Info RTP
Abnormal
> change of sequence numbers, adjusting to expect 7793 ssrc=3D41
> > 2007/08/07 10:46:36.299 OpalMediaThread:aed1f8 Info RTP
Abnormal
> change of sequence numbers, adjusting to expect 7842 ssrc=3D41
> > 2007/08/07 10:46:36.689 OpalMediaThread:aed1f8 Info RTP
Abnormal
> change of sequence numbers, adjusting to expect 7893 ssrc=3D41
> > 2007/08/07 10:46:36.980 OpalMediaThread:aed1f8 Info RTP
Abnormal
> change of sequence numbers, adjusting to expect 7942 ssrc=3D41
> > 2007/08/07 10:46:37.390 OpalMediaThread:aed1f8 Info RTP
Abnormal
> change of sequence numbers, adjusting to expect 7992 ssrc=3D41
> > 2007/08/07 10:46:37.761 OpalMediaThread:aed1f8 Info RTP
Abnormal
> change of sequence numbers, adjusting to expect 8041 ssrc=3D41
> > 2007/08/07 10:46:52.100 OpalMediaThread:aed1f8 Info RTP
Abnormal
> change of sequence numbers, adjusting to expect 8092 ssrc=3D41
> > 2007/08/07 10:46:52.400 OpalMediaThread:aed1f8 Info RTP
Abnormal
> change of sequence numbers, adjusting to expect 8141 ssrc=3D41
> > 2007/08/07 10:46:53.692 Call Info ***
DESTROYED
> *** SIPTimer Manager
> > 2007/08/07 10:46:53.702 OpalMediaThread:af4eb8 Info RTP_UDP
> Closing Media Stream
> > 2007/08/07 10:46:53.702 OpalMediaThread:aed1f8 Info RTP_UDP
> Closing Media Stream
> >
|
