Dismiss Notice
We would like to remind you that we’re updating our login process for all 3CX forums whereby you will be able to login with the same credentials you use for the Partner or Customer Portal. Click here to read more.

Call transfer

Discussion in '3CX Phone System - General' started by Alexord, Jul 4, 2008.

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

    Joined:
    May 28, 2008
    Messages:
    19
    Likes Received:
    0
    Hello all!

    I'm using MS exchange as auto-attendant, and I have problem with call transfer. It works only if I turn off "supports re-invite" provider capability, but this is no good way because of I have huge delay with this option turned off.
    If I turn on "re-invite" my phone ringing after transfer but call hangs up just after answering.

    Can anybody advice me something?
     
  2. Henk

    Henk Member

    Joined:
    Nov 13, 2007
    Messages:
    250
    Likes Received:
    0
    Can you provide some server logs? It might be register issue, but the logs might shed some light.

    H.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. Anonymous

    Anonymous Guest

    The technical support requesting here goes beyond that we can provide in the free peer-peer forums and would require finite trouble-shooting of your specific installation which we would normally do via our Support Portal at http://support.3cx.com .

    We suggest that for a little amount of money we could give you this full support or provide you with feasible alternative solutions.

    This can start from a Small Business Edition with 8 simultaneous calls and Support Contract going at Eur 375 + Eur 125 per year. We also recommend version upgrade insurance at Eur 99 per year. We can also propose larger licenses as you desire and you can eventually perform Edition Upgrades as your needs grow.

    If you have any further queries about this or how to proceed, please contact sales@3cx.com .

    Thanks,
     
  4. Alexord

    Joined:
    May 28, 2008
    Messages:
    19
    Likes Received:
    0
    I'm just trying to understand this is my fault or somewhat wrong with my provider, because it works with another SIP provider. May be I have nothing to do with this...

    Here is my logs that appeared after trying to connect:

    11:02:02.271 Call::Terminate [CM503008]: Call(225): Call is terminated
    11:02:02.224 Call::Terminate [CM503008]: Call(225): Call is terminated
    11:02:02.052 LineCfg::getInboundTarget [CM503012]: Inbound out-of-office hours' rule for LN:10002 forwards to DN:800
    11:02:01.865 CallCtrl::eek:nLegConnected [CM503007]: Call(225): Device joined: sip:208@192.168.0.86:5060
    11:02:01.849 Extension::printEndpointInfo [CM505001]: Ext.208: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Linksys/SPA922-5.1.15(a)] Transport: [sip:192.168.0.200:5060]
    11:02:01.849 CallCtrl::eek:nAnsweredCall [CM503002]: Call(225): Alerting sip:208@192.168.0.86:5060
    11:01:59.693 CallCtrl::eek:nSelectRouteReq [CM503004]: Call(225): Calling: Ext:Ext.208@[Dev:sip:208@192.168.0.86:5060]
    11:01:59.693 CallCtrl::eek:nSelectRouteReq [CM503010]: Making route(s) to [sip:208@192.168.0.200:5060;user=phone;transport=Tcp]
    11:01:38.662 MediaServerReporting::DTMFhandler [MS211000] C:225.1: 81.26.212.141:60232 is delivering DTMF using RTP payload (RFC2833). In-Band DTMF tone detection is disabled for this call segment.
    11:01:31.411 CallCtrl::eek:nLegConnected [CM503007]: Call(225): Device joined: sip:800@192.168.x.x:5060;transport=TCP
    11:01:31.411 LineCfg::getInboundTarget [CM503012]: Inbound out-of-office hours' rule for LN:10002 forwards to DN:800
    11:01:31.365 CallCtrl::eek:nLegConnected [CM503007]: Call(225): Device joined: sip:007xxxxxx030@81.26.212.141
    11:01:31.349 CallCtrl::eek:nAnsweredCall [CM503002]: Call(225): Alerting sip:MSExchange@192.168.x.x:5060;transport=TCP
    11:01:30.443 CallCtrl::eek:nSelectRouteReq [CM503004]: Call(225): Calling: @[Dev:sip:MSExchange@192.168.x.x:5060;transport=TCP]
    11:01:30.427 CallCtrl::eek:nSelectRouteReq [CM503010]: Making route(s) to [sip:800@3cx-pbx.xxxxxxxxx.net:5060]
    11:01:30.427 Line::printEndpointInfo [CM505003]: Provider:[XeloQ] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [GNC SS5 Proxy] Transport: [sip:192.168.0.200:5060]
    11:01:30.427 LineCfg::getInboundTarget [CM503012]: Inbound out-of-office hours' rule for LN:10002 forwards to DN:800
    11:01:30.349 CallCtrl::eek:nIncomingCall [CM503001]: Call(225): Incoming call from 00xxxxxx030@(Ln.10002@XeloQ) to [sip:800@3cx-pbx.xxxxxxxx.net:5060]
    11:01:30.208 LineCfg::getInboundTarget [CM503012]: Inbound out-of-office hours' rule for LN:10002 forwards to DN:800
    11:01:11.567 ClientRegs::eek:nSuccess [CM504004]: Registration succeeded for: 10002@XeloQ
    11:01:11.333 ClientRegs::Register [CM504003]: Sent registration request for 10002@XeloQ
     
Thread Status:
Not open for further replies.