Or your plugin will have to reference a db. It reminds me of a couple of itsp's I struggled with in mexico and Australia. Callcentric certainly comes to mind. On Oct 12, 2012 11:25 AM, "Sven Evensen" <sven.even...@onrelay.com> wrote:
> Thanks Tony, you confirmed what I was afraid of. > > And Yes, we are very close to saying we just cannot use this ITSP. > > Our last hope is that we have a plugin where we possibly can intercept the > refer and replace the internal number with the full DID. > Of course some internal numbers might not have a full DID, but we will > have to live with that. > > > On Fri, Oct 12, 2012 at 4:15 PM, Tony Graziano < > tgrazi...@myitdepartment.net> wrote: > >> I do not blame you for not wanting to do it that way. >> >> It would be better to find an ITSP who supports REFER. >> >> If you use sipxbridge and set it up as a trunk it (sipxbridge) will >> handle the refer locally. It would need the ITSP to support re-invite. >> If you set it up as an unmanaged gateway then the proxy will send the >> REFER to the ITSP (or their gateway, etc.), but it sounds like this >> ITSP does not support reinvite AND requires the "Route by To Header". >> Smacks to me of a best case of what not to look for. >> >> There is a way you can route by the to header in sipxbridge as a >> siptrunk. There is not a way that I know of to do this as an unmanaged >> gateway. I'm not sure how hard it would be to add that feature or what >> else would break or become problematic with users who have lots of >> unmanaged gateways out there since it also assumes the gateway >> supports refer and looks at the INVITE and not the TO header. >> >> >> On Fri, Oct 12, 2012 at 10:46 AM, Sven Evensen <sven.even...@onrelay.com> >> wrote: >> > A customer is using an ITSP which does not support re-invite, therefore >> we >> > set it up an unmanaged gateway and REFER is used when doing a transfer. >> If >> > an external call comes through SIP trunk to an AA 200 and the AA does a >> > transfer to say 211, the refer back to the SIP trunk will have refer-to >> as >> > 211 and that is not a number that the SIP trunk knows, it only knows the >> > full DIDs assigned to that trunk. >> > >> > If I program the AA with the full DID of ext 211, then it works. Be we >> do >> > not want internal users to transfer to internal users with full DID. >> > >> > So is there any way we can do externally originated transfer? >> > >> > Thanks, >> > Sven >> > >> > -- >> > >> > Sven Evensen, Operations Consultant >> > >> > OnRelay >> > >> > Elizabeth House │ 39 York Road, London SE1 7NQ, UK │ +44 (0) 207 902 >> 8123 │ >> > mailto:sven.even...@onrelay.com │ www.onrelay.com >> > >> > >> > This electronic message transmission contains information from OnRelay, >> > Ltd., that may be confidential or privileged. The information is >> intended >> > solely for the recipient and use by any other party is not authorised. >> If >> > you are not the intended recipient, be aware that any disclosure, >> copying, >> > distribution or use of the contents of this information or any >> attachment, >> > is prohibited. If you have received this electronic transmission in >> error, >> > please notify us immediately by electronic mail (i...@onrelay.com) and >> > delete this message, along with any attachments, from your computer. >> > Registered in England No 04006093 ¦ Registered Office 1st Floor, 236 >> Gray's >> > Inn Road, London WC1X 8HB >> > >> > >> > >> > _______________________________________________ >> > sipx-users mailing list >> > sipx-users@list.sipfoundry.org >> > List Archive: http://list.sipfoundry.org/archive/sipx-users/ >> >> >> >> -- >> ~~~~~~~~~~~~~~~~~~ >> Tony Graziano, Manager >> Telephone: 434.984.8430 >> sip: tgrazi...@voice.myitdepartment.net >> Fax: 434.465.6833 >> ~~~~~~~~~~~~~~~~~~ >> Linked-In Profile: >> http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 >> Ask about our Internet Fax services! >> ~~~~~~~~~~~~~~~~~~ >> >> Using or developing for sipXecs from SIPFoundry? Ask me about sipX-CoLab >> 2013! >> >> -- >> LAN/Telephony/Security and Control Systems Helpdesk: >> Telephone: 434.984.8426 >> sip: helpd...@voice.myitdepartment.net >> >> Helpdesk Customers: http://myhelp.myitdepartment.net >> Blog: http://blog.myitdepartment.net >> _______________________________________________ >> sipx-users mailing list >> sipx-users@list.sipfoundry.org >> List Archive: http://list.sipfoundry.org/archive/sipx-users/ > > > > > -- > > *Sven Evensen, Operations Consultant* > > *OnRelay* > > Elizabeth House │ 39 York Road, London SE1 7NQ, UK │ +44 (0) 207 902 8123 > │ mailto:sven.even...@onrelay.com <sven.even...@onrelay.com> │ > www.onrelay.com > > > This electronic message transmission contains information from OnRelay, > Ltd., that may be confidential or privileged. The information is intended > solely for the recipient and use by any other party is not authorised. If > you are not the intended recipient, be aware that any disclosure, copying, > distribution or use of the contents of this information or any attachment, > is prohibited. If you have received this electronic transmission in error, > please notify us immediately by electronic mail (i...@onrelay.com) and > delete this message, along with any attachments, from your computer. > Registered in England No 04006093 ¦ Registered Office 1st Floor, 236 Gray's > Inn Road, London WC1X 8HB > > > > _______________________________________________ > sipx-users mailing list > sipx-users@list.sipfoundry.org > List Archive: http://list.sipfoundry.org/archive/sipx-users/ > -- LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 sip: helpd...@voice.myitdepartment.net Helpdesk Customers: http://myhelp.myitdepartment.net Blog: http://blog.myitdepartment.net
_______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
