Jump to content


< Back to Forum


 

Service Stop After 1 Hour Run


  • Please log in to reply

#1 allenlee 02 January 2018 - 10:34 PM

hi, 

i've purchase and activated the pro version 4 lines, 

-i've activated and it shows in line status correctly at first, 

-however the service is not running well after 1 hour, in the line status it is still shows waiting for call, ( i've check my pbx and it shows client disconnected.)

-after the manual stop and start service, it works as normal again

-sometime the line status shows my license as evaluation copy randomly when the service stop and restart manually. 

attached wireshark captured for the 1 hour. 

 

please help 



#2 SupportTeam 02 January 2018 - 10:55 PM

Attached WireShark trace does not capture any startup REGISTER messages, and does not capture any calls. It just captures a series of OPTIONS/OK messages.

 

Please start the WireShark capture before starting the VoiceGuide service. This way any REGISTER messages that are sent out by VoiceGuide to register itself with the PBX will be captured. And please make a call into the system as well.

 

We can then see how the communications between the PBX and VoiceGuide is working.

 

No need to do capture for an hour, ending capture 5 minutes after end of the call into system is sufficient.

 

After finishing the trace please post the VoiceGuide ktTel trace as well (.ZIP up first also). We can then see both the SIP comms and VoiceGuide trace together,

 

Most likely the Registration between the VoiceGuide and this Yeastar S100 PBX is not fully set up. Traces will let us confirm and advise.

  • ws1.png


#3 allenlee 03 January 2018 - 01:30 AM

hi, 

attached file as suggested. 

thank you 

  • Attached File  log.zip   426.22KB   4 downloads


#4 SupportTeam 03 January 2018 - 08:06 AM

Could you please .ZIP up and post all the files in this directory:

 

C:\Program Files (x86)\Dialogic\HMP\log



#5 SupportTeam 03 January 2018 - 08:59 AM

In VoiceGuide's Config.xml, in section <VoIP-Registration> please set the <LocalAlias> field to:

 

1004@192.168.111.235

 

the LocalAlias should be the local address, not a remote address.

 

The reason why the SIP Register did not work as far as HMP was concerned was because of the Contact: field mismatch between the Register request and response.

SIP Registrars usually just use the Contact: setting provided in the original Register request, but the Yeastar PBX decided to use a different setting for Contact: in its reply.

In situations where the SIP Registrar changes the Contact:  details we must change the LocalAlias to match.

 

(the actual Contact: field returned by the Yeastar PBX is 1004@192.168.111.235:5060 but just using 1004@192.168.111.235 should be enough)

 

 

Also please add this entry to the <VoIP-Registration> section:

 

<Expires>60</Expires>

 

This will allow to quickly see if the REGISTER requests are being resent, without waiting for an hour.

 

After changing the Config.xml please stop both the VoiceGuide service and the Dialogic HMP service, and after the Dialogic HMP service has fully stopped the please start the Dialogic service and then start the VoiceGuide service.

 

Starting WireShark before starting the VoiceGuide service will let you monitor the REGISTER messages and confirm if they are being regularly sent to keep VoiceGuide registered.

 

 

Another option is to set up a direct IP trunk in the PBX. With direct IP trunk there is no need to do any registration.

PBX will just send calls direct to VoiceGuide IP address and VoiceGuide will answer all calls arriving at its IP address.

 

 

.

177 232531.237  7876     fn    VoIPProvider_Register(protocol=SIP, reg_server=192.168.111.4, reg_client=1004@192.168.111.4, local_alias=1004@192.168.111.4:5060, sH323SupportedPrefixes=)210 232531.299  2912     ev    GCEV_SERVICERESP (board device)

211 232531.303  2912           GCEV_SERVICERESP ResultInfo: gcValue=1285(0x505|GCRV_INTERNAL|event caused internal failure) gcMsg=[Event caused internal failure] ccLibId=8 ccLibName=[GC_H3R_LIB] ccValue=[0x93||] ccMsg=[IPEC_REG_FAIL_serverResponseDataMismatch] additionalinfo=[]
  • ws2.png


#6 allenlee 03 January 2018 - 02:33 PM

hi, 

i've follow the step and change the following, now the service not working after 1 minute, should i remove the "60" instead? 

 

 

1-

In VoiceGuide's Config.xml, in section <VoIP-Registration> please set the <LocalAlias> field to: 1004@192.168.111.235

 

2-

Also please add this entry to the <VoIP-Registration> section:

<Expires>60</Expires>



#7 SupportTeam 03 January 2018 - 03:01 PM

Please post the WireShark traces and the ktTel traces, as before. Then we can see what is happening on this system and comment.



#8 allenlee 03 January 2018 - 03:13 PM

hi, 

attached wireshark and kttel



#9 SupportTeam 03 January 2018 - 03:31 PM

ktTel trace shows that there is still a "serverResponseDataMismatch" error ( IPEC_REG_FAIL_serverResponseDataMismatch ) during the SIP Registration :

210 130954.703  4716           GCEV_SERVICERESP ResultInfo: gcValue=1285(0x505|GCRV_INTERNAL|event caused internal failure) gcMsg=[Event caused internal failure] ccLibId=8 ccLibName=[GC_H3R_LIB] ccValue=[0x93||] ccMsg=[IPEC_REG_FAIL_serverResponseDataMismatch] additionalinfo=[]

WireShark shows the sent out Contact header was:

 

<sip:1004@192.168.111.235>

 

and the Yeastar responded with this Contact header in the response message:

 

<sip:1004@192.168.111.235:5060>;expires=59

 

 

please set the <LocalAlias> field in VoiceGuide's Config.xml to:

 

1004@192.168.111.235:5060

 

and then stop both VoiceGuide and Dialogic HMP and then start Dialogic HMP and then start VoiceGuide.

 

 

Please start WireShark before starting the VoiceGuide service, to capture the Registration messages, and post both ktTel and WireShark traces if still encountering issues.



#10 allenlee 04 January 2018 - 03:56 AM

hi, 

i think the issue resolved after the suggestion. 

thank you