![]() ![]() |
#1
|
|||
|
|||
![]()
Hi,
I'm running out of ideas on what could be causing this issue. I have configured the SIP extension to 6499. The short code configured is 60XX;Dial Extn;6499|>>. The task flow has been activated. The SIP extension is registered and showing at System monitor. Is there still some settings that i have missed out? I've tried to follow the installation document but the number busy still persist. |
#2
|
|||
|
|||
![]()
version to IPOCC ?
|
#3
|
|||
|
|||
![]()
Try altering the Tasklfow to route directly to a music announcement, like wait.wav (since it is default on the system). I have had this happen to me in the past when the taskflow was picking up malformed logic which caused the call to act strange. If the test music plays, then step into the flow a block or 2 at a time until you find the offending step.
Also, check the Taskserver_IPO, VEA, or CHAP logs in TTRace for possible errors. |
#4
|
|||
|
|||
![]() |
#5
|
|||
|
|||
![]()
While reviewing the VEA logs, i came across this particular entry
G9503a 10:09:13.672 CHAP_SIP_Warning [0x00004390] ocSIPUAController::vSetInternalNpiTon(cont=1): invalid numbering plan '' found -> using ISDN/unknown. Could this be causing the number busy? |
#6
|
|||
|
|||
![]()
Hi All,
Issue resolved when i reinstalled IPOCC. |
#7
|
|||
|
|||
![]()
IPocc 9.1 same problem number busy when dial topic
|
![]() |
Thread Tools | Search this Thread |
Display Modes | |
|
|