[FS-8363] Vitelity (Gateway) Registers but cannot dial out Created: 19/Oct/15  Updated: 19/Oct/15  Resolved: 19/Oct/15

Status: Resolved
Project: FreeSWITCH
Component/s: Configuration
Affects Version/s: 1.6.0
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: Johny Rodriguez Assignee: Brian West
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment: Windows Server 2008 R2

Attachments: Text File freeswitch.log     Text File freeswitch.log     XML File vitelity.xml    
CPU Architecture:
Microsoft Windows
Microsoft Visual Studio
Compiler Version: 2015 Full
FreeSWITCH GIT Revision: 1.6
GIT Master Revision hash:: df8d8713fedc1f836bde954bc18d827f13e6038a
FSS Support Agreement Customer Number and Company name: iMerchant Systems - Gold FSA Agreement, we don't see any customer number.

We can register our Vitelity account and get Status=REGED. However when we try to dial out we get the busy signal and the attached log activity. I will also attach the Vitality external profile we created. Thank you.

Comment by Brian West [ 19/Oct/15 ]
remove external-ipv6.xml or see the commit associated with this issue, this will resolve what you hit, notice your invite going out has ipv6.
Comment by Johny Rodriguez [ 19/Oct/15 ]
I removed external-ipv6.xml. Sorry about that. I am still not having success though. Attached is the log. What can I search for to pull up the existing issue on this?
Comment by Brian West [ 19/Oct/15 ]
Change the default password for one in vars.xml, then join our mailing lists at lists.freeswitch.org for further assistance. This is not a bug in FreeSWITCH bug a configuration issue. (The IPv6 issue was real, I had known about it for a week or two but didn't around to fixing it.)

Generated at Sat Jul 20 05:32:56 CDT 2019 using Jira 8.1.0#801000-sha1:2e1cd1bb771978cda2c5e8f3f10539ab180613f6.