On Fri, Dec 26, 2008 at 6:48 PM, Arnaldo de Moraes Pereira <[email protected]> wrote: > > > On Wed, Dec 24, 2008 at 5:56 PM, Melcon Moraes <[email protected]> wrote: >> >> On Wed, Dec 24, 2008 at 1:13 AM, M. Ranganathan <[email protected]> wrote: >> > On Tue, Dec 23, 2008 at 7:59 PM, M. Ranganathan <[email protected]> >> > wrote: >> >> On Tue, Dec 23, 2008 at 4:57 PM, Melcon Moraes <[email protected]> >> >> wrote: >> >>> Hi, Ranga. >> >>> >> >> >> >>> Does all this make any sense? >> >> >> >> >> >> Yes it does. I will look at my code. There is possibly a bug. >> > >> > >> > Check out revsion 14358 I fixed an issue which will address this >> > problem you observed. The P-Asserted-Identity header will now contain >> > the ID that the ITSP wishes to see ( it was previously put in the >> > From: header as well -- which was the bug you ran into). >> > >> > The From: header will pass through unmodified. >> > >> > Thanks for catching it. >> > >> >> Very nice Ranga. I'll give it a try. Thank you. >> >> Regarding the other issue, I do use sipxconfig to configure >> sipxbridge. I was just copying/pasting the corresponding generated >> part to the option on the GUI and I did it wrong. I pasted the >> registration part, when what I meant was to paste the one said at the >> e-mail before. >> >> In short, the behaviour is the same, whether I check the "Use public >> address for call setup" or not. > > Debugging this with Melcon, I found out that BackToBackUserAgent.java is > calling setUseGlobalAddressing(true), which happens when itspAccountInfo is > null. > > It seems that sipxbridge couldn't identify the itsp account, hence it > applied the default policy for use-global-addressing, which is set it to > true. For this particular case, it'd be better to have the default to false, > but since sipxbridge's main goal is to communicate with an ITSP, I'd suggest > that it, at least, warns the user when it can't identify the account. > Thoughts? > > What exactly has to match to identify an itsp account?
For outbound calling, the request URI of the inbound request that is received at sipxbridge from the sipx proxy server is used to select the account. The request URI is determined from the Address field of Devices>Gateways>configuration On the other hand, sipxbridge reads a file called etc/sipxpbx/sipxbridge.xml. The domain name of the ITSP account that is in the file is determined by the field : Devices>gateways>ITSP Server domain-name The outbound request URI from sipx proxy that is received by sipxbridge is used to pick the account and send the request on its way to the iTSP. If an account is not found, then you should get back a 404 Not Found. I will look at the trace and post my finidngs here. Ranga > > >> >> Do you need more info on that? >> >> -MM >> >> > >> > Ranga >> > >> > >> >> >> >> >> >>> >> >>> -MM >> >>> >> >>>>> >> >>>>> Please let me know if you need more info. >> >>>>> >> >>>>> Thanks in advance for your time. >> >>>>> >> >>>>> -MM >> >>>>> >> >>>>> _______________________________________________ >> >>>>> 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 >> >> >> > >> > >> > >> > -- >> > 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 > > > > -- > Arnaldo M Pereira > [email protected] > http://www.arnaldopereira.com > -- 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
