Wayne, I've had a bit of decent fun with them. First off call in and ask that they change the port to which they send data to 5080 - this will fall in line with FS's external profile setup in a vanilla environment. Second, the username and password fields are optional, however they are required in order for FS to accept the XML as valid. Also, bandwidth.comdoes not have any usernames/passwords, but will send back a 200OK from an auth request if necessary. Third, take note of the e.164 with leading '+', that screwed with me for a while. While you're on the phone with them you might have them also change the format to not use the leading + to make things a little easier. On Tue, Aug 30, 2011 at 1:25 PM, Wayne <wayne@hamilton.net> wrote:
Does anyone have a setup with bandwidth.com?
The example on the wiki has a username and password. I didn't receive a username and password form bandwidth.com. Just setup a sip peer and have an IP address. If I send calls to freeswitch from the peer I get Rejected by acl "domains". Falling back to Digest auth. Looks like they are sending it on port 5060. I'm sure the rejected by acl is the most asked question but I have been unable to find the answer.
Thanks Wayne
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org