Hi Tony, The provider can send it as DNID "or not DNID". I was suggested to have DNID set on their side since we are using FreeSwitch under the hood.
1. With DNID not set and Route by To Header not set sipx returns 404 2. With DNID not set and Route by To Header it appears that the call is constantly INVITE'ing to the A record for our domain (as opposed to what the SRV records are saying or handling it locally). 3. With DNID set and Route by To Header not set sipx returns 404 4. With DNID set and Route by To Header it appears that the call is constantly INVITE'ing to the A record for our domain (as opposed to what the SRV records are saying or handling it locally). Cheers, Kris -----Original Message----- From: sipx-users-boun...@list.sipfoundry.org [mailto:sipx-users-boun...@list.sipfoundry.org] On Behalf Of Tony Graziano Sent: Wednesday, 1 December 2010 12:40 PM To: sipx-users@list.sipfoundry.org Subject: Re: [sipx-users] Inbound Route Outbound calls is handled by the "identity". Depending on what the itsp requires, there are different options needed to satisfy that. The pai, preferred asserted identity is not how all itsp's authenticate calls. Normally on a non-authenticated (registration required trunk), this is a non-issue. Let's not confuse did's coming from the pstn to sipx and outbound calls from sipx to the itsp. Did's coming into sipx are handled as a user alias (or dialplan alias to the aa, etc.). If the itsp sends that in the "to" header instead of the the "invite", the gateway on sipx needs to have the box checked (route by to header). I normally "frown" that a itsp is more residentially focused when they do that. As far as the outbound calls once you have the identity solved to send the correct information the itsp needs, try putting the "caller I'd" in an active user account and seeing if the itsp sends it upstream. ============================ Tony Graziano, Manager Telephone: 434.984.8430 Fax: 434.984.8431 Email: tgrazi...@myitdepartment.net LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 Fax: 434.984.8427 Helpdesk Contract Customers: http://www.myitdepartment.net/gethelp/ ----- Original Message ----- From: sipx-users-boun...@list.sipfoundry.org <sipx-users-boun...@list.sipfoundry.org> To: 'Discussion list for users of sipXecs software' <sipx-users@list.sipfoundry.org> Sent: Tue Nov 30 21:26:18 2010 Subject: Re: [sipx-users] Inbound Route How do you handle multiple numbers coming in the same authenticated trunk if you specify the asserted identity? -- Kris Amy Systems Administrator NEXTDC Level 4, 20 Wharf Street BRISBANE QLD 4000 Direct: +61 7 3177 4716 Email: kris....@nextdc.com Web: www.nextdc.com -----Original Message----- From: sipx-users-boun...@list.sipfoundry.org [mailto:sipx-users-boun...@list.sipfoundry.org] On Behalf Of Tony Graziano Sent: Wednesday, 1 December 2010 12:23 PM To: sipx-users@list.sipfoundry.org Subject: Re: [sipx-users] Inbound Route Sorry. Then it is an "asserted identity" change that would be needed. ============================ Tony Graziano, Manager Telephone: 434.984.8430 Fax: 434.984.8431 Email: tgrazi...@myitdepartment.net LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 Fax: 434.984.8427 Helpdesk Contract Customers: http://www.myitdepartment.net/gethelp/ ----- Original Message ----- From: Tony Graziano <tgrazi...@myitdepartment.net> To: sipx-users@list.sipfoundry.org <sipx-users@list.sipfoundry.org> Sent: Tue Nov 30 21:18:19 2010 Subject: Re: [sipx-users] Inbound Route Yes When you create a trunk with no template there is a checkbox to "route by to header". Did you see if it is in your gateway as an option? ============================ Tony Graziano, Manager Telephone: 434.984.8430 Fax: 434.984.8431 Email: tgrazi...@myitdepartment.net LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 Fax: 434.984.8427 Helpdesk Contract Customers: http://www.myitdepartment.net/gethelp/ ----- Original Message ----- From: sipx-users-boun...@list.sipfoundry.org <sipx-users-boun...@list.sipfoundry.org> To: sipx-users@list.sipfoundry.org <sipx-users@list.sipfoundry.org> Sent: Tue Nov 30 21:14:40 2010 Subject: [sipx-users] Inbound Route Hi All, On calls coming in it seems that sipx is matching prefix against the trunk username as opposed to the To field. In this case it will match against 1541 as the prefix. But won't match against 61731774717. Is there anything special to get it to match against the secondary To? Cheers, Kris _______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/ _______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/ _______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/ _______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
