On Mon, Apr 20, 2009 at 9:03 AM, Nikolay Kondratyev <[email protected]> wrote: > Ranga, > Here is the file: > [r...@sipx3 sipxpbx]# cat /etc/sipxpbx/sipxbridge.xml > <?xml version="1.0" ?> > <sipxbridge-config > xmlns="http://www.sipfoundry.org/sipX/schema/xml/sipxbridge-00-00";> > > <bridge-configuration> > <global-address>81.211.30.104</global-address> > <external-address>172.23.19.5</external-address> > <external-port>5080</external-port> > <local-address>172.23.19.5</local-address> > <local-port>5090</local-port> > <sipx-proxy-domain>sipx3.lab.nstel.ru</sipx-proxy-domain> > <sipx-supervisor-host>sipx3.lab.nstel.ru</sipx-supervisor-host> > <sipx-supervisor-xml-rpc-port>8092</sipx-supervisor-xml-rpc-port> > <stun-server-address>stun01.sipphone.com</stun-server-address> > <sip-keepalive-seconds>20</sip-keepalive-seconds> > > <sip-session-timer-interval-seconds>1800</sip-session-timer-interval-seconds >> > <media-keepalive-seconds>1</media-keepalive-seconds> > <xml-rpc-port>8088</xml-rpc-port> > <music-on-hold-support-enabled>false</music-on-hold-support-enabled> > <music-on-hold-address>~~mh~</music-on-hold-address> > <music-on-hold-delay-miliseconds>500</music-on-hold-delay-miliseconds> > > <music-on-hold-supported-codecs>PCMU,PCMA</music-on-hold-supported-codecs> > <log-level>DEBUG</log-level> > <log-directory>/var/log/sipxpbx/</log-directory> > <location-id>1</location-id> > </bridge-configuration> > > <itsp-account> > <itsp-proxy-domain>yate.lab.nstel.ru</itsp-proxy-domain> > <itsp-proxy-address>yate.lab.nstel.ru</itsp-proxy-address> > <itsp-proxy-listening-port>5059</itsp-proxy-listening-port>
Your INVITE will go to yate.lab.nstel.ru:5059 Do a name lookup on that and see what it resolves to. If you have a DNS SRV record for that name, sipxbridge will use that record. > <itsp-transport>UDP</itsp-transport> > <use-global-addressing>false</use-global-addressing> > <strip-private-headers>false</strip-private-headers> > <default-asserted-identity>true</default-asserted-identity> > <register-on-initialization>false</register-on-initialization> > <registration-interval>600</registration-interval> > <sip-keepalive-method>CR-LF</sip-keepalive-method> > <rtp-keepalive-method>NONE</rtp-keepalive-method> > </itsp-account> > > </sipxbridge-config> > [r...@sipx3 sipxpbx]# > > Thanks and regards, > Nikolay. > >> -----Original Message----- >> From: M. Ranganathan [mailto:[email protected]] >> Sent: Monday, April 20, 2009 4:47 PM >> To: Nikolay Kondratyev >> Cc: [email protected] >> Subject: Re: [sipX-dev] sipxbridge sends invite to wrong ip address >> >> On Mon, Apr 20, 2009 at 8:33 AM, Nikolay Kondratyev <[email protected]> wrote: >> > Hi all, >> > >> > >> > >> > I encountered very strange problem. In two words - sipxbridge is sending >> > invite to wrong ipaddress.. >> >> >> It is very likely that you have a mis configured system. >> > >> > Details: >> > >> > I'm trying to use yate as sip-h323 gateway between my test sipx machine >> > (4.1.0-015216) and avaya ip office (because of avaya has problems with >> sip). >> > >> > I'm trying to send calls to yate trough sipxbridge. >> > >> > Yate is running on the same machine as sipx (172.23.19.5), but listens >> on >> > port 5059. >> > >> > In the sipx ui I configured yate as a sip trunk with route throught >> > sipxbridge. >> > >> > >> > >> > When I send call to yate through sipxbridge, sipxbridge sends Invite >> (see >> > attached merged.xml file) to 172.23.19.6:5059 instead of sending it to >> >> >> Post just your etc/sipxbridge.xml (i.e. the configuration file that >> sipxbridge uses ) in response to this mail and I can tell you what is >> wrong. >> >> >> > 172.23.19.5:5059. >> > >> > Dns does resolve a gateway name to correct address. >> > >> > And I actually can not imagine how does this 172.23.19.6 address arise >> at >> > all.. >> > >> > The only thing I can imagine is that some time ago, there was a second >> > ethernet interface on this machine : eth0:0 - 172.23.19.6. >> > >> > But it was removed from the system some time ago. >> > >> > >> > >> > I tried to look at sipxbridge.log, but the only fact that I can see, is >> that >> > sipxbridge sends invite to 172.23.19.6:5059. >> > >> > >> > >> > The whole snapshot is on my ftp: >> > >> > ftp://sipx:[email protected]/sipx-configuration- >> sipx3.lab.nstel.ru.tar.gz >> > >> > >> > >> > Can anybody please take a look? >> >> Please post just etc/sipxbridge.xml >> >> >> >> Ranga >> >> > >> > Thanks in advance, >> > >> > Nikolay. >> > >> > >> > >> > >> > >> > _______________________________________________ >> > sipx-dev mailing list >> > [email protected] >> > List Archive: http://list.sipfoundry.org/archive/sipx-dev >> > Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev >> > >> >> >> >> -- >> M. Ranganathan > > > -- M. Ranganathan _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
