Given this is 'Open Source' would it be possible to get some detail providing which ITSP depends upon what 'hack' and the Protocol violation.
We who pay the ITSPs may have some influence with them. Don McIlvin -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of WORLEY, Dale R (Dale) Sent: Wednesday, June 16, 2010 1:32 PM To: [email protected]; 'Tony Graziano'; 'M. Ranganathan' Cc: [email protected] Subject: Re: [sipx-users] Tightening up sipxbridge behavior ________________________________________ From: [email protected] [[email protected]] On Behalf Of Martin Steinmann [[email protected]] We have the same problem in Europe and actually there now is a fix for this particular issue in the builds provided by Douglas. Incoming call routing based on TO field is configurable in sipXconfig. While I am told it is very bad behavior, it is done by a major ITSP in Europe. _______________________________________________ We do need to keep our eyes open in regard to the state of the market, and apply pressure to the ITSPs when possible. Clearly, if a significant market is dominated by badly-behaved ITSPs, there is not much we can do and still sell the product. But once a significant number of well-behaved ITSPs are available and competitive, we need to pressure the customers to use them, to apply pressure to the badly-behaved ITSPs to clean up their acts. Dale _______________________________________________ sipx-users mailing list [email protected] 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/ "The information in this electronic mail message is the sender's confidential business and may be legally privileged. It is intended solely for the addressee(s). Access to this internet electronic mail message by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful." "The sender believes that this E-mail and any attachments were free of any virus, worm, Trojan horse, and/or malicious code when sent. This message and its attachments could have been infected during transmission. By reading the message and opening any attachments, the recipient accepts full responsibility for taking protective and remedial action about viruses and other defects. The sender's employer is not liable for any loss or damage arising in any way from this message or its attachments." [v1.0.07.109] _______________________________________________ sipx-users mailing list [email protected] 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/
