|
|
|
|
Joined: Jul 2004
Posts: 291
Member
|
|
Member
Joined: Jul 2004
Posts: 291 |
Hey all. I installed a Zultys MX 250 and connected it via T1 to an old Executone IDS. I can call between the two system with no issue. The problem is when a call comes in on a PRI into the EXECUTONE and I transfer it to Zultys, Zultys drops the call. In SYSLOG it shows the call as failure "not found;calling party - ids_Tie;called party-; "
Where am i going wrong ?
|
|
|
Visit Atcom to get started with your new business VoIP phone system ASAP
Turn up is quick, painless, and can often be done same day.
Let us show you how to do VoIP right, resulting in crystal clear call quality and easy-to-use features that make everyone happy!
Proudly serving Canada from coast to coast.
|
|
|
|
Joined: Oct 2004
Posts: 1,492
Member
|
|
Member
Joined: Oct 2004
Posts: 1,492 |
never worked with Zultys but do you have a ringing destination for the T1 trunks on the Zultys? Sounds like it doesn't know where to ring
|
|
|
|
|
Joined: Jul 2004
Posts: 291
Member
|
|
Member
Joined: Jul 2004
Posts: 291 |
I do have a destination set. The same destination that answers when i call it directly. I only have this problem when transferring calls.
|
|
|
|
|
Joined: Jul 2004
Posts: 291
Member
|
|
Member
Joined: Jul 2004
Posts: 291 |
Below is a CAS log from my Zultys system. Zultys is telling me that when i transfer a call, the executone system is dropping the call after it sends the DTMF digits 2 0 1. I can see the digits starting on line 6. Does anyone know what the data on the following lines mean ?
Dec 11 10:58:42:683 - 2 - {0x20009} [147.464] [ptl_fsm] [CAS: 0/11] CAS_PTL_ST_IDLE -> CAS_PTL_ST_WINK_ON Rx 0xf
Dec 11 10:58:42:922 - 2 - {0x20009} [147.703] [ptl_fsm] [CAS: 0/11] CAS_PTL_ST_WINK_ON -> CAS_PTL_ST_WINK_OFF Rx 0xf
Dec 11 10:58:42:924 - 2 - {0x20009} [147.705] [ptl] [CAS: 0/11] Port 0 On(Ptl Notf Wink Off) state st_CC_IDLE
Dec 11 10:58:42:924 - 2 - {0x20009} [147.705] [ptl] [CAS: 0/11] Port 0 SetState: st_CC_IDLE(1) -> st_CC_WAIT_FOR_DTMF(26)
Dec 11 10:58:42:924 - 2 - {0x20009} [147.705] [cas_dsp] [CAS: 0/11] >> DSP_start_dtmf_collection
Dec 11 10:58:43:560 - 2 - {0x20009} [148.341] [cas_dsp] [CAS: 0/11] DSP:digit rx 0x32 2:
Dec 11 10:58:43:758 - 2 - {0x20009} [148.539] [cas_dsp] [CAS: 0/11] DSP:digit rx 0x30 0:
Dec 11 10:58:43:977 - 2 - {0x20009} [148.758] [cas_dsp] [CAS: 0/11] DSP:digit rx 0x31 1:
Dec 11 10:58:45:031 - 2 - {0x20009} [149.812] [ptl] [CAS: 0/11] End of Dialing
Dec 11 10:58:45:031 - 2 - {0x20009} [149.812] [ptl_fsm] [CAS: 0/11] CAS_PTL_ST_WINK_OFF -> CAS_PTL_ST_ANSWER Rx 0xf
Dec 11 10:58:45:031 - 2 - {0x20009} [149.812] [ptl] [CAS: 0/11] Port 0 On(Ptl Notf Answer) state st_CC_WAIT_FOR_DTMF
Dec 11 10:58:45:031 - 2 - {0x20009} [149.812] [ptl] [CAS: 0/11] Port 0 SetState: st_CC_WAIT_FOR_DTMF(26) -> st_CC_SETUP_AWAIT_MEDIA_TRM(6)
Dec 11 10:58:45:031 - 2 - {0x20009} [149.812] [ptl] [CAS: 0/11] media_request_frontend: port 0 ch 4107 media_status 0
Dec 11 10:58:45:040 - 2 - {0x20009} [149.821] [cas_dsp] [CAS: 0/11] DSP:media_info_rsp
Dec 11 10:58:45:040 - 2 - {0x20009} [149.821] [ptl] [CAS: 0/11] Port 0 SetState: st_CC_SETUP_AWAIT_MEDIA_TRM(6) -> st_CC_SETUP_SEND(7)
|
|
|
|
Forums84
Topics94,457
Posts639,629
Members49,824
| |
Most Online5,661
May 23rd, 2018
|
|
|
|
|
|
