How could I make "Dial and Conference" work

[Harry C]

I was trying to transfer call to other system and before handover call to the other system, I need to run another script to hand over caller information by using 4 digits DTMF.

Could you please let me how could I using Transfer Call module to make it happen??

[SupportTeam]

You can use the "Dial and Conference - Monitored" transfer type.

On that transfer module's Properties pages in the Script Designer go to the "Announce Message" tab and set the "Sound file to play to recipient" to be the DTMF string to play. If the "Sound file to play.." is a series of digits instead of a filename then the DTMF tones will be played. This is how it works in every place a sound file can be  played.

You can use a Result Variable to hold the value of that 4 digit DTMF string, and just specify that Result Variable as the "Sound file to play to recipient".

More information here:

https://www.voiceguide.com/vghelp/source/html/modxfer.htm

https://www.voiceguide.com/vghelp/source/html/resultvariables.htm

[Harry C]

I got disconnect as soon as call went into Transfer Call module with Dial and Conference - Monitored selected.

which log file I need to provide?

[SupportTeam]

Please .ZIP up the latest 'vgEngine' and 'ktTel' traces which are in VoiceGuide's log subdirectory.

Please .ZIP up and post entire files, not just an excerpt.

[Harry C]

0620_ktTel.zip

[SupportTeam]

The outgoing leg of the call got immediately disconnected.

Are you able to make outgoing calls from this system? Have you tried just loading an outgoing call using the Dialer to confirm that outgoing calls work on this system?

WireShark trace might show more information here.

Please try placing an outgoing call using the Dialer and do a WireShark capture of that outgoing call attempt, and post the .pcapng save file from WireShark here.

421 100404.201 14208   3   1 fn    LineMakeCall(iLineId=3, iCallRequestId=0 (ignored), strNumberToCall=[913019626359@10.92.39.22], callprog=CONNECT_IMMEDIATELY<rtp-audio><rtp-audio-1>G711U</rtp-audio-1><rtp-audio-2>G711A</rtp-audio-2><rtp-audio-3>G729</rtp-audio-3></rtp-audio>, timeout=60, params:0,8,cidtosend=[12409973549@10.92.39.22],opt=[<calltype>DialAndConf</calltype><CallerId>12409973549@10.92.39.22</CallerId>])

...
445 100404.214  5112   3   1       gc_MakeCall [913019626359@10.92.39.22] call (HMP)
446 100404.214  5112   3   1       gc_MakeCall ok. crnx=8000001
447 100404.215  5112   3   1       TelDriver_LineMakeCall ret=0 crnx=8000001
448 100404.215  5112   3   1 r     generic ktTel_Completion|10000  Completion_MakeCall|0  134217729 (134217729|0|0|913019626359@10.92.39.22|12409973549@10.92.39.22|<result>ok</result><crn>134217729</crn><crnx>8000001</crnx>) this=075CFFCC pTelProxy_Global=0782ABC8
449 100404.216  5112   3   1 ev    GCEV_DIALING crn=8000001 crn_lastMakeCall=8000001
450 100404.216  5112   3   1 r     CallState(3, 8000001, 0, GCEV_DIALING, 16, 0, 16, , , )
451 100404.216 16152               extension - idx=23
452 100404.218  5112   3   1 ev    GCEV_DISCONNECTED crn=8000001 q: 2/3
453 100404.218  5112   3   1 r     CallState(3, 8000001, 0, GCEV_DISCONNECTED, 16384, 1931495192, 64, �Íh䈧    <, , ) 

[Harry C]

Yes, I have no issue for outgoing call.

I could use PBX Hookflash Transfer --Blind to the same outgoing number without any issue. It should be in the log too.

[SupportTeam]

Can you please make an outgoing call from this system. After the outgoing call is made please .ZIP up the latest 'vgEngine' and 'ktTel' traces which are in VoiceGuide's log subdirectory and post them here.

Please .ZIP up and post entire 'vgEngine' and 'ktTel' trace files, not just an excerpt.

Also:

Please .ZIP up Dialogic RTF logs in Dialogic's \log\ subdirectory - usually "C:\Program Files (x86)\Dialogic\HMP\log" and post the .ZIP file here.

[SupportTeam]

The outgoing call should be made using the Dialer. A 'Hookflash Transfer' (which on SIP systems results in a "REFER" transfer) does not result in an outgoing call being placed.

[Harry C]

rtflog-LOCAL-20230616-21h55m02.140s.zip

[SupportTeam]

Attached traces do not show an outgoing call attempt using the Dialer.

The outgoing call should be made using the Dialer.

A 'Hookflash Transfer' (which on SIP systems results in a "REFER" transfer) does not result in an outgoing call being placed.

 

[Harry C]

I don't know which module that I should in script as Dialer?

[SupportTeam]

You can use the Dialer app to load an outgoing call.

Please see:

https://www.voiceguide.com/ivr-software/outbound-ivr-dialer.htm

also:

https://www.voiceguide.com/vghelp/source/html/outbound-ivr-dialer-introduction.htm

and as this is a VoIP/SIP system:

https://www.voiceguide.com/vghelp/source/html/dial_voip.htm

[Harry C]

Do I need to change config file for Dialer?

I did Active  the call list and could find loaded number in report, but no dialing happen yet.

[SupportTeam]

You just need to specify the number to call, and the sound file to play for 'Live Answer". Nothing else needs to be set.

The number to call can be specified like this:

Then press the "Load Phone Numbers" button.

You should see the call attempt in the Line Status Monitor, and in the VoiceGuide log files.

[Harry C]

New folder (2).zip

[SupportTeam]

Trace files shows that the attempted outgoing call request was sent by VoiceGuide to Dialogic HMP, and Dialogic HMP accepted the call request and advised that it was making the outgoing call, and then a few milliseconds later HMP advised that the call has been Disconnected.

The RTF log does not show any errors.

WireShark trace might show more information about the outgoing call, and whether the HMP did issue the SIP INVITE message to 10.92.39.22

Please start a WireShark capture and then try placing an outgoing call using the Dialer and see if you can capture any IP messages of that outgoing call attempt. Then post the .pcapng save file from WireShark here.

 

980 205924.810 17448   3   1       gc_MakeCall [913019626359@10.92.39.22] call (HMP)
981 205924.811 17448   3   1       gc_MakeCall ok. crnx=8000001
...
984 205924.812 17448   3   1 ev    GCEV_LISTEN
985 205924.813 17448   3   1 ev    GCEV_DIALING crn=8000001 crn_lastMakeCall=8000001
...
988 205924.819 17448   3   1 ev    GCEV_DISCONNECTED crn=8000001 q: 2/52

 

[Harry C]

DialerTest.pcapng

[SupportTeam]

WireShark trace shows that the outgoing call fails as the device at 10.92.39.22 responds with a FORBIDDEN to VoiceGuide's/HMP's INVITE.

You should speak with administrator of whatever that device at 10.92.39.22 is.

Previous traces showed that this 10.92.39.22 device is already sending calls to VoiceGuide that VoiceGuide answers and can REFER transfer, so you now need to have that 10.92.39.22 device configured to accept calls from VoiceGuide/HMP as well.

Edited 06/23/2023 06:14 AM by SupportTeam
added the screenshot for the INVITE packet

[Harry C]

10.92.39.22 is NEC 9500 PBX.

I could use the same number 26259 in 3CX softphone to dial out OK. It means PBX setup should be OK.

What line configuration need to be setup in PBX side? My NEC engineer always use 3CX to verify line configuration.

Does "Dailout and Conference" and dialer are using the same command to dial out?

so fare only "PBX Hookflash Transfer - Blind" is working. I tried other option in Transfer Call Module and all of them got disconnected when script hit Transfer Call Module. 

 

[SupportTeam]

If you can do a WireShark capture the SIP messages of the outgoing call from the 3CX softphone then we can compare the two traces and see what he differences are.

Ultimately it's the PBX that is explicitly rejecting the call so the PBX administrator should see what is the cause of the PBX doing what it's doing.

Same formatted INVITE is sent by "Dial and Conference" as by the Dialer. "Dial and Conference" uses the Dialer module to make the outgoing call.

[SupportTeam]

Perhaps that 3CX softphone is  registering itself with the PBX as one the PBXs extensions, and that's why the PBX is then allowing that 3CX softphone to make outgoing calls through the PBX?

A good softphone to to use for testing is MicroSIP: https://www.microsip.org/

[Harry C]

3CX_DialLog.pcapng

[SupportTeam]

That softphone is on a different IP address.

Maybe the PBX allows some IP addresses but not others.

The PBX administrator can check the PBX logs and advise.

[Harry C]

The attached Wireshark file was captured by using MicroSIP to dial out.

MicroSIP_Dial_Log.pcapng

[SupportTeam]

Provided trace is from a softphone (MicroSIP) installed on a different machine with a different IP address.

Maybe the PBX allows some IP addresses but not others.

The PBX administrator can check the PBX logs and advise

[Harry C]

NEC NTAC supporting fund that 403 error was related to "User Agent Class is blank"

User Agent must be identified by the 3rd party vendor (minimum 3 characters).

[SupportTeam]

Please try loading an outgoing call using the VoiceGuide Dialer and specify this in the "Call Options" text box:

<sip-header>User-Agent: VoiceGuide</sip-header>

Like this:

 

This should add a 'User-Agent' header to the outgoing SIP INVITE.

Please do a WireShark Capture of the outgoing call as before, and post the .pcapng WireShark capture file here.

More information on specifying SIP headers on outgoing calls can be found here:

https://www.voiceguide.com/vghelp/source/html/dial_voip.htm

[Harry C]

I did use Dialer and add <sip-header>User-Agent</sip-Header> and I still got 403 error.

Could we add User-Agent during registration phase? It looks like MicroSIP or 3CX do provide User-Agent during line registration.

 

DialerUserAgent.pcapng

[SupportTeam]

Provided .pcapng trace shows that the SIP INVITE message now does contain the User-Agent header.

Looks like the header was specified to use "MSTIVR" instead of "VoiceGuide" as the User-Agent identifier, but either meets the "minimum 3 characters" advice that was provided.

You should ask the PBX administrator why was this call rejected by the PBX, even though it had the User-Agent header included in the INVITE as requested.

 

[Harry C]

PBX vendor is NEC North America point out that User-Agent should be provided during line registration.

MicroSIP does provide User-Agent information during registration phase.

[SupportTeam]

Please install MicroSIP on the same machine as VoiceGuide. Do not make any changes or set any Account or other settings on MicroSIP.

Then perform this test:

1. Stop VoiceGuide service and the Dialogic HMP service.

2. Start WireShark capture.

3. Without setting MicroSIP to Register with the PBX (ie. do not set any 'Account' settings) just place a place a call from MicroSIP to the PBX.

4. Configure MicroSIP to Register with the PBX (make sure no other softphone anywhere else is using this same registration/account details at the same time). Wait till you can see that the Registration is working in WireShark and again place a call from MicroSIP to the PBX.

5. Post the WireShark .pcapng capture file here.

[Harry C]

After I enable server audio services, I could use MicroSIP to dial out.

DialerMicroSIP.pcapng

[SupportTeam]

Do have the WireShark trace for the "Step 3" of the test:

Quote

3. Without setting MicroSIP to Register with the PBX (ie. do not set any 'Account' settings) just place a place a call from MicroSIP to the PBX.

 

Provided trace is only for the "Step 4" of the test.

We need to see what happens if MicroSIP does NOT register itself. Just sends call to 912409973549@10.92.39.22 without registration.

[Harry C]

DialerMicroSIP_NoReg.pcapng

[SupportTeam]

The next release of VoiceGuide (v7.4.4) now includes a fix that should resolve the "403 Forbidden" response issue from the NEC 9500 PBX that has been reported in this thread.

 

The fix involves ability for user to set the "User-Agent" header to any value when issuing a SIP REGISTER and SIP INVITE etc.

It looks like this PBX has been set to only accept SIP REGISTER and SIP INVITE with the "User-Agent" header set to a specific set of valued only.

v7.4.4 allows setting of "User-Agent" header value in VoiceGuide's VG.INI configuration file (for setting User-Agent during SIP REGISTER), and retains ability to set "User-Agent" on outgoing calls using by using the <sip-header> setting in the CallOptions field, like below:

<sip-header>User-Agent: MyUserAgentName</sip-header> 

 

VoiceGuide v7.4.4 will be available for general download from our Downloads page in a few days.

[Harry C]

We still got 403 after744 installed. I will contract NEC.

VG774.zip

[SupportTeam]

Please try removing the below Call Options entry from the Call Loader's Call Options text box:

<sip-header>User-Agent: MSTIVR</sip-header> 

using the above entry results in a different User-Agent header being sent with the outgoing call then what was used during SIP REGISTER.

In SIP REGISTER the User-Agent is:

User-Agent: VoiceGuide

And by using the above <sip-header> option, the User-Agent on outgoing call's SIP INVITE is:

User-Agent: VoiceGuide,MSTIVR

Removing the <sip-header> option will make the SIP INVITE's User-Agent header same as the SIP REGISTER's User-Agent header.

[SupportTeam]

Can see now in second call the User-Agent is just "VoiceGuide" and yet the PBX still responds with a 403.

Maybe the PBX needs to be configured to accept a specific User-Agent SIP Header?

The PBX administrator should advise why was this call "403 Forbidden" rejected by the PBX...

 

You should also try registering the SIP line/extension and placing an outgoing call with the User-Agent SIP header set to:

MicroSIP

or

MicroSIP/3.21.3

like in the working calls made using MicroSIP, and see if those calls work...

This way you would confirm, as we suspect, that this PBX does in fact only allows outgoing SIP INVITES that have "User-Agent" header set to some small set of specific values... and that the "User-Agent" header must be set to one of those values when doing the SIP REGISTER and the SIP INVITE on that line/extension afterwards...

Some PBXs have such restrictions in place, but setting the "User-Agent" header to one of their allowed values lets you work around such attempts of a vendor "walled garden" to limit 3rd party access.