DDI routing problems with VOIP On

Discussion in '3CX Phone System - General' started by neilevans, May 15, 2008.

Thread Status:
Not open for further replies.
  1. neilevans

    Joined:
    May 15, 2008
    Messages:
    1
    Likes Received:
    0
    Hi

    Have successfully setup the latest version of 3CX with the softphone and VOIP On.

    Also registered several new 0871 DDI numbers under the same account

    At one point the DDI's were working correctly, now any of the DDI numbers simple go straight to the main hunt group.

    I've attached the logs,

    14:23:08.187 Call::Terminate [CM503008]: Call(1): Call is terminated
    14:23:08.171 LineCfg::getInboundTarget [CM503011]: Inbound office hours' rule for LN:10000 forwards to DN:800
    14:22:53.375 CallCtrl::eek:nSelectRouteReq [CM503004]: Call(1): Calling: HuntGrp:800@[Dev:sip:104@192.168.16.246:5070;rinstance=8a2b7f7c774b5127]
    14:22:53.375 CallCtrl::eek:nSelectRouteReq [CM503004]: Call(1): Calling: HuntGrp:800@[Dev:sip:103@192.168.16.240:5070;rinstance=0625e46c897f914e]
    14:22:53.375 CallCtrl::eek:nSelectRouteReq [CM503004]: Call(1): Calling: HuntGrp:800@[Dev:sip:102@192.168.16.46:5070;rinstance=9c740b45280cb807]
    14:22:53.375 CallCtrl::eek:nSelectRouteReq [CM503004]: Call(1): Calling: HuntGrp:800@[Dev:sip:101@192.168.16.228:5070;rinstance=6a698f489d43d366]
    14:22:53.375 CallCtrl::eek:nSelectRouteReq [CM503015]: Call(1): Target is not registered: HuntGrp800:Ext.100

    14:22:53.328 Line::printEndpointInfo [CM505003]: Provider:[VoipOn] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Telappliant VoIP Gateway] Transport: [sip:192.168.16.10:5060]

    14:22:53.328 LineCfg::getInboundTarget [CM503011]: Inbound office hours' rule for LN:10000 forwards to DN:800
    14:22:53.140 CallCtrl::eek:nIncomingCall [CM503001]: Call(1): Incoming call from 07XX9XX36X6@(Ln.10000@VoipOn) to [sip:800@2XX.XX5.XX3.137:5060]

    I just wanted to know is this is an issue I need to address with 3CX or VOIP On?

    What I seem to make of it is that VOIP On are not correctly sending the required DDI data so that 3CX can route it properly

    Any help would be appreciated.

    Thanks
     
Thread Status:
Not open for further replies.