Re: [Serusers] nathelper updated to support RTP proxy

List overview All Threads
Download

newer

older

RE: [Serusers] www_authorize()

Maxim Sobolev

9 Jul 2003 9 Jul '03

9:11 p.m.

Oh, sorry, I've misunderstood your problem. What kind of device UA1 is? Can you please try the same with ATAs on both ends? -Maxim Ricardo Villa wrote:

...

Hi Maxim, Sorry but I don't understand what you mean. Ser and RTP Proxy are on a machine with IP Address=192.168.1.111. The WAN interface of the NAT Router is 192.168.1.1. What exactly should I do? UA1---SER(192.168.1.111)---(192.168.1.1)NAT(192.168.0.1)----ATA186(192.168.0 .15) Thanks, Ricardo ----- Original Message ----- From: "Maxim Sobolev" <sobomax(a)portaone.com> To: "Ricardo Villa" <ricvil(a)epm.net.co> Cc: <serusers(a)lists.iptel.org>rg>; <serdev(a)lists.iptel.org> Sent: Wednesday, July 09, 2003 7:18 PM Subject: Re: [Serusers] nathelper updated to support RTP proxy

Try to bind both ser and rtpproxy to the IP address of "WAN" interface - 192.168.0.1 and let me know if it helps or not. -Maxim Ricardo Villa wrote: >Hi Maxim, > >I have tested on 0.8.12dev-t10 installed on RedHat 7.3. > >The results are mixed. Only about 40% of the calls have audio even

though

the SDP is rewritten properly. My test setup is like this: UA1(192.168.1.10) -- SER(192.168.1.111)---(192.168.1.1)NAT(192.168.0.1)--ATA186(192.168.0.15) I have included the "-f" output from the rtpproxy plus 4 ngrep files. 1. success_from_internet.txt --> good call from UA1 to ATA186 2. fail_from_internet.txt ---> no audio call from UA1 to ATA186 3. success_from_nat.txt ----> good call from ATA186 to UA1 4. fail_from_nat.txt ---> no audio call from ATA186 to UA1 Please let me know how else we can troubleshoot this. Thanks, Ricardo ----- Original Message ----- From: "Maxim Sobolev" <sobomax(a)portaone.com> To: <serusers(a)lists.iptel.org> Cc: <serdev(a)lists.iptel.org> Sent: Sunday, July 06, 2003 12:16 PM Subject: [Serusers] nathelper updated to support RTP proxy >Folks, > >Today I've updated nathelper module to support RTP proxy. It would >be nice if somebody can test it on platforms other than FreeBSD, >because I don't have an access to such boxes right now. The RTP >proxy itself can be downloaded from: > >https://demo.portaone.com/~sobomax/PortaSIP/rtpproxy/ > >Any feedback is greatly appreciated. > >-Maxim >P.S. I've committed it to the HEAD, those with 0.8.11 prerelease >please apply the following patch: > >https://demo.portaone.com/~sobomax/nathelper.diff > >_______________________________________________ >Serusers mailing list >serusers(a)lists.iptel.org >http://lists.iptel.org/mailman/listinfo/serusers > > > >------------------------------------------------------------------------ > >_______________________________________________ >Serusers mailing list >serusers(a)lists.iptel.org >http://lists.iptel.org/mailman/listinfo/serusers

Show replies by date

Ricardo Villa

9 Jul 9 Jul

10:18 p.m.

New subject: [Serusers] nathelper updated to support RTP proxy

Hi Maxim, UA1 is the Nortel Networks SIP Client. I did not put it behind a NAT so as to avoid any issues. But I followed your suggestion and swapped it for another ATA186. It seems to work fine now. Made about 20 calls and all had fine audio. Any ideas why other UAs can have problems even though they are not behind a NAT??

...

From my observations of the rtpproxy output, I notice that when the call is

...

Oh, sorry, I've misunderstood your problem. What kind of device UA1 is? Can you please try the same with ATAs on both ends? -Maxim Ricardo Villa wrote: > Hi Maxim, > > Sorry but I don't understand what you mean. Ser and RTP Proxy are on a > machine with IP Address=192.168.1.111. The WAN interface of the NAT

Router

...

> is 192.168.1.1. What exactly should I do? > >

UA1---SER(192.168.1.111)---(192.168.1.1)NAT(192.168.0.1)----ATA186(192.168.0

...

.15) Thanks, Ricardo ----- Original Message ----- From: "Maxim Sobolev" <sobomax(a)portaone.com> To: "Ricardo Villa" <ricvil(a)epm.net.co> Cc: <serusers(a)lists.iptel.org>rg>; <serdev(a)lists.iptel.org> Sent: Wednesday, July 09, 2003 7:18 PM Subject: Re: [Serusers] nathelper updated to support RTP proxy

though >>the SDP is rewritten properly. >> >>My test setup is like this: >> >>UA1(192.168.1.10) --

>SER(192.168.1.111)---(192.168.1.1)NAT(192.168.0.1)--ATA186(192.168.0.15) >> >>I have included the "-f" output from the rtpproxy plus 4 ngrep files. >> >>1. success_from_internet.txt --> good call from UA1 to ATA186 >>2. fail_from_internet.txt ---> no audio call from UA1 to ATA186 >>3. success_from_nat.txt ----> good call from ATA186 to UA1 >>4. fail_from_nat.txt ---> no audio call from ATA186 to UA1 >> >>Please let me know how else we can troubleshoot this. >> >>Thanks, >>Ricardo >> >> >> >>----- Original Message ----- >>From: "Maxim Sobolev" <sobomax(a)portaone.com> >>To: <serusers(a)lists.iptel.org> >>Cc: <serdev(a)lists.iptel.org> >>Sent: Sunday, July 06, 2003 12:16 PM >>Subject: [Serusers] nathelper updated to support RTP proxy >> >> >> >> >>>Folks, >>> >>>Today I've updated nathelper module to support RTP proxy. It would >>>be nice if somebody can test it on platforms other than FreeBSD, >>>because I don't have an access to such boxes right now. The RTP >>>proxy itself can be downloaded from: >>> >>>https://demo.portaone.com/~sobomax/PortaSIP/rtpproxy/ >>> >>>Any feedback is greatly appreciated. >>> >>>-Maxim >>>P.S. I've committed it to the HEAD, those with 0.8.11 prerelease >>>please apply the following patch: >>> >>>https://demo.portaone.com/~sobomax/nathelper.diff >>> >>>_______________________________________________ >>>Serusers mailing list >>>serusers(a)lists.iptel.org >>>http://lists.iptel.org/mailman/listinfo/serusers >>> >>> >>>

------------------------------------------------------------------------ > >_______________________________________________ >Serusers mailing list >serusers(a)lists.iptel.org >http://lists.iptel.org/mailman/listinfo/serusers

Maxim Sobolev

10 Jul 10 Jul

8:37 a.m.

New subject: [Serusers] nathelper updated to support RTP proxy

Try to disable VAD (aka silence surpression or compression) in Nortel if it supports that, it might help. -Maxim Ricardo Villa wrote:

...

From my observations of the rtpproxy output, I notice that when the call is

Oh, sorry, I've misunderstood your problem. What kind of device UA1 is? Can you please try the same with ATAs on both ends? -Maxim Ricardo Villa wrote: >Hi Maxim, > >Sorry but I don't understand what you mean. Ser and RTP Proxy are on a >machine with IP Address=192.168.1.111. The WAN interface of the NAT

Router

>is 192.168.1.1. What exactly should I do? > >

UA1---SER(192.168.1.111)---(192.168.1.1)NAT(192.168.0.1)----ATA186(192.168.0

though >>the SDP is rewritten properly. >> >>My test setup is like this: >> >>UA1(192.168.1.10) --

>SER(192.168.1.111)---(192.168.1.1)NAT(192.168.0.1)--ATA186(192.168.0.15) > >>I have included the "-f" output from the rtpproxy plus 4 ngrep files. >> >>1. success_from_internet.txt --> good call from UA1 to ATA186 >>2. fail_from_internet.txt ---> no audio call from UA1 to ATA186 >>3. success_from_nat.txt ----> good call from ATA186 to UA1 >>4. fail_from_nat.txt ---> no audio call from ATA186 to UA1 >> >>Please let me know how else we can troubleshoot this. >> >>Thanks, >>Ricardo >> >> >> >>----- Original Message ----- >>From: "Maxim Sobolev" <sobomax(a)portaone.com> >>To: <serusers(a)lists.iptel.org> >>Cc: <serdev(a)lists.iptel.org> >>Sent: Sunday, July 06, 2003 12:16 PM >>Subject: [Serusers] nathelper updated to support RTP proxy >> >> >> >> >> >>>Folks, >>> >>>Today I've updated nathelper module to support RTP proxy. It would >>>be nice if somebody can test it on platforms other than FreeBSD, >>>because I don't have an access to such boxes right now. The RTP >>>proxy itself can be downloaded from: >>> >>>https://demo.portaone.com/~sobomax/PortaSIP/rtpproxy/ >>> >>>Any feedback is greatly appreciated. >>> >>>-Maxim >>>P.S. I've committed it to the HEAD, those with 0.8.11 prerelease >>>please apply the following patch: >>> >>>https://demo.portaone.com/~sobomax/nathelper.diff >>> >>>_______________________________________________ >>>Serusers mailing list >>>serusers(a)lists.iptel.org >>>http://lists.iptel.org/mailman/listinfo/serusers >>> >>> >>>

>------------------------------------------------------------------------ > >>_______________________________________________ >>Serusers mailing list >>serusers(a)lists.iptel.org >>http://lists.iptel.org/mailman/listinfo/serusers

_______________________________________________ Serusers mailing list serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers

Ricardo Villa

10:36 a.m.

New subject: [Serusers] nathelper updated to support RTP proxy

Hi Maxim, The Nortel Client does not support silence suppression. You can take a look at the ngrep traces I sent and you will see that both UAs are transmitting audio to the RTPProxy, but it does not relay it to their destinations. Regards, Ricardo ----- Original Message ----- From: "Maxim Sobolev" <sobomax(a)portaone.com> To: "Ricardo Villa" <ricvil(a)epm.net.co> Cc: <serdev(a)lists.iptel.org>rg>; <serusers(a)lists.iptel.org> Sent: Thursday, July 10, 2003 7:37 AM Subject: Re: [Serusers] nathelper updated to support RTP proxy

...

Try to disable VAD (aka silence surpression or compression) in Nortel if it supports that, it might help. -Maxim Ricardo Villa wrote: > Hi Maxim, > > UA1 is the Nortel Networks SIP Client. I did not put it behind a NAT so

...

> to avoid any issues. But I followed your suggestion and swapped it for > another ATA186. It seems to work fine now. Made about 20 calls and all

had

...

> fine audio. Any ideas why other UAs can have problems even though they

are

...

> not behind a NAT?? > >>From my observations of the rtpproxy output, I notice that when the call

...

> successfull I see these two lines: > addr1 filled in > addr2 filled in > > But when there is no audio I only see: > addr1 filled in > > By the way we mainly use ATA186s on our network but there are a handul

...

> others that should coexist if we were to deply the RTPProxy. > > Thanks, > Ricardo > > > > ----- Original Message ----- > From: "Maxim Sobolev" <sobomax(a)portaone.com> > To: "Ricardo Villa" <ricvil(a)epm.net.co> > Cc: <serdev(a)lists.iptel.org>rg>; <serusers(a)lists.iptel.org> > Sent: Wednesday, July 09, 2003 8:11 PM > Subject: Re: [Serusers] nathelper updated to support RTP proxy > > > >>Oh, sorry, I've misunderstood your problem. What kind of device UA1 is? >>Can you please try the same with ATAs on both ends? >> >>-Maxim >> >>Ricardo Villa wrote: >> >> >>>Hi Maxim, >>> >>>Sorry but I don't understand what you mean. Ser and RTP Proxy are on a >>>machine with IP Address=192.168.1.111. The WAN interface of the NAT > > Router > >>>is 192.168.1.1. What exactly should I do? >>> >>> > >

UA1---SER(192.168.1.111)---(192.168.1.1)NAT(192.168.0.1)----ATA186(192.168.0

...

> >>>.15) >>> >>> >>>Thanks, >>>Ricardo >>> >>> >>>----- Original Message ----- >>>From: "Maxim Sobolev" <sobomax(a)portaone.com> >>>To: "Ricardo Villa" <ricvil(a)epm.net.co> >>>Cc: <serusers(a)lists.iptel.org>rg>; <serdev(a)lists.iptel.org> >>>Sent: Wednesday, July 09, 2003 7:18 PM >>>Subject: Re: [Serusers] nathelper updated to support RTP proxy >>> >>> >>> >>> >>>>Try to bind both ser and rtpproxy to the IP address of "WAN"

interface -

...

>>>192.168.0.1 and let me know if it helps or not. >>> >>>-Maxim >>> >>>Ricardo Villa wrote: >>> >>> >>> >>>>Hi Maxim, >>>> >>>>I have tested on 0.8.12dev-t10 installed on RedHat 7.3. >>>> >>>>The results are mixed. Only about 40% of the calls have audio even >> >>though >> >> >>>>the SDP is rewritten properly. >>>> >>>>My test setup is like this: >>>> >>>>UA1(192.168.1.10) -- >

>>SER(192.168.1.111)---(192.168.1.1)NAT(192.168.0.1)--ATA186(192.168.0.15) >>> >>>>I have included the "-f" output from the rtpproxy plus 4 ngrep files. >>>> >>>>1. success_from_internet.txt --> good call from UA1 to ATA186 >>>>2. fail_from_internet.txt ---> no audio call from UA1 to ATA186 >>>>3. success_from_nat.txt ----> good call from ATA186 to UA1 >>>>4. fail_from_nat.txt ---> no audio call from ATA186 to UA1 >>>> >>>>Please let me know how else we can troubleshoot this. >>>> >>>>Thanks, >>>>Ricardo >>>> >>>> >>>> >>>>----- Original Message ----- >>>>From: "Maxim Sobolev" <sobomax(a)portaone.com> >>>>To: <serusers(a)lists.iptel.org> >>>>Cc: <serdev(a)lists.iptel.org> >>>>Sent: Sunday, July 06, 2003 12:16 PM >>>>Subject: [Serusers] nathelper updated to support RTP proxy >>>> >>>> >>>> >>>> >>>> >>>>>Folks, >>>>> >>>>>Today I've updated nathelper module to support RTP proxy. It would >>>>>be nice if somebody can test it on platforms other than FreeBSD, >>>>>because I don't have an access to such boxes right now. The RTP >>>>>proxy itself can be downloaded from: >>>>> >>>>>https://demo.portaone.com/~sobomax/PortaSIP/rtpproxy/ >>>>> >>>>>Any feedback is greatly appreciated. >>>>> >>>>>-Maxim >>>>>P.S. I've committed it to the HEAD, those with 0.8.11 prerelease >>>>>please apply the following patch: >>>>> >>>>>https://demo.portaone.com/~sobomax/nathelper.diff >>>>> >>>>>_______________________________________________ >>>>>Serusers mailing list >>>>>serusers(a)lists.iptel.org >>>>>http://lists.iptel.org/mailman/listinfo/serusers >>>>> >>>>> >>>>> >

>>>>-----------------------------------------------------------------------

...

>> >>>_______________________________________________ >>>Serusers mailing list >>>serusers(a)lists.iptel.org >>>http://lists.iptel.org/mailman/listinfo/serusers > > >

_______________________________________________ Serusers mailing list serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers

Younger Wang

1:25 p.m.

New subject: [Serdev] Re: [Serusers] nathelper updated to support RTP proxy

Use tcpdump or Ethereal to see what happenes is always a good idea. ----- Original Message ----- From: "Ricardo Villa" <ricvil(a)epm.net.co> To: "Maxim Sobolev" <sobomax(a)portaone.com> Cc: <serdev(a)lists.iptel.org>rg>; <serusers(a)lists.iptel.org> Sent: Wednesday, July 09, 2003 7:18 PM Subject: [Serdev] Re: [Serusers] nathelper updated to support RTP proxy

...

Hi Maxim, UA1 is the Nortel Networks SIP Client. I did not put it behind a NAT so

...

to avoid any issues. But I followed your suggestion and swapped it for another ATA186. It seems to work fine now. Made about 20 calls and all

had

...

fine audio. Any ideas why other UAs can have problems even though they

are

...

not behind a NAT?? >From my observations of the rtpproxy output, I notice that when the call

...

successfull I see these two lines: addr1 filled in addr2 filled in But when there is no audio I only see: addr1 filled in By the way we mainly use ATA186s on our network but there are a handul of others that should coexist if we were to deply the RTPProxy. Thanks, Ricardo ----- Original Message ----- From: "Maxim Sobolev" <sobomax(a)portaone.com> To: "Ricardo Villa" <ricvil(a)epm.net.co> Cc: <serdev(a)lists.iptel.org>rg>; <serusers(a)lists.iptel.org> Sent: Wednesday, July 09, 2003 8:11 PM Subject: Re: [Serusers] nathelper updated to support RTP proxy > Oh, sorry, I've misunderstood your problem. What kind of device UA1 is? > Can you please try the same with ATAs on both ends? > > -Maxim > > Ricardo Villa wrote: > > > Hi Maxim, > > > > Sorry but I don't understand what you mean. Ser and RTP Proxy are on

...

> machine with IP Address=192.168.1.111. The WAN interface of the NAT

Router

> is 192.168.1.1. What exactly should I do? > >

UA1---SER(192.168.1.111)---(192.168.1.1)NAT(192.168.0.1)----ATA186(192.168.0

...

> > .15) > > > > > > Thanks, > > Ricardo > > > > > > ----- Original Message ----- > > From: "Maxim Sobolev" <sobomax(a)portaone.com> > > To: "Ricardo Villa" <ricvil(a)epm.net.co> > > Cc: <serusers(a)lists.iptel.org>rg>; <serdev(a)lists.iptel.org> > > Sent: Wednesday, July 09, 2003 7:18 PM > > Subject: Re: [Serusers] nathelper updated to support RTP proxy > > > > > > > >>Try to bind both ser and rtpproxy to the IP address of "WAN"

interface -

...

192.168.0.1 and let me know if it helps or not. -Maxim Ricardo Villa wrote: >Hi Maxim, > >I have tested on 0.8.12dev-t10 installed on RedHat 7.3. > >The results are mixed. Only about 40% of the calls have audio even

though >>the SDP is rewritten properly. >> >>My test setup is like this: >> >>UA1(192.168.1.10) --

SER(192.168.1.111)---(192.168.1.1)NAT(192.168.0.1)--ATA186(192.168.0.15) >> >>I have included the "-f" output from the rtpproxy plus 4 ngrep files. >> >>1. success_from_internet.txt --> good call from UA1 to ATA186 >>2. fail_from_internet.txt ---> no audio call from UA1 to ATA186 >>3. success_from_nat.txt ----> good call from ATA186 to UA1 >>4. fail_from_nat.txt ---> no audio call from ATA186 to UA1 >> >>Please let me know how else we can troubleshoot this. >> >>Thanks, >>Ricardo >> >> >> >>----- Original Message ----- >>From: "Maxim Sobolev" <sobomax(a)portaone.com> >>To: <serusers(a)lists.iptel.org> >>Cc: <serdev(a)lists.iptel.org> >>Sent: Sunday, July 06, 2003 12:16 PM >>Subject: [Serusers] nathelper updated to support RTP proxy >> >> >> >> >>>Folks, >>> >>>Today I've updated nathelper module to support RTP proxy. It would >>>be nice if somebody can test it on platforms other than FreeBSD, >>>because I don't have an access to such boxes right now. The RTP >>>proxy itself can be downloaded from: >>> >>>https://demo.portaone.com/~sobomax/PortaSIP/rtpproxy/ >>> >>>Any feedback is greatly appreciated. >>> >>>-Maxim >>>P.S. I've committed it to the HEAD, those with 0.8.11 prerelease >>>please apply the following patch: >>> >>>https://demo.portaone.com/~sobomax/nathelper.diff >>> >>>_______________________________________________ >>>Serusers mailing list >>>serusers(a)lists.iptel.org >>>http://lists.iptel.org/mailman/listinfo/serusers >>> >>> >>>

------------------------------------------------------------------------ >> >>_______________________________________________ >>Serusers mailing list >>serusers(a)lists.iptel.org >>http://lists.iptel.org/mailman/listinfo/serusers

_______________________________________________ Serdev mailing list serdev(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serdev

7707

days inactive

7707

days old

sr-users@lists.kamailio.org

Manage subscription

4 comments

3 participants

tags (0)

participants (3)

Maxim Sobolev
Ricardo Villa
Younger Wang