Making Outbound Calls Over Voip

[zhang19min88]

I use voip to test send phone message,but it can not work too.

Maybe something I forget to do or set wrong. can you give me some advice .thank you!

voip send phone message.zip

[zhang19min88]

403 Forbidden.

detail see the attachment.thanks

new_catch.zip

[SupportTeam]

It looks like you have VoiceGuide registering itself with a 3CX PBX, and then trying to place a call to extension 222 on that PBX.

 

Does extension 222 exist on the system and was at the time registered with the 3CX PBX?

 

Does the 3CX use G.729 ?

 

The HMP evaluation license that you are using has G.729 licenses, so the outgoing call is made with G.729 specified as the codec to use.

 

Can you remove the evaluation license from HMP and have HMP use the basic 1 port license that it comes in, and try making the outgoing call then. The outgoing call will then use G.711 codec.

[zhang19min88]

"Does the 3CX use G.729 ?"

Sorry ,I don't konw about it.

 

I use the basic 1 port license,and try again ,but still not work.

 

new vg.zip

[SupportTeam]

Please change in Config.xml from this:

 

<VoIP_Registrations>

<VoIP_Registration>

<Protocol>SIP</Protocol>

<RegServer>192.168.1.125</RegServer>

<RegClient>666@192.168.1.125</RegClient>

<LocalAlias>sip:666@192.168.1.123:5060</LocalAlias>

<CallerID>666@192.168.1.125</CallerID>

</VoIP_Registration>

</VoIP_Registrations>

<VoIP_Authentications>

<VoIP_Authentication>

<Display></Display>

<Realm>3CXPhoneSystem</Realm>

<Identity>sip:666@192.168.1.125</Identity>

<AuthUsername>666</AuthUsername>

<AuthPassword>666</AuthPassword>

<CallerID>666@192.168.1.125</CallerID>

</VoIP_Authentication>

</VoIP_Authentications>

to this:

<VoIP_Registrations>

<VoIP_Registration>

<Protocol>SIP</Protocol>

<RegServer>192.168.1.125</RegServer>

<RegClient>666@192.168.1.125</RegClient>

<LocalAlias>sip:666@192.168.1.123:5060</LocalAlias>

</VoIP_Registration>

</VoIP_Registrations>

<VoIP_Authentications>

<VoIP_Authentication>

<Realm></Realm>

<Identity></Identity>

<AuthUsername>666</AuthUsername>

<AuthPassword>666</AuthPassword>

</VoIP_Authentication>

</VoIP_Authentications>

and restart the VoiceGuide service after making the change.

Please see notes regarding Realm and Identity fields here: http://www.voiceguide.com/vghelp/source/html/config_voip_register.htm

Then make a call to

 

555@192.168.1.125

 

instead of:

 

222@192.168.1.125

 

and post both the WireShark trace and the ktTel traces capturing system startup and calls made.

 

[zhang19min88]

I have followed you advice ,and try again.

please see the attachment.

tray_again.zip

[SupportTeam]

did you attempt a call to 555@192.168.1.125 from VoiceGuide?

 

WireShark trace does not show any call attempt.

 

Please post both the WireShark trace and the ktTel traces capturing system startup and calls made.

[zhang19min88]

please try this.thanks

vg555.zip

[SupportTeam]

In this case the SIP registration did not work

 

the previous SIP register at 12:24:36 was fine, but SIP register at 12:28:48 returned "403 - Forbidden" from the PBX :

100 122436.844  6856     fn    VoIPProvider_AuthenticationSet
101 122436.845  6856           TelDriver_VoIPProvider_AuthenticationSet start. adding 1 auth entries.
102 122436.845  6856           adding to auth parmblk:   666 ******

106 122436.846  6856     fn    VoIPProvider_Register(protocol=SIP, reg_server=192.168.1.125, reg_client=666@192.168.1.125, local_alias=sip:666@192.168.1.123:5060, sH323SupportedPrefixes=)

181 122437.002  7072     ev    GCEV_SERVICERESP (board device)
182 122437.010  7072           GCEV_SERVICERESP ResultInfo: gcValue=0(0x0|GC_SUCCESS|GC_SUCCESS) gcMsg=[Success] ccLibId=8 ccLibName=[GC_H3R_LIB] ccValue=[0x0||] ccMsg=[IPERR_OK] additionalinfo=[]
183 122437.010  7072           ccValue==IPERR_OK (gc_ReqService registered a VoIP account)


099 122848.106  2332     fn    VoIPProvider_AuthenticationSet
100 122848.107  2332           TelDriver_VoIPProvider_AuthenticationSet start. adding 1 auth entries.
101 122848.107  2332           adding to auth parmblk:   666 ******

105 122848.109  2332     fn    VoIPProvider_Register(protocol=SIP, reg_server=192.168.1.125, reg_client=666@192.168.1.125, local_alias=sip:666@192.168.1.123:5060, sH323SupportedPrefixes=)

147 122848.232  6584     ev    GCEV_SERVICERESP (board device)

150 122848.240  6584           GCEV_SERVICERESP ResultInfo: gcValue=1286(0x506|GCRV_CCLIBSPECIFIC|event caused by cclib specific failure) gcMsg=[Event caused by call control library specific failure] ccLibId=8 ccLibName=[GC_H3R_LIB] ccValue=[0x151b||] ccMsg=[IPEC_SIPReasonStatus403Forbidden] additionalinfo=[]
151 122848.240  6584           ccValue!=IPERR_OK (VoIPProvider_AuthenticationSet)

you can see that PBX returned 403 in the WireShark trace as well. See attached WireShark screenshot.

 

You would need to check 3CX logs to determine why 3CX decided to respond to a REGISTER request with 403.

 

Probably simplest to just restart the 3CX and restart Dialogic drivers and try the same test again.

 

Please watch WireShark to confirm SIP registration succeeded before proceeding with making outgoing calls.

 

Use sip in WireShark's Filter text box to have WireShark only show you the SIP packets.

[zhang19min88]

I restart 3CXPhone System , HMP and VoiceGuide .it still can not work .

can you give me some advie about how to deal with " SIP registration did not work"?

may I need to re install 3cxphone system? or do something else?

[SupportTeam]

First you need to get the SIP Registration working again.

 

WireShark shows that HMP/VoiceGuide is sending exactly the same REGISTER request to 3CX but in last trace 3CX replies with "403 - Forbidden", whereas before 3CX replied with 407 and then HMP resent the REGISTER with authentication included and that was accepted OK by 3CX.

 

Has anything changed on 3CX ?

Are you able to see from any 3CX logs as to why 3CX is replying with "403 - Forbidden" ?

Was anything else installed or enabled on the system at 192.168.1.125 ?

 

Once you have the SIP Registration working again then you can try outgoing calls again.