> > Hi, Robert, > > That's well done according to your indication. Thanks so much ! > > That issue is cleared now and do I need to close this JIRA myself ? >
I'm glad to hear that this solved your problem. The typical Jira workflow is for the originator to close the tracker if he accepts the proposed resolution. > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf > Of Robert Joly > (JIRA) > Sent: Wednesday, June 02, 2010 10:13 PM > To: [email protected] > Subject: [SFtrack] Resolved: (XX-8490) RTP is NATed to public > IP rather thaninside IPSEC tunnel between two SIPX when > site-to-site calling. > > > [ > http://track.sipfoundry.org/browse/XX-8490?page=com.atlassian. jira.plugin.sy > stem.issuetabpanels:all-tabpanel ] > > Robert Joly resolved XX-8490. > ----------------------------- > > Resolution: Configuration Error > Assignee: jun.wen > > Under system->internet calling, you need to describe the full > extent of your extended private network (and that includes > your VPN'd networks). I see that you have done it properly > for the IP addresses but not for the domain names. More > specifically, you need to add *.masplus.net to to the subdomain list. > > > RTP is NATed to public IP rather than inside IPSEC tunnel > between two > > SIPX > when site-to-site calling. > > > ---------------------------------------------------------------------- > > --------------------------------- > > > > Key: XX-8490 > > URL: http://track.sipfoundry.org/browse/XX-8490 > > Project: sipXecs > > Issue Type: Bug > > Components: sipXproxy > > Affects Versions: 4.2.0 > > Environment: Build source from rlease 4.2.1, build 18926, > > Centos > 5.4, through IPSEC tunnel between two HA SIPX servers by > site-to-site call. > > Reporter: jun.wen > > Assignee: jun.wen > > Attachments: sipx-snapshot-mvp01.motomas.net.tar.gz, > > sipXproxy.log, trace.cap > > > > > > The problem is nailed down the RTP path between two ends of > IPSEC tunnel. > It was observed the SIP messages were delivered inside the > IPSEC tunnel but both sipx servers NAted RTP to the its > internet public IP rather than to the IP of IPSEC tunnel. > > -- > This message is automatically generated by JIRA. > - > If you think it was sent incorrectly contact one of the > administrators: > http://track.sipfoundry.org/secure/Administrators.jspa > - > For more information on JIRA, see: > http://www.atlassian.com/software/jira > > > _______________________________________________ > sipxecs-commit mailing list [email protected] > List Archive: http://list.sipfoundry.org/archive/sipxecs-commit > Unsubscribe: > http://list.sipfoundry.org/mailman/listinfo/sipxecs-commit > sipXecs IP PBX -- http://www.sipfoundry.org/ > > _______________________________________________ > sipx-dev mailing list [email protected] List > Archive: http://list.sipfoundry.org/archive/sipx-dev > Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev > sipXecs IP PBX -- http://www.sipfoundry.org/ > _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
