help nat problems

classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|

help nat problems

troxlinux

Hi list, I want to comment some problems of nat that I have, I have two connected remote UAC in a same location

UAC 202 REMOTE A 
UAC 123 REMOTE A

if the UAC 123 calls to UAC 202 there is not bidirectional audio

UAC 204 REMOTE B
UAC 122 REMOTE C

if the UAC 122 calls to UAC 202 if there is bidirectional audio

some help like I can solve this problem?, the remote clients in site A they are behind a nat symetrics

I am using rtpproxy version 1.1 and openser 1.3.2


log sip

U +2.975758 190.212.49.86:58944 -> 190.184.22.152:5060
SIP/2.0 200 OK
Via: SIP/2.0/UDP 190.184.22.152:5060;branch=z9hG4bK74f3.13c6ec23.0
Via: SIP/2.0/UDP 192.168.10.37:5060;rport=63451;received=190.212.49.86;branch=z9hG4bK33571797d7d31cb0

Record-Route: <sip:190.184.22.152;lr=on;ftag=0966ab4346392f45>
From: "ricardo-elim" <[hidden email]>;tag=0966ab4346392f45
To: <[hidden email]>;tag=15c74eb7e1a2ae92
Call-ID: [hidden email]
CSeq: 17345 INVITE
User-Agent: Grandstream GXP2020 1.1.6.16
Contact: <sip:202@192.168.10.40:5064;transport=udp>
Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE,UPDATE,PRACK,MESSAGE
Content-Type: application/sdp
Supported: replaces, timer
Content-Length: 214

v=0
o=202 8000 8000 IN IP4 192.168.10.40
s=SIP Call
c=IN IP4 192.168.10.40
t=0 0
m=audio 5004 RTP/AVP 18 101
a=sendrecv
a=rtpmap:18 G729/8000
a=ptime:20
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-11

#
U +0.000475 190.184.22.152:5060 -> 190.212.49.86:63451
SIP/2.0 200 OK
Via: SIP/2.0/UDP
192.168.10.37:5060;rport=63451;received=190.212.49.86;branch=z9hG4bK33571797d7d31cb0
Record-Route: <sip:190.184.22.152;lr=on;ftag=0966ab4346392f45>
From: "ricardo-elim" <[hidden email]>;tag=0966ab4346392f45
To: <[hidden email]>;tag=15c74eb7e1a2ae92
Call-ID: [hidden email]
CSeq: 17345 INVITE
User-Agent: Grandstream GXP2020 1.1.6.16
Contact: <sip:202@190.212.49.86:58944;transport=udp;nat=yes>
Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE,UPDATE,PRACK,MESSAGE
Content-Type: application/sdp
Supported: replaces, timer
Content-Length: 234
P-hint: onreply_route|force_rtp_proxy
P-hint: Onreply-route - fixcontact

v=0
o=202 8000 8000 IN IP4 192.168.10.40
s=SIP Call
c=IN IP4 190.184.22.152
t=0 0
m=audio 35036 RTP/AVP 18 101
a=sendrecv
a=rtpmap:18 G729/8000
a=ptime:20
a=rtpmap:101
telephone-event/8000
a=fmtp:101 0-11
a=nortpproxy:yes

#
U +0.241543 190.212.49.86:63451 -> 190.184.22.152:5060
ACK sip:202@190.212.49.86:58944;transport=udp;nat=yes SIP/2.0
Via: SIP/2.0/UDP 192.168.10.37:5060;branch=z9hG4bKa26522558c582a68
Route: <sip:190.184.22.152;lr=on;ftag=0966ab4346392f45>
From: "ricardo-elim" <[hidden email]>;tag=0966ab4346392f45
To: <[hidden email]>;tag=15c74eb7e1a2ae92
Contact: <sip:123@192.168.10.37:5060;transport=udp>
Supported: path
Proxy-Authorization: Digest username="123", realm="190.184.22.152", algorithm=MD5, uri="[hidden email]", nonce="49485f8958ba6dc4e39ee5893d15ea3e60ae19ad", response="afb5db07f3a90d4cfc6ea483fd120404"
Call-ID: [hidden email]
CSeq: 17345 ACK
User-Agent: Grandstream BT200 1.1.6.16
Max-Forwards: 70
Allow:
INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE,UPDATE,PRACK
Content-Length: 0


#
U +0.000334 190.184.22.152:5060 -> 190.212.49.86:58944
ACK sip:202@190.212.49.86:58944;transport=udp SIP/2.0
Record-Route: <sip:190.184.22.152;lr=on;ftag=0966ab4346392f45>
Via: SIP/2.0/UDP 190.184.22.152;branch=z9hG4bK74f3.13c6ec23.2
Via: SIP/2.0/UDP 192.168.10.37:5060;rport=63451;received=190.212.49.86;branch=z9hG4bKa26522558c582a68
From: "ricardo-elim" <[hidden email]>;tag=0966ab4346392f45
To: <[hidden email]>;tag=15c74eb7e1a2ae92
Contact: <sip:123@190.212.49.86:63451;transport=udp;nat=yes>
Supported: path
Proxy-Authorization: Digest username="123", realm="190.184.22.152", algorithm=MD5, uri="[hidden email]", nonce="49485f8958ba6dc4e39ee5893d15ea3e60ae19ad", response="afb5db07f3a90d4cfc6ea483fd120404"
Call-ID: [hidden email]
CSeq:
17345 ACK
User-Agent: Grandstream BT200 1.1.6.16
Max-Forwards: 69
Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE,UPDATE,PRACK
Content-Length: 0


#
U +0.383479 190.184.22.152:5060 -> 190.212.49.86:58944
OPTIONS sip:190.212.49.86:58944 SIP/2.0
Via: SIP/2.0/UDP 190.184.22.152:5060;branch=0
From: [hidden email];tag=d7259e51
To: sip:190.212.49.86:58944
Call-ID: [hidden email]
CSeq: 1 OPTIONS
Content-Length: 0


#
U +0.173847 190.212.49.86:58944 -> 190.184.22.152:5060
SIP/2.0 200 OK
Via: SIP/2.0/UDP 190.184.22.152:5060;branch=0
From: [hidden email];tag=d7259e51
To: sip:190.212.49.86:58944;tag=15c74eb7e1a2ae92
Call-ID: [hidden email]
CSeq: 1 OPTIONS
User-Agent: Grandstream GXP2020 1.1.6.16
Contact: <sip:202@192.168.10.40:5064;transport=udp>
Allow:
INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE,UPDATE,PRACK,MESSAGE
Supported: replaces, timer
Content-Length: 0


#
U +0.826048 190.184.22.152:5060 -> 190.212.35.160:50273
OPTIONS sip:190.212.35.160:50273 SIP/2.0
Via: SIP/2.0/UDP 190.184.22.152:5060;branch=0
From: [hidden email];tag=e7259e51
To: sip:190.212.35.160:50273
Call-ID: [hidden email]
CSeq: 1 OPTIONS
Content-Length: 0


#
U +0.192726 190.212.35.160:50273 -> 190.184.22.152:5060
SIP/2.0 200 OK
Via: SIP/2.0/UDP 190.184.22.152:5060;branch=0
From: [hidden email];tag=e7259e51
To: sip:190.212.35.160:50273;tag=c2c330e1c7bae7ba
Call-ID: [hidden email]
CSeq: 1 OPTIONS
User-Agent: Grandstream GXP2000 1.1.6.16
Contact: <sip:203@192.168.0.16:5060;transport=udp;user=phone>
Allow:
INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE,UPDATE,PRACK,MESSAGE
Supported: replaces, timer
Content-Length: 0


#
U +1.807039 192.168.11.1:5060 -> 192.168.11.30:5060
OPTIONS sip:192.168.11.30:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.11.1:5060;branch=0
From: [hidden email];tag=f7259e51
To: sip:192.168.11.30:5060
Call-ID: [hidden email]
CSeq: 1 OPTIONS
Content-Length: 0


regards

rickygm

_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: help nat problems

Iñaki Baz Castillo
2008/12/17 troxlinux <[hidden email]>:

>
> Hi list, I want to comment some problems of nat that I have, I have two
> connected remote UAC in a same location
>
> UAC 202 REMOTE A
> UAC 123 REMOTE A
>
> if the UAC 123 calls to UAC 202 there is not bidirectional audio
>
> UAC 204 REMOTE B
> UAC 122 REMOTE C
>
> if the UAC 122 calls to UAC 202 if there is bidirectional audio
>
> some help like I can solve this problem?, the remote clients in site A they
> are behind a nat symetrics
>
> I am using rtpproxy version 1.1 and openser 1.3.2


Not enough info to suggest a problem cause.
You should inspect the SDP in the INVITE received by the callee and
the 200 OK received by the caller in all the cases, and verify if they
make sense (if you are using RtpProxy for these calls you should see
there the IP of RtpProxy, if not you get unidirectiaonal audio and
so).

Also, being behind symmetric NAT doesn't matter here since you are
using RtpProxy.

Question: Are all your phones in the same network? is the proxy and
RtpProxy behind NAT (I hope not)?



--
Iñaki Baz Castillo
<[hidden email]>
_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: help nat problems

Robert Dyck
In reply to this post by troxlinux
Do you control the UAs at location A? Do they use STUN or are they configured
to masquerade as the router's public address? Both would claim to be
listening on the same IP. Many ( most? ) routers do not support hairpin
routing.

On Wednesday 17 December 2008, troxlinux wrote:

> Hi list, I want to comment some problems of nat that I have, I have two
> connected remote UAC in a same location
>
> UAC 202 REMOTE A
> UAC 123 REMOTE A
>
> if the UAC 123 calls to UAC 202 there is not bidirectional audio
>
> UAC 204 REMOTE B
> UAC 122 REMOTE C
>
> if the UAC 122 calls to UAC 202 if there is bidirectional audio
>
> some help like I can solve this problem?, the remote clients in site A they
> are behind a nat symetrics
>
> I am using rtpproxy version 1.1 and openser 1.3.2
>
>
> log sip
>
> U +2.975758 190.212.49.86:58944 -> 190.184.22.152:5060
> SIP/2.0 200 OK
> Via: SIP/2.0/UDP 190.184.22.152:5060;branch=z9hG4bK74f3.13c6ec23.0
> Via: SIP/2.0/UDP
> 192.168.10.37:5060;rport=63451;received=190.212.49.86;branch=z9hG4bK3357179
>7d7d31cb0
>
> Record-Route: <sip:190.184.22.152;lr=on;ftag=0966ab4346392f45>
> From: "ricardo-elim" <sip:123@190.184.22.152
> <sip%3A123@190.184.22.152>>;tag=0966ab4346392f45
> To: <sip:202@190.184.22.152
> <sip%3A202@190.184.22.152>>;tag=15c74eb7e1a2ae92 Call-ID:
> 4dfa1b96e314c165@192.168.10.37
> CSeq: 17345 INVITE
> User-Agent: Grandstream GXP2020 1.1.6.16
> Contact: <sip:202@192.168.10.40:5064;transport=udp>
> Allow:
> INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE,UPDATE,PRACK,MESS
>AGE Content-Type: application/sdp
> Supported: replaces, timer
> Content-Length: 214
>
> v=0
> o=202 8000 8000 IN IP4 192.168.10.40
> s=SIP Call
> c=IN IP4 192.168.10.40
> t=0 0
> m=audio 5004 RTP/AVP 18 101
> a=sendrecv
> a=rtpmap:18 G729/8000
> a=ptime:20
> a=rtpmap:101 telephone-event/8000
> a=fmtp:101 0-11
>
> #
> U +0.000475 190.184.22.152:5060 -> 190.212.49.86:63451
> SIP/2.0 200 OK
> Via: SIP/2.0/UDP
>
> 192.168.10.37:5060;rport=63451;received=190.212.49.86;branch=z9hG4bK3357179
>7d7d31cb0 Record-Route: <sip:190.184.22.152;lr=on;ftag=0966ab4346392f45>
> From: "ricardo-elim" <sip:123@190.184.22.152
> <sip%3A123@190.184.22.152>>;tag=0966ab4346392f45
> To: <sip:202@190.184.22.152
> <sip%3A202@190.184.22.152>>;tag=15c74eb7e1a2ae92 Call-ID:
> 4dfa1b96e314c165@192.168.10.37
> CSeq: 17345 INVITE
> User-Agent: Grandstream GXP2020 1.1.6.16
> Contact: <sip:202@190.212.49.86:58944;transport=udp;nat=yes>
> Allow:
> INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE,UPDATE,PRACK,MESS
>AGE Content-Type: application/sdp
> Supported: replaces, timer
> Content-Length: 234
> P-hint: onreply_route|force_rtp_proxy
> P-hint: Onreply-route - fixcontact
>
> v=0
> o=202 8000 8000 IN IP4 192.168.10.40
> s=SIP Call
> c=IN IP4 190.184.22.152
> t=0 0
> m=audio 35036 RTP/AVP 18 101
> a=sendrecv
> a=rtpmap:18 G729/8000
> a=ptime:20
> a=rtpmap:101
>  telephone-event/8000
> a=fmtp:101 0-11
> a=nortpproxy:yes
>
> #
> U +0.241543 190.212.49.86:63451 -> 190.184.22.152:5060
> ACK sip:202@190.212.49.86:58944;transport=udp;nat=yes SIP/2.0
> Via: SIP/2.0/UDP 192.168.10.37:5060;branch=z9hG4bKa26522558c582a68
> Route: <sip:190.184.22.152;lr=on;ftag=0966ab4346392f45>
> From: "ricardo-elim" <sip:123@190.184.22.152
> <sip%3A123@190.184.22.152>>;tag=0966ab4346392f45
> To: <sip:202@190.184.22.152
> <sip%3A202@190.184.22.152>>;tag=15c74eb7e1a2ae92 Contact:
> <sip:123@192.168.10.37:5060;transport=udp>
> Supported: path
> Proxy-Authorization: Digest username="123", realm="190.184.22.152",
> algorithm=MD5, uri="sip:202@190.184.22.152
> <sip%3A202@190.184.22.152>",
> nonce="49485f8958ba6dc4e39ee5893d15ea3e60ae19ad",
> response="afb5db07f3a90d4cfc6ea483fd120404"
> Call-ID: 4dfa1b96e314c165@192.168.10.37
> CSeq: 17345 ACK
> User-Agent: Grandstream BT200 1.1.6.16
> Max-Forwards: 70
> Allow:
>  INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE,UPDATE,PRACK
> Content-Length: 0
>
>
> #
> U +0.000334 190.184.22.152:5060 -> 190.212.49.86:58944
> ACK sip:202@190.212.49.86:58944;transport=udp SIP/2.0
> Record-Route: <sip:190.184.22.152;lr=on;ftag=0966ab4346392f45>
> Via: SIP/2.0/UDP 190.184.22.152;branch=z9hG4bK74f3.13c6ec23.2
> Via: SIP/2.0/UDP
> 192.168.10.37:5060;rport=63451;received=190.212.49.86;branch=z9hG4bKa265225
>58c582a68 From: "ricardo-elim" <sip:123@190.184.22.152
> <sip%3A123@190.184.22.152>>;tag=0966ab4346392f45
> To: <sip:202@190.184.22.152
> <sip%3A202@190.184.22.152>>;tag=15c74eb7e1a2ae92 Contact:
> <sip:123@190.212.49.86:63451;transport=udp;nat=yes>
> Supported: path
> Proxy-Authorization: Digest username="123", realm="190.184.22.152",
> algorithm=MD5, uri="sip:202@190.184.22.152
> <sip%3A202@190.184.22.152>",
> nonce="49485f8958ba6dc4e39ee5893d15ea3e60ae19ad",
> response="afb5db07f3a90d4cfc6ea483fd120404"
> Call-ID: 4dfa1b96e314c165@192.168.10.37
> CSeq:
>  17345 ACK
> User-Agent: Grandstream BT200 1.1.6.16
> Max-Forwards: 69
> Allow:
> INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE,UPDATE,PRACK
> Content-Length: 0
>
>
> #
> U +0.383479 190.184.22.152:5060 -> 190.212.49.86:58944
> OPTIONS sip:190.212.49.86:58944 SIP/2.0
> Via: SIP/2.0/UDP 190.184.22.152:5060;branch=0
> From: sip:pinger@190.184.22.152 <sip%3Apinger@190.184.22.152>;tag=d7259e51
> To: sip:190.212.49.86:58944
> Call-ID: 1f9f65c1-fcccdef2-674a@190.184.22.152
> CSeq: 1 OPTIONS
> Content-Length: 0
>
>
> #
> U +0.173847 190.212.49.86:58944 -> 190.184.22.152:5060
> SIP/2.0 200 OK
> Via: SIP/2.0/UDP 190.184.22.152:5060;branch=0
> From: sip:pinger@190.184.22.152 <sip%3Apinger@190.184.22.152>;tag=d7259e51
> To: sip:190.212.49.86:58944;tag=15c74eb7e1a2ae92
> Call-ID: 1f9f65c1-fcccdef2-674a@190.184.22.152
> CSeq: 1 OPTIONS
> User-Agent: Grandstream GXP2020 1.1.6.16
> Contact: <sip:202@192.168.10.40:5064;transport=udp>
> Allow:
>
> INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE,UPDATE,PRACK,MESS
>AGE Supported: replaces, timer
> Content-Length: 0
>
>
> #
> U +0.826048 190.184.22.152:5060 -> 190.212.35.160:50273
> OPTIONS sip:190.212.35.160:50273 SIP/2.0
> Via: SIP/2.0/UDP 190.184.22.152:5060;branch=0
> From: sip:pinger@190.184.22.152 <sip%3Apinger@190.184.22.152>;tag=e7259e51
> To: sip:190.212.35.160:50273
> Call-ID: 1f9f65c1-0dccdef2-774a@190.184.22.152
> CSeq: 1 OPTIONS
> Content-Length: 0
>
>
> #
> U +0.192726 190.212.35.160:50273 -> 190.184.22.152:5060
> SIP/2.0 200 OK
> Via: SIP/2.0/UDP 190.184.22.152:5060;branch=0
> From: sip:pinger@190.184.22.152 <sip%3Apinger@190.184.22.152>;tag=e7259e51
> To: sip:190.212.35.160:50273;tag=c2c330e1c7bae7ba
> Call-ID: 1f9f65c1-0dccdef2-774a@190.184.22.152
> CSeq: 1 OPTIONS
> User-Agent: Grandstream GXP2000 1.1.6.16
> Contact: <sip:203@192.168.0.16:5060;transport=udp;user=phone>
> Allow:
>
> INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE,UPDATE,PRACK,MESS
>AGE Supported: replaces, timer
> Content-Length: 0
>
>
> #
> U +1.807039 192.168.11.1:5060 -> 192.168.11.30:5060
> OPTIONS sip:192.168.11.30:5060 SIP/2.0
> Via: SIP/2.0/UDP 192.168.11.1:5060;branch=0
> From: sip:pinger@190.184.22.152 <sip%3Apinger@190.184.22.152>;tag=f7259e51
> To: sip:192.168.11.30:5060
> Call-ID: 1f9f65c1-1dccdef2-974a@192.168.11.1
> CSeq: 1 OPTIONS
> Content-Length: 0
>
>
>
> regards
>
> rickygm



_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

help nat problems

troxlinux
In reply to this post by Iñaki Baz Castillo



2008/12/17 Iñaki Baz Castillo <[hidden email]>



Not enough info to suggest a problem cause.
You should inspect the SDP in the INVITE received by the callee and
the 200 OK received by the caller in all the cases, and verify if they
make sense (if you are using RtpProxy for these calls you should see
there the IP of RtpProxy, if not you get unidirectiaonal audio and
so).

Also, being behind symmetric NAT doesn't matter here since you are
using RtpProxy.

Question: Are all your phones in the same network? is the proxy and
RtpProxy behind NAT (I hope not)?

the extension 123 and 202 is in the same netwotk behind a symmetric nat and my server this in another network and he has an ip public .

the problem is that when those extensions call there is not you bidirectional audio, alone in one of them


I see in the sdp of the message that the proxy puts me an a=nortpproxy:yes and not you because!

ideas as solving this problem?

v=0 
o=202 8000 8000 IN IP4 192.168.10.40
s=SIP Call
c=IN IP4 190.184.22.152
t=0 0
m=audio 35036 RTP/AVP 18 101
a=sendrecv
a=rtpmap:18 G729/8000
a=ptime:20
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-11
a=nortpproxy:yes

 
regards

rickygm


_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: help nat problems

troxlinux
In reply to this post by Robert Dyck
the telephones are behind a nat symmetric, they have in the network a router thomson speedtouch that doesn't have ip it public and that it masquerade the internal network to leave to internet ...


will there be some solution for this type of networks with nat symmetrics?

best regardss

rickygm

2008/12/17 Robert Dyck <[hidden email]>
Do you control the UAs at location A? Do they use STUN or are they configured
to masquerade as the router's public address? Both would claim to be
listening on the same IP. Many ( most? ) routers do not support hairpin
routing.



_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: help nat problems

Iñaki Baz Castillo
2008/12/18 troxlinux <[hidden email]>:
> the telephones are behind a nat symmetric, they have in the network a router
> thomson speedtouch that doesn't have ip it public and that it masquerade the
> internal network to leave to internet ...
>
>
> will there be some solution for this type of networks with nat symmetrics?

I don't know why you insisit on it. Having symmetrics NAT is not a
problem at all if you use RtpProxy, please don't insist more on it
since this is not your problem.
The only problem that symmetric NAT produces it the fact that
symmetric NAT doesn't allow the usage of STUN (which is not your
case), just it.

Maybe your router has SIP ALG enabled?:
  http://www.voip-info.org/wiki/view/Routers+SIP+ALG


--
Iñaki Baz Castillo
<[hidden email]>
_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: help nat problems

troxlinux

ok made the change in the router and I work very well ...

thanks to all, now they call the one to other and they have audio in both senses

regards

rickygm

2008/12/18 Iñaki Baz Castillo <[hidden email]>

I don't know why you insisit on it. Having symmetrics NAT is not a
problem at all if you use RtpProxy, please don't insist more on it
since this is not your problem.
The only problem that symmetric NAT produces it the fact that
symmetric NAT doesn't allow the usage of STUN (which is not your
case), just it.

Maybe your router has SIP ALG enabled?:
 http://www.voip-info.org/wiki/view/Routers+SIP+ALG


--


_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: help nat problems

Iñaki Baz Castillo
El Viernes, 19 de Diciembre de 2008, troxlinux escribió:
> ok made the change in the router and I work very well ...
>
> thanks to all, now they call the one to other and they have audio in both
> senses

But have you learnt how to check if your router has SIP ALG enabled (so you
must dissable it)?


--
Iñaki Baz Castillo

_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: help nat problems

troxlinux
thank you iñaki for the explanation, the problem with the routers that
support alg is that they replace you the ip of the proxy for that
telephone or softphone, very good I articulate

similar to my case, and me thinking that it was problem of the
proxy... every day one learns but

2008/12/20 Iñaki Baz Castillo <[hidden email]>:
>
> But have you learnt how to check if your router has SIP ALG enabled (so you
> must dissable it)?
>
>

regards
--
rickygm

_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users