On Wed, Apr 1, 2009 at 6:35 PM, M. Ranganathan <[email protected]> wrote: > On Wed, Apr 1, 2009 at 6:30 PM, M. Ranganathan <[email protected]> wrote: >> On Wed, Apr 1, 2009 at 6:15 PM, Grant Lang >> <[email protected]> wrote: >>> Hi, >>> >>> Sure, sorry >>> >>> <?xml version="1.0" ?> >>> <sipxbridge-config >>> xmlns="http://www.sipfoundry.org/sipX/schema/xml/sipxbridge-00-00";> >>> <bridge-configuration> >>> <global-address>203.97.95.xxx</global-address> >>> <global-port>5060</global-port> >>> <external-address>10.1.2.11</external-address> >>> <external-port>5080</external-port> >>> <local-address>10.1.2.11</local-address> >>> <local-port>5090</local-port> >>> <sipx-proxy-domain>FQHN</sipx-proxy-domain> >>> <stun-server-address>stun01.sipphone.com</stun-server-address> >>> <sip-keepalive-seconds>20</sip-keepalive-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> >>> <log-level>INFO</log-level> >>> <log-directory>/var/log/sipxpbx/</log-directory> >>> </bridge-configuration> >>> <itsp-account> >>> <itsp-proxy-domain>202.180.76.166</itsp-proxy-domain> >>> <user-name>099744735</user-name> >>> <password>password</password> >>> <itsp-proxy-address>202.180.76.166</itsp-proxy-address> >>> <itsp-proxy-listening-port>0</itsp-proxy-listening-port> >>> <itsp-transport>UDP</itsp-transport> >>> <use-global-addressing>true</use-global-addressing> >>> <strip-private-headers>false</strip-private-headers> >>> <default-asserted-identity>true</default-asserted-identity> >>> <register-on-initialization>true</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> >>> <itsp-account> >>> <itsp-proxy-domain>202.180.76.166</itsp-proxy-domain> >>> <user-name>079297025</user-name> >>> <password>password</password> >>> <itsp-proxy-address>202.180.76.166</itsp-proxy-address> >>> <itsp-proxy-listening-port>0</itsp-proxy-listening-port> >>> <itsp-transport>UDP</itsp-transport> >>> <use-global-addressing>true</use-global-addressing> >>> <strip-private-headers>false</strip-private-headers> >>> <default-asserted-identity>true</default-asserted-identity> >>> <register-on-initialization>true</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> >>> >>> >>> Thank you >>> Grant >> >> >> You can see what the problem is because both your accounts have the >> same ITSP domain. The way sipxbridge picks the specific ITSP to route >> through depends up on request URI and From header. The From header of >> the request is determined from the Dial plan. >> >> Right now the dial plan cannot support what you want because the >> Domain maps you to a dial plan. You can essentially have only one user >> name per ITSP domain. Thats the JIRA issue I referred you to earlier. > > > Sorry, I had meant trunking gateway definition (not dial plan) that > rewrites the From header. Please excuse the confusion. > > If you have two of them with the same proxy domain, you will not be > able to select one or the other. > > Thats the issue described in http://track.sipfoundry.org/browse/XECS-2283 >
Another point to note : Please set your caller-id to a specific value when you set up your trunking gateway. Go to the advanced section and select use...@itsp-domain That determines what account gets selected. However for a given ITSP domain, you can select only one account at present. Ranga > >> >>> >>> ________________________________________ >>> From: Melcon Moraes [[email protected]] >>> Sent: Thursday, 2 April 2009 11:08 a.m. >>> To: Grant Lang >>> Cc: M. Ranganathan; [email protected] >>> Subject: Re: [sipx-users] SipXecs 3.11.12 Gateway vs Dialing Rulles >>> Error/Bug >>> >>> The way you obfuscated the XML gives a wrong impression that you're >>> using the same username for both ITSP Accounts. >>> >>> Can that be assumed as user1 for the first <itsp-account /> block and >>> user2 for the second? >>> >>> (Just to make it clear to everyone.) >>> >>> -MM >>> >>> >>> On Wed, Apr 1, 2009 at 7:02 PM, Grant Lang >>> <[email protected]> wrote: >>>> Hi, >>>> >>>> Here it is: >>>> >>>> <?xml version="1.0" ?> >>>> <sipxbridge-config >>>> xmlns="http://www.sipfoundry.org/sipX/schema/xml/sipxbridge-00-00";> >>>> <bridge-configuration> >>>> <global-address>203.97.95.xxx</global-address> >>>> <global-port>5060</global-port> >>>> <external-address>10.1.2.11</external-address> >>>> <external-port>5080</external-port> >>>> <local-address>10.1.2.11</local-address> >>>> <local-port>5090</local-port> >>>> <sipx-proxy-domain>FQHN</sipx-proxy-domain> >>>> <stun-server-address>stun01.sipphone.com</stun-server-address> >>>> <sip-keepalive-seconds>20</sip-keepalive-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> >>>> <log-level>INFO</log-level> >>>> <log-directory>/var/log/sipxpbx/</log-directory> >>>> </bridge-configuration> >>>> <itsp-account> >>>> <itsp-proxy-domain>202.180.76.166</itsp-proxy-domain> >>>> <user-name>username</user-name> >>>> <password>password</password> >>>> <itsp-proxy-address>202.180.76.166</itsp-proxy-address> >>>> <itsp-proxy-listening-port>0</itsp-proxy-listening-port> >>>> <itsp-transport>UDP</itsp-transport> >>>> <use-global-addressing>true</use-global-addressing> >>>> <strip-private-headers>false</strip-private-headers> >>>> <default-asserted-identity>true</default-asserted-identity> >>>> <register-on-initialization>true</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> >>>> <itsp-account> >>>> <itsp-proxy-domain>202.180.76.166</itsp-proxy-domain> >>>> <user-name>username</user-name> >>>> <password>password</password> >>>> <itsp-proxy-address>202.180.76.166</itsp-proxy-address> >>>> <itsp-proxy-listening-port>0</itsp-proxy-listening-port> >>>> <itsp-transport>UDP</itsp-transport> >>>> <use-global-addressing>true</use-global-addressing> >>>> <strip-private-headers>false</strip-private-headers> >>>> <default-asserted-identity>true</default-asserted-identity> >>>> <register-on-initialization>true</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> >>>> >>>> Thank you >>>> Grant >>>> >>>> ________________________________________ >>>> From: M. Ranganathan [[email protected]] >>>> Sent: Thursday, 2 April 2009 10:12 a.m. >>>> To: Grant Lang >>>> Cc: Melcon Moraes; [email protected] >>>> Subject: Re: [sipx-users] SipXecs 3.11.12 Gateway vs Dialing Rulles >>>> Error/Bug >>>> >>>> On Wed, Apr 1, 2009 at 4:32 PM, Grant Lang >>>> <[email protected]> wrote: >>>>> Hi, >>>>> >>>>> Essentially top of the Devices/Gateway list which in turn alters the >>>>> position in the sipxbridge.xml file etc. >>>>> >>>>> Cheers >>>>> Grant >>>> >>>> Could I request you to post the contents of etc/sipxpbx/sipxbridge.xml >>>> after removing passwords. >>>> >>>> Thanks >>>> >>>> >>>>> >>>>> ________________________________________ >>>>> From: Melcon Moraes [[email protected]] >>>>> Sent: Thursday, 2 April 2009 9:23 a.m. >>>>> To: Grant Lang >>>>> Cc: Damian Krzeminski; [email protected] >>>>> Subject: Re: [sipx-users] SipXecs 3.11.12 Gateway vs Dialing Rulles >>>>> Error/Bug >>>>> >>>>> When you say "gateway is at the top of", are you refering to the >>>>> Gateways list at Devices/Gateways or the list inside your Local >>>>> Diaplan rule at System/Dialplan ? >>>>> >>>>> -MM >>>>> >>>>> On Wed, Apr 1, 2009 at 5:01 PM, Grant Lang >>>>> <[email protected]> wrote: >>>>>> Hi, >>>>>> >>>>>> Yes you are correct Local Auckland has an area code of 9 and Tauranga >>>>>> has an area code of 7. >>>>>> >>>>>> My ITSP allows you to have local numbers in each area and separate >>>>>> registrations for them, so you can register the Tauranga number as a >>>>>> gateway and the Auckland one as a separate gateway, although both >>>>>> registrations go to the same ITSP. >>>>>> >>>>>> What happens when I dial using that configuration though is the call >>>>>> gets routed out the gateway at the top of the list, so when I dial a >>>>>> Tauranga number (07) if the Auckland gateway is at the top of the bridge >>>>>> then the call goes through the ITSP as an Auckland number and doesnt >>>>>> take advantage of least cost routing, i.e. coming out on the Tauranga >>>>>> PSTN. >>>>>> >>>>>> Does that make sense and did it help? >>>>>> >>>>>> Cheers >>>>>> Grant >>>>>> >>>>>> ________________________________________ >>>>>> From: [email protected] >>>>>> [[email protected]] On Behalf Of Damian Krzeminski >>>>>> [[email protected]] >>>>>> Sent: Thursday, 2 April 2009 8:44 a.m. >>>>>> To: [email protected] >>>>>> Subject: Re: [sipx-users] SipXecs 3.11.12 Gateway vs Dialing Rulles >>>>>> Error/Bug >>>>>> >>>>>> Scott Lawrence wrote: >>>>>>> On Thu, 2009-04-02 at 07:58 +1300, Grant Lang wrote: >>>>>>>> Hi, >>>>>>>> Thanks for the reply. >>>>>>>> I have a suggestion, what if I added entries into the host file and >>>>>>>> created separate entries for the ITSP but pointed to the same ITSP? >>>>>>>> For example >>>>>>>> 202.67.162.1 a.itsp.com >>>>>>>> 202.67.162.1 b.itsp.com >>>>>>>> >>>>>>>> And then in each Gateway pointed the gateway to that host? >>>>>>>> >>>>>>>> I am not sure that would work because the fallbackrules.xml resolves >>>>>>>> the itsp domain name and puts an IP Address into the fallbackrules.xml >>>>>>>> file? >>>>>>>> >>>>>>>> Is there a possibility in either case that I could use an external >>>>>>>> rules file and if so how would I configure that? >>>>>>>> >>>>>>>> Thanks for your help. >>>>>>>> Grant >>>>>>>> >>>>>>>> <?xml version="1.0" encoding="UTF-8"?> >>>>>>>> <mappings >>>>>>>> xmlns="http://www.sipfoundry.org/sipX/schema/xml/fallback-00-00";> >>>>>>>> <hostMatch> >>>>>>>> <hostPattern>FQDN</hostPattern> >>>>>>>> <hostPattern>FQHN</hostPattern> >>>>>>>> <hostPattern>HostName</hostPattern> >>>>>>>> <hostPattern>10.1.2.11</hostPattern> >>>>>>>> <userMatch> >>>>>>>> <!--Local Auckland--> >>>>>>>> <description>Local Auckland dialing</description> >>>>>>>> <userPattern>909.</userPattern> >>>>>>>> <userPattern>99.</userPattern> >>>>>>>> <transform> >>>>>>>> <user>09{vdigits}</user> >>>>>>>> <host>202.180.76.166</host> >>>>>>>> <headerparams>route=10.1.2.11:5090</headerparams> >>>>>>>> <headerparams>expires=60</headerparams> >>>>>>>> <fieldparams>q=0.9</fieldparams> >>>>>>>> </transform> >>>>>>>> </userMatch> >>>>>>>> <userMatch> >>>>>>>> <!--Local Tauranga--> >>>>>>>> <description>Local Tauranga Dialing</description> >>>>>>>> <userPattern>907.</userPattern> >>>>>>>> <transform> >>>>>>>> <user>07{vdigits}</user> >>>>>>>> <host>202.180.76.166</host> >>>>>>>> <headerparams>route=10.1.2.11:5090</headerparams> >>>>>>>> <headerparams>expires=60</headerparams> >>>>>>>> <fieldparams>q=0.9</fieldparams> >>>>>>>> </transform> >>>>>>>> </userMatch> >>>>>>>> </hostMatch> >>>>>>>> </mappings> >>>>>>> >>>>>>> That looks correct. >>>>>>> >>>>>>> I think you should get call traces of calls that work and calls that >>>>>>> don't and take a snapshot. >>>>>>> >>>>>>> Don't jump to conclusions about what's happening >>>>>>> >>>>>> >>>>>> I does look OK: but I am not sure if I understand your setup. >>>>>> Looks like you have 2 rules "Local Auckland" and "Local Tauranga". >>>>>> They both send calls to the same physical gateway (202.180.76.166) >>>>>> through >>>>>> the same SBC (10.1.2.11:5090). The only difference between the 2 gateways >>>>>> are inserted prefixes. >>>>>> >>>>>> How is it different form what you expected? >>>>>> D. >>>>>> >>>>>> _______________________________________________ >>>>>> sipx-users mailing list >>>>>> [email protected] >>>>>> List Archive: http://list.sipfoundry.org/archive/sipx-users >>>>>> Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users >>>>>> _______________________________________________ >>>>>> sipx-users mailing list >>>>>> [email protected] >>>>>> List Archive: http://list.sipfoundry.org/archive/sipx-users >>>>>> Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users >>>>>> >>>>> _______________________________________________ >>>>> sipx-users mailing list >>>>> [email protected] >>>>> List Archive: http://list.sipfoundry.org/archive/sipx-users >>>>> Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users >>>>> >>>> >>>> >>>> >>>> -- >>>> M. Ranganathan >> >> >> >> -- >> M. Ranganathan >> > > > > -- > M. Ranganathan > -- M. Ranganathan _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
