Just for testing purposes, I did enter the user-ID as an alias and ... worked like a charm, which at least Removes some of my headaches. Thank you all for the great advice.
Now on to outbound calling. -----Ursprüngliche Nachricht----- Von: Tony Graziano [mailto:tgrazi...@myitdepartment.net] Gesendet: Mittwoch, 23. Juni 2010 18:55 An: Picher, Michael Cc: maybelater; sipx-users@list.sipfoundry.org Betreff: Re: [sipx-users] DID / cannot complete calls On Wed, Jun 23, 2010 at 12:48 PM, Picher, Michael <mpic...@cmctechgroup.com> wrote: > Usually what we do is leave the user with a regular extension and then > add the DID as an alias on the user account... > > This does work. > >> -----Original Message----- >> From: sipx-users-boun...@list.sipfoundry.org [mailto:sipx-users- >> boun...@list.sipfoundry.org] On Behalf Of maybelater >> Sent: Wednesday, June 23, 2010 12:46 PM >> To: sipx-users@list.sipfoundry.org >> Subject: [sipx-users] DID / cannot complete calls >> >> Hi, >> >> finally got sipx working. >> Now I want to setup DID for inbound calling. >> >> I am currently testing with an account from sipgate.de >> >> When I forward the incoming calls from the sipxbridge >> To an extension-alias (ex. 2000) it works well. >> >> However, in later use every extension is getting a complete >> Pstn (DID) number. >> >> As I understand, I therefore leave the field for >> "Incoming calls destination" blank so that sipx checks if any alias >> Exists for the called DID and routes the call to it. >> >> This does not work... >> (also I cannot call outbound, but that's the next construction > site...) >> One step at a time... This means you are not putting in the alias in the format the provider is sending. tail the sipxproxy.log and maker a call, then look back and see what is in the invite. example: 4345551212 14345551212 +14345551212 094345551212 are different DID number strings that could be sent by different trunk providers. The only "real" correct one is +14345551212, but not all providers are the same. It varies. You could also ask the provider what they are sending. If they are sending the "account number" in the invite (sending the DID in the TO header instead), then they either need to change that or you need to find another provider, or use a different SBC. When you set it to "catch all" calls coming in, it doesn't inspect the INVITE. That's an important thing to KNOW WHAT THE PROVIDER IS SENDING. >> >> Thx in advance >> regards >> >> _______________________________________________ >> sipx-users mailing list sipx-users@list.sipfoundry.org >> List Archive: http://list.sipfoundry.org/archive/sipx-users >> Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users >> sipXecs IP PBX -- http://www.sipfoundry.org/ > _______________________________________________ > sipx-users mailing list sipx-users@list.sipfoundry.org > List Archive: http://list.sipfoundry.org/archive/sipx-users > Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users > sipXecs IP PBX -- http://www.sipfoundry.org/ > -- ====================== Tony Graziano, Manager Telephone: 434.984.8430 sip: tgrazi...@voice.myitdepartment.net Fax: 434.984.8431 Email: tgrazi...@myitdepartment.net LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 sip: helpd...@voice.myitdepartment.net Fax: 434.984.8427 Helpdesk Contract Customers: http://www.myitdepartment.net/gethelp/ Why do mathematicians always confuse Halloween and Christmas? Because 31 Oct = 25 Dec. _______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
