Guest AaronMHopkins Report post Posted 11/25/2018 04:58 PM Greetings, I was able to successfully completed sip registration. I was also able to successfully receive an incoming call using the DID attached to my Voip provider. I have however having difficulty making calls. Please help. Attached find a copy of my call event log. 1125_CallEvents.txt Share this post Link to post
SupportTeam Report post Posted 11/25/2018 08:26 PM Can you please make a WireShark capture of the SIP packets exchanged during the call attempt. We can then see what messaging is exchanged between VoiceGuide and your SIP provider. WireShark can be downloaded from: www.wireshark.org To isolate SIP traffic the following should be specified in WireShark's Filter text box: sip Then to save the captured SIP packets go to WireShark's File->Export Specified Packets menu and save the displayed packets as .pcapng format. Please post that .pcapng file, and also .ZIP up and post VoiceGuide's vgEngine and ktTel trace files that were created while those calls were made If running the unregistered evaluation version of VoiceGuide please make sure to make the calls within one hour of last VoiceGuide service restart. Share this post Link to post
Guest AaronMHopkins Report post Posted 11/25/2018 10:27 PM Attached find the log files created during the test calls. VoiceGuideSupport.zip Share this post Link to post
SupportTeam Report post Posted 11/25/2018 10:58 PM Can you please try specifying your full username/account name as the CallerID when making the outgoing call, including the SIP providers domain name. Like this: 17778691320@callcentric.com so the entry specified ion the Call Options field would be: <CallerID>17778691320@callcentric.com</CallerID> More information on setting the CallerID/username/account on the outgoing SIP calls can be found here: https://www.voiceguide.com/vghelp/source/html/dial_voip.htm 253 171526.400 7036 fn VoIPProvider_Register(protocol=SIP, reg_server=callcentric.com, reg_client=17778691320@callcentric.com, local_alias=17778691320@192.168.0.32, sH323SupportedPrefixes=) Share this post Link to post
Guest AaronMHopkins Report post Posted 11/25/2018 11:50 PM Thanks for your help adding the CallID solved the issue. I also seemed to have an error in my vg.ini file. I corrected the entry DialedNumberSuffix=@callcentric.com . Orginally I had DialedNumberSuffix=@sip.callcentric.com which was incorrect. Share this post Link to post
SupportTeam Report post Posted 11/26/2018 12:07 AM OK, thanks for letting us know the issue is now resolved Share this post Link to post