Hi all, While digging through the http://track.sipfoundry.org/browse/XX-7695 issue, I came to notice the following thing: I created a SIP Trunk with sipxbridge-1 SBC route, and selected the Nortel CS1000 ITSP template. The address field for other templates gets populated with some value after selecting the template, but not for this particular one. Here's what happens: when selecting the CS1000 template, the value of the address field (which corresponds to itsp-account/itsp-proxy-address setting) is filled with the default value of the itsp-account/itsp-proxy-domain setting (which in this case is not-defined hence null). The UI validation does not let you leave the address field blank so we can manually write something in there, but the problem is that when forwardingrules.xml is generated, the forwardingrules.vm velocity template uses the itsp-account/itsp-proxy-domain value to output <routeFrom>.....</routeFrom> tag. That's where from the problem of this issue appears (having the itsp-proxy-domain setting value null). In my opinion we have three basic solutions : - either we are using the wrong setting in the velocity template (itsp-proxy-domain instead of itsp-proxy-address) and we should change that. - either we should specify a "please.specify.address" similar value for the itsp-proxy-domain default value. - either we modify the velocity template in order to obtain an empty <routeFrom></routeFrom> tag when the itsp-proxy-domain setting is null.
But maybe the biggest question is why do we have this itsp-proxy-domain setting and what is its purpose ? It's a hidden setting so it couldn't be changed by the user from the UI, and I didn't found direct references to it, besides the thing described above. On the other hand why do we need to fill the value of a A setting from the default value of another B setting instead of just using a default value for the A setting ? Could anyone clear these things for me? Thanks for your answer, Bogdan _______________________________________________ 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/
