CamriVox Flexor 151 ATA configuration

Discussion in '3CX Phone System - General' started by jonathanc, Oct 17, 2012.

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

    Joined:
    Sep 3, 2012
    Messages:
    64
    Likes Received:
    1
    I hope this is the right place for this post.

    I've just bought a Flexor 151 ATA for nineteen pounds on eBay - before realising that it was a discontinued product and that there was therefore no support available from the manufacturer (or the supplier).

    It works fine when configured to interact with my VoIP provider (DrayTEL) directly.

    It works fine on incoming calls when configured for 3CX Phone System. However, with 3CX I receive an outbound dial tone but cannot make outbound calls.

    I can make 3CXPhone on my PC work perfectly both ways, so I would guess my firewall settings are OK. However, the Flexor 151's diagnostic software reports 'Blocking Firewall' when I enter 216.93.246.16 as the STUN server, and 'DNS Problem' when I enter 'stun.3cx.com' as the STUN server. But disabling both the software firewall (BullGuard) and the router's SPI firewall doesn't solve anything.

    If I enter anything at all in the Flexor's 'SIP Outbound Proxy' box in its account settings, 3CX immediately unregisters it.

    Short of investing in an approved ATA (I need 7 of the things!) has anyone any ideas, please?

    Many thanks in hopeful advance.
     
  2. lneblett

    lneblett Well-Known Member

    Joined:
    Sep 7, 2010
    Messages:
    2,083
    Likes Received:
    61
    You did not mention which version and edition of 3CX your are running. Hopefully a V11 SP1 version and that you also ran the firewall checker and it passes.

    Are you using the device as an FXO gateway or as a FXS analog telephone adapter when connected to 3CX? I just want to be clear of its intended use.

    If you are running v11 Sp1 and you have a fixed public IP, the STUN is not needed. Is the device co-located with the 3CX system and on the same subnet?

    The manual I found on-line is not very detailed as it seems to be expecting you to use the device to connect an analog telphone set in the house to a pre-defined VoIP provider.
     
  3. jonathanc

    Joined:
    Sep 3, 2012
    Messages:
    64
    Likes Received:
    1
    Thank you, lneblett, for your swift response - and for looking up the manual online.

    I did download v11 but had to revert to v10 in order to test the Ring Groups facility before purchasing the product. We're not a big company - there's just the two of us - but we need to be able to get to the phone in several locations.

    I am using the Flexor as an FXS analog telephone adapter - at least, I think I am! An analog phone is plugged into it and the device itself is inserted between the PC and the router. The device co-located with the 3CX system and on the same subnet.

    Running Firewall Checker has revealed a couple of warnings which I'm not too sure how to clear. I've opened (forwarded service ports to internal ports) the following ports on my TP-Link WR841N router:

    53
    5060
    5065
    5070
    5090
    8000-8020
    9000-9049

    ...all as ALL protocols except 5070 which is UDP only.

    The Flexor did not come pre-programmed to a specific ITSP, so I programmed it as follows:

    Account Settings
    Service Provider: Manual: Thru PBX
    User Name: 101 [extension number in 3CX Phone System]
    Auth Name: 101 [extension number in 3CX Phone System]
    Password: [as given by 3CX]
    Confirm Password: [as given by 3CX]
    Your name: optional

    Please enter the following manual configuration settings:

    Name: Thru PBX
    SIP Registrar/Proxy: 192.168.1.3 [the bound IP address of the PC running 3CX Phone System]
    SIP Registrar/Proxy port: 5060
    SIP Outbound Proxy: [blank]
    SIP Outbound Proxy port: 0 (filled in automatically)
    STUN Server: [blank after your advice]
    STUN Server port: 0 (filled in automatically)
    Map SDP only: [checkbox NOT ticked]

    The Flexor's built-in diagnostic facility reports:

    Gathering diagnostics...complete.
    Internet Connectivity
    IP Address: 192.168.1.6
    Gateway: 192.168.1.1 Ping OK
    DNS: 192.168.1.1 Ping OK
    A network requiring log in via a web browser has been detected. We recommend you change the network settings to Emulate PC Settings. Click here to do so. [When I did, 3CX deregistered the device, so I reverted to the 'Automatic' setting.]
    Detailed Internet Information
    The WAN port is connected to the Internet.
    The LAN port is connected to the local network.
    Using DHCP to determine IP address.
    DHCP Server on port connected to the Internet.
    DHCP Server MAC: 90:f6:52:8a:fb:ac
    STUN Server: 216.93.246.14
    NAT Type: Cone NAT
    External Address: 5.61.196.247

    I do not have a static public IP address since changing to satellite broadband, but the allocated one seems pretty constant.

    As I say, incoming calls work perfectly, and outgoing calls when the Flexor is configured to interact directly with DrayTEL; but when you try to make an outgoing call through 3CX you get dial tone, DTMF sequence, then silence.

    Are the two WARNINGS given by Firewall Checker below to blame, do you think? And if so, how do I get rid of them?

    Many thanks for your help.

    ***Firewall Checker report***

    3CX Firewall Checker, v1.0. Copyright (C) 3CX Ltd. All rights reserved.

    <23:38:49>: Phase 1, checking servers connection, please wait...
    <23:38:49>: Stun Checker service is reachable. Phase 1 check passed.
    <23:38:49>: Phase 2a, Check Port Forwarding to UDP SIP port, please wait...
    <23:38:51>: UDP SIP Port is set to 5060. Response received WITH TRANSLATION 1026::5060. Phase 2a check passed with WARNINGS. Some functionality will be LIMITED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/

    <23:38:51>: Phase 2b. Check Port Forwarding to TCP SIP port, please wait...
    <23:38:52>: TCP SIP Port is set to 5060. Response received WITH TRANSLATION 1026::5060. Phase 2b check passed with WARNINGS. Some functionality will be LIMITED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/

    <23:38:52>: Phase 3. Check Port Forwarding to TCP Tunnel port, please wait...
    <23:38:53>: TCP TUNNEL Port is set to 5090. Response received correctly with no translation. Phase 3 check passed.

    <23:38:53>: Phase 4. Check Port Forwarding to RTP external port range, please wait...
    <23:39:38>: UDP RTP Port 9000. Response received correctly with no translation. Phase 4-01 check passed.
    <23:39:38>: UDP RTP Port 9001. Response received correctly with no translation. Phase 4-02 check passed.
    <23:39:38>: UDP RTP Port 9002. Response received correctly with no translation. Phase 4-03 check passed.
    <23:39:38>: UDP RTP Port 9003. Response received correctly with no translation. Phase 4-04 check passed.
    <23:39:38>: UDP RTP Port 9004. Response received correctly with no translation. Phase 4-05 check passed.
    <23:39:38>: UDP RTP Port 9005. Response received correctly with no translation. Phase 4-06 check passed.
    <23:39:38>: UDP RTP Port 9006. Response received correctly with no translation. Phase 4-07 check passed.
    <23:39:38>: UDP RTP Port 9007. Response received correctly with no translation. Phase 4-08 check passed.
    <23:39:38>: UDP RTP Port 9008. Response received correctly with no translation. Phase 4-09 check passed.
    <23:39:38>: UDP RTP Port 9009. Response received correctly with no translation. Phase 4-10 check passed.
    <23:39:38>: UDP RTP Port 9010. Response received correctly with no translation. Phase 4-11 check passed.
    <23:39:38>: UDP RTP Port 9011. Response received correctly with no translation. Phase 4-12 check passed.
    <23:39:38>: UDP RTP Port 9012. Response received correctly with no translation. Phase 4-13 check passed.
    <23:39:38>: UDP RTP Port 9013. Response received correctly with no translation. Phase 4-14 check passed.
    <23:39:38>: UDP RTP Port 9014. Response received correctly with no translation. Phase 4-15 check passed.
    <23:39:38>: UDP RTP Port 9015. Response received correctly with no translation. Phase 4-16 check passed.
    <23:39:38>: UDP RTP Port 9016. Response received correctly with no translation. Phase 4-17 check passed.
    <23:39:38>: UDP RTP Port 9017. Response received correctly with no translation. Phase 4-18 check passed.
    <23:39:38>: UDP RTP Port 9018. Response received correctly with no translation. Phase 4-19 check passed.
    <23:39:38>: UDP RTP Port 9019. Response received correctly with no translation. Phase 4-20 check passed.
    <23:39:38>: UDP RTP Port 9020. Response received correctly with no translation. Phase 4-21 check passed.
    <23:39:38>: UDP RTP Port 9021. Response received correctly with no translation. Phase 4-22 check passed.
    <23:39:38>: UDP RTP Port 9022. Response received correctly with no translation. Phase 4-23 check passed.
    <23:39:38>: UDP RTP Port 9023. Response received correctly with no translation. Phase 4-24 check passed.
    <23:39:38>: UDP RTP Port 9024. Response received correctly with no translation. Phase 4-25 check passed.
    <23:39:38>: UDP RTP Port 9025. Response received correctly with no translation. Phase 4-26 check passed.
    <23:39:38>: UDP RTP Port 9026. Response received correctly with no translation. Phase 4-27 check passed.
    <23:39:38>: UDP RTP Port 9027. Response received correctly with no translation. Phase 4-28 check passed.
    <23:39:38>: UDP RTP Port 9028. Response received correctly with no translation. Phase 4-29 check passed.
    <23:39:38>: UDP RTP Port 9029. Response received correctly with no translation. Phase 4-30 check passed.
    <23:39:38>: UDP RTP Port 9030. Response received correctly with no translation. Phase 4-31 check passed.
    <23:39:38>: UDP RTP Port 9031. Response received correctly with no translation. Phase 4-32 check passed.
    <23:39:38>: UDP RTP Port 9032. Response received correctly with no translation. Phase 4-33 check passed.
    <23:39:38>: UDP RTP Port 9033. Response received correctly with no translation. Phase 4-34 check passed.
    <23:39:38>: UDP RTP Port 9034. Response received correctly with no translation. Phase 4-35 check passed.
    <23:39:38>: UDP RTP Port 9035. Response received correctly with no translation. Phase 4-36 check passed.
     
  4. lneblett

    lneblett Well-Known Member

    Joined:
    Sep 7, 2010
    Messages:
    2,083
    Likes Received:
    61
    OK.

    You should not need STUN, so you can eliminate these entries. Your ATA and 3CX system are all behind the same firewall and connected to the same LAN and Subnet.

    The WAN port is where you should plug in your existing LAN> The LAN port is where you would plug in say a PC or other device that you want connected to your network. It may have bridge mode or router as settings. You will likely want bridge so that the other devive, if any, will pick up a DHCP address from your network and it will function with normal interaction with your network. It is simply a way of providing an outlet as a convenience.

    The firewall warnings are centric to the ability of the system to communicate to Dreytel and have nothing to do with the ATA. The ATA communicates directly with 3CX in this case and never traverses the firewall. It is 3CX having a difficulty, but that is another thread.

    Does the ATA support a send/dial key like "#"? Is there a timeout by which once reached, the ATA will dial? The dial tone is being provided by the ATA and not 3CX. Like a cell or mobile, there is generally a need to tell the device when all the digits are entered and this is usually done by waiting for the timeout to occur, or, for the less patient, by hitting the send/dial key. As a typical analog phone does not possess such a key the ATA should allow you to specify which key that will be and most use the "#" key.

    We want to make sure that the call is actually being sent out, so check the logs after trying to make a call. THere should be some log entries. You might also need to check your DTMF settings. 3CX is pretty flexible in this area so I do not think there will be an issue, but the manual I saw does not show most of the options that available for manual settings related to SIP and Voip. An inband or out of band setting will work. The specs do not show any of the RFCs so am uncertain in this area.

    Set the CODEC for g711a.

    Enable Vmail for the extension and dial the appropriate code for same. What happens? Do you get the prompts and does it repsond to your key inputs (DTMF)?

    Try dialing "*777". This is an echo test and if all is working, then you should be able to hear your own echo of whatever is spoken. If you hear the echo, then presumably you are OK. If not, then try setting PBX provides audio and supports re-invites to on in the extension settings within 3CX for that extension and try again.

    If this still fails then we will likley need screen shots of the ATA settings and also of the 3CX log recordings.
     
  5. jonathanc

    Joined:
    Sep 3, 2012
    Messages:
    64
    Likes Received:
    1
    Thank you for your further advice. I have checked all your kind suggestions in turn.

    I have eliminated all the STUN entries from the Flexor settings.

    The network is plugged into the Flexor's WAN port and the neighbouring PC into its LAN port.

    It has been allocated an IP address and can be contacted via a web browser from other PCs on
    the network. It can also receive calls when plugged independently into a vacant network
    socket. These both suggest that the problem is not with the network.

    I have tried using the "#" key as a "send" key to no avail. Also, when the ATA is configured
    for direct connection to DrayTEL it is not necessary to press any key after dialling the
    number.

    Checking the Server Activity log showed no entry after attempting an outbound call via the
    Flexor (and yes, I did remember to refresh!).

    However, looking further down the log I see an entry where the Flexor is mentioned:


    12:05:18.343 [CM505001]: Ext.101: Device info: Device Not Identified: User Agent not
    matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Camrivox
    Flexor 151 2.36] PBX contact: [sip:101@192.168.1.3:5060]


    It's the "recvonly" item which interests me: presumably it means that 3CX thinks that the
    device can only receive and not initiate calls. I'm not sure where it gets that impression
    from: it can only be from the Flexor settings, surely?

    Incidentally, I did set the Primary CODEC for G711a, but 3CX resets it to G711u. However,
    G711a appears as the secondary CODEC.

    I enabled voicemail and dialled the appropriate number: silence.

    I dialled "*777": again, silence.

    I tried <Recall> 777 and ;Recall> *777: silence.

    I tried all these both with and without "PBX provides audio" and "Supports re-invites".

    The only prompt I could get was by pressing "#", when an English voice said: "Please spell
    name to dial" - but since the 3CX prompts are set to the default US English this prompt
    presumably came from the Flexor itself.

    You kindly asked for screenshots and logs. The Server Activity log is as below.

    Screenshots of the Flexor settings are attached.

    Thank you again for your perseverance.

    ***3CX log***

    13:04:43.671 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to
    STUN server [ V4 199.192.206.228:3478 UDP target domain=unspecified mFlowKey=0 ] over
    Transport [ V4 192.168.1.3:5060 UDP target domain=unspecified mFlowKey=0 ]
    12:48:26.375 [CM504001]: Ext.101: new contact is registered. Contact(s):
    [sip:101@192.168.1.6:5060/101]
    12:48:18.984 [CM504002]: Ext.101: a contact is unregistered. Contact(s): []
    12:47:06.703 [CM504001]: Ext.101: new contact is registered. Contact(s):
    [sip:101@192.168.1.6:5060/101]
    12:46:44.093 [CM503008]: Call(6): Call is terminated
    12:46:38.453 [CM503007]: Call(6): Device joined:
    sip:666@127.0.0.1:40600;rinstance=51cfd76d8471360a
    12:46:38.437 [CM503007]: Call(6): Device joined: sip:8115773@draytel.org:5060
    12:46:38.406 [CM505001]: Ext.666: Device info: Device Identified: [Man: 3CX Ltd.;Mod: Voice


    Mail Menu;Rev: General] Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent:
    [3CX Voice Mail Menu] PBX contact: [sip:666@127.0.0.1:5060]
    12:46:38.390 [CM503002]: Call(6): Alerting
    sip:666@127.0.0.1:40600;rinstance=51cfd76d8471360a
    12:46:38.265 [CM503025]: Call(6): Calling
    Ext:Ext.666@[Dev:sip:666@127.0.0.1:40600;rinstance=51cfd76d8471360a]
    12:46:38.218 [CM503005]: Call(6): Forwarding:
    Ext:Ext.666@[Dev:sip:666@127.0.0.1:40600;rinstance=51cfd76d8471360a]
    12:46:38.218 [CM503016]: Call(6): Attempt to reach <sip:101@192.168.1.3:5060> failed.
    Reason: Not Registered
    12:46:38.218 [CM503017]: Call(6): Target is not registered: Ext.101
    12:46:38.203 [CM503010]: Making route(s) to <sip:101@192.168.1.3:5060>
    12:46:38.171 [CM505003]: Provider:[Draytel] Device info: Device Not Identified: User Agent
    not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [voip] PBX
    contact: [sip:8115773@5.61.196.247:5060]
    12:46:38.156 [CM503001]: Call(6): Incoming call from 01994419834@(Ln.10000@Draytel) to
    <sip:101@192.168.1.3:5060>
    12:46:37.328 [CM503012]: Inbound any hours rule (Personal) for 10000 forwards to DN:101
    12:46:18.781 [CM504002]: Ext.101: a contact is unregistered. Contact(s): []
    12:44:43.593 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to
    STUN server [ V4 199.192.206.228:3478 UDP target domain=unspecified mFlowKey=0 ] over
    Transport [ V4 192.168.1.3:5060 UDP target domain=unspecified mFlowKey=0 ]
    12:33:58.671 [CM504001]: Ext.666: new contact is registered. Contact(s):
    [sip:666@127.0.0.1:40600;rinstance=51cfd76d8471360a/666]
    12:24:43.531 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to
    STUN server [ V4 199.192.206.228:3478 UDP target domain=unspecified mFlowKey=0 ] over
    Transport [ V4 192.168.1.3:5060 UDP target domain=unspecified mFlowKey=0 ]
    12:20:56.453 [CM503003]: Call(5): Call to sip:101@192.168.1.3 has failed; Cause: 487
    Request Terminated; from IP:192.168.1.6:5060
    12:20:56.343 [CM503008]: Call(5): Call is terminated
    12:20:52.609 [CM505001]: Ext.101: Device info: Device Not Identified: User Agent not
    matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Camrivox
    Flexor 151 2.36] PBX contact: [sip:101@192.168.1.3:5060]
    12:20:52.578 [CM503002]: Call(5): Alerting sip:101@192.168.1.6:5060
    12:20:52.437 [CM503025]: Call(5): Calling Ext:Ext.101@[Dev:sip:101@192.168.1.6:5060]
    12:20:52.390 [CM503004]: Call(5): Route 1: Ext:Ext.101@[Dev:sip:101@192.168.1.6:5060]
    12:20:52.375 [CM503010]: Making route(s) to <sip:101@192.168.1.3:5060>
    12:20:52.359 [CM505003]: Provider:[Draytel] Device info: Device Not Identified: User Agent
    not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [voip] PBX
    contact: [sip:8115773@5.61.196.247:5060]
    12:20:52.312 [CM503001]: Call(5): Incoming call from 01994419834@(Ln.10000@Draytel) to
    <sip:101@192.168.1.3:5060>
    12:20:51.375 [CM503012]: Inbound any hours rule (Personal) for 10000 forwards to DN:101
    12:05:29.937 [CM503008]: Call(4): Call is terminated
    12:05:23.937 [CM503007]: Call(4): Device joined: sip:101@192.168.1.6:5060
    12:05:23.921 [CM503007]: Call(4): Device joined: sip:8115773@draytel.org:5060
    12:05:18.343 [CM505001]: Ext.101: Device info: Device Not Identified: User Agent not
    matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Camrivox
    Flexor 151 2.36] PBX contact: [sip:101@192.168.1.3:5060]
    12:05:18.343 [CM503002]: Call(4): Alerting sip:101@192.168.1.6:5060
    12:05:18.296 [CM503025]: Call(4): Calling Ext:Ext.101@[Dev:sip:101@192.168.1.6:5060]
    12:05:18.250 [CM503004]: Call(4): Route 1: Ext:Ext.101@[Dev:sip:101@192.168.1.6:5060]
    12:05:18.218 [CM503010]: Making route(s) to <sip:101@192.168.1.3:5060>
    12:05:18.218 [CM505003]: Provider:[Draytel] Device info: Device Not Identified: User Agent
    not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [voip] PBX
    contact: [sip:8115773@5.61.196.247:5060]
    12:05:18.187 [CM503001]: Call(4): Incoming call from 01994419834@(Ln.10000@Draytel) to
    <sip:101@192.168.1.3:5060>
    12:05:17.015 [CM503012]: Inbound any hours rule (Personal) for 10000 forwards to DN:101
    12:04:43.515 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to
    STUN server [ V4 199.192.206.228:3478 UDP target domain=unspecified mFlowKey=0 ] over
    Transport [ V4 192.168.1.3:5060 UDP target domain=unspecified mFlowKey=0 ]
    12:01:09.109 [CM504001]: Ext.101: new contact is registered. Contact(s):
    [sip:101@192.168.1.6:5060/101]
    11:59:36.625 [CM503008]: Call(3): Call is terminated
    11:59:29.171 [CM503007]: Call(3): Device joined:
    sip:999@127.0.0.1:40600;rinstance=258367ebdec0ec1e
    11:59:29.109 [CM503007]: Call(3): Device joined: sip:8115773@draytel.org:5060
    11:59:28.796 [CM505001]: Ext.999: Device info: Device Identified: [Man: 3CX Ltd.;Mod: Voice


    Mail Menu;Rev: General] Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent:
    [3CX Voice Mail Menu] PBX contact: [sip:999@127.0.0.1:5060]
    11:59:28.796 [CM503002]: Call(3): Alerting
    sip:999@127.0.0.1:40600;rinstance=258367ebdec0ec1e
    11:59:28.578 [CM503025]: Call(3): Calling
    Ext:Ext.999@[Dev:sip:999@127.0.0.1:40600;rinstance=258367ebdec0ec1e]
    11:59:28.468 [CM503005]: Call(3): Forwarding:
    Ext:Ext.999@[Dev:sip:999@127.0.0.1:40600;rinstance=258367ebdec0ec1e]
    11:59:28.453 [CM503016]: Call(3): Attempt to reach <sip:101@192.168.1.3:5060> failed.
    Reason: Not Registered
    11:59:28.453 [CM503017]: Call(3): Target is not registered: Ext.101
    11:59:28.453 [CM503010]: Making route(s) to <sip:101@192.168.1.3:5060>
    11:59:28.437 [CM505003]: Provider:[Draytel] Device info: Device Not Identified: User Agent
    not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [voip] PBX
    contact: [sip:8115773@5.61.196.247:5060]
    11:59:28.421 [CM503001]: Call(3): Incoming call from 01994419834@(Ln.10000@Draytel) to
    <sip:101@192.168.1.3:5060>
    11:59:27.281 [CM503012]: Inbound any hours rule (Personal) for 10000 forwards to DN:101
    11:56:58.531 [MS105000] C:2.1: No RTP packets were
    received:remoteAddr=127.0.0.1:40012,extAddr=0.0.0.0:0,localAddr=127.0.0.1:7002
    11:56:57.875 [CM503008]: Call(2): Call is terminated
    11:56:54.734 [CM505003]: Provider:[Draytel] Device info: Device Not Identified: User Agent
    not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [voip] PBX
    contact: [sip:8115773@5.61.196.247:5060]
    11:56:54.734 [CM503002]: Call(2): Alerting sip:8115773@draytel.org:5060
    11:56:52.578 [CM503025]: Call(2): Calling
    VoIPline:01994419834@(Ln.10000@Draytel)@[Dev:sip:8115773@draytel.org:5060]
    11:56:51.640 [CM503004]: Call(2): Route 1:
    VoIPline:01994419834@(Ln.10000@Draytel)@[Dev:sip:8115773@draytel.org:5060]
    11:56:51.593 [CM503010]: Making route(s) to <sip:01994419834@192.168.1.3:5060>
    11:56:51.578 [CM505001]: Ext.103: Device info: Device Not Identified: User Agent not
    matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CXPhone
    6.0.26523.0] PBX contact: [sip:103@127.0.0.1:5060]
    11:56:51.562 [CM503001]: Call(2): Incoming call from Ext.103 to
    <sip:01994419834@192.168.1.3:5060>
    11:56:02.843 [CM503008]: Call(1): Call is terminated
    11:55:51.375 [CM503007]: Call(1): Device joined:
    sip:999@127.0.0.1:40600;rinstance=258367ebdec0ec1e
    11:55:51.359 [CM503007]: Call(1): Device joined: sip:8115773@draytel.org:5060
    11:55:51.187 [CM505001]: Ext.999: Device info: Device Identified: [Man: 3CX Ltd.;Mod: Voice


    Mail Menu;Rev: General] Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent:
    [3CX Voice Mail Menu] PBX contact: [sip:999@127.0.0.1:5060]
    11:55:51.171 [CM503002]: Call(1): Alerting
    sip:999@127.0.0.1:40600;rinstance=258367ebdec0ec1e
    11:55:51.000 Currently active calls - 1: [1]
    11:55:49.609 [CM503025]: Call(1): Calling
    Ext:Ext.999@[Dev:sip:999@127.0.0.1:40600;rinstance=258367ebdec0ec1e]
    11:55:49.515 [CM503005]: Call(1): Forwarding:
    Ext:Ext.999@[Dev:sip:999@127.0.0.1:40600;rinstance=258367ebdec0ec1e]
    11:55:49.359 [CM503016]: Call(1): Attempt to reach <sip:101@192.168.1.3:5060> failed.
    Reason: Not Registered
    11:55:49.359 [CM503017]: Call(1): Target is not registered: Ext.101
    11:55:49.203 [CM503010]: Making route(s) to <sip:101@192.168.1.3:5060>
    11:55:49.093 [CM505003]: Provider:[Draytel] Device info: Device Not Identified: User Agent
    not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [voip] PBX
    contact: [sip:8115773@5.61.196.247:5060]
    11:55:48.937 [CM503001]: Call(1): Incoming call from 01994419834@(Ln.10000@Draytel) to
    <sip:101@192.168.1.3:5060>
    11:55:43.953 [CM503012]: Inbound any hours rule (Personal) for 10000 forwards to DN:101
    11:55:14.500 [CM504002]: Ext.101: a contact is unregistered. Contact(s): []
    11:51:23.875 [CM504001]: Ext.100: new contact is registered. Contact(s):
    [sip:100@192.168.1.5:5065;ob/100]
    11:46:16.812 [CM504001]: Ext.EndCall: new contact is registered. Contact(s):
    [sip:EndCall@127.0.0.1:40600;rinstance=51a4da567ae421b4/EndCall]
    11:46:16.812 [CM504001]: Ext.999: new contact is registered. Contact(s):
    [sip:999@127.0.0.1:40600;rinstance=258367ebdec0ec1e/999]
    11:45:33.328 [CM504001]: Ext.*1: new contact is registered. Contact(s):
    [sip:*1@127.0.0.1:40000;rinstance=79cf07a168134cdb/*1]
    11:45:33.328 [CM504001]: Ext.*0: new contact is registered. Contact(s):
    [sip:*0@127.0.0.1:40000;rinstance=278e0ee51ae713d5/*0]
    11:45:33.281 [CM504001]: Ext.*777: new contact is registered. Contact(s):
    [sip:*777@127.0.0.1:40000;rinstance=20f348082607edcb/*777]
    11:45:32.218 [CM504001]: Ext.101: new contact is registered. Contact(s):
    [sip:101@192.168.1.6:5060/101]
    11:45:16.437 [CM102001]: Authentication failed for SipReq: REGISTER 192.168.1.9
    tid=971d576dfe35cc72 cseq=REGISTER contact=DialCode@127.0.0.1:5488 / 2 from(wire); Reason:
    Credentials don't match, check that authorization-ID and password match the ones in
    extension settings
    11:45:14.109 [EC100007]: External application is connected:
    application:study:0/QueueManager local:127.0.0.1:5482 remote:127.0.0.1:1126
    11:45:04.078 [EC200005]: Parking Orbit server is connected:
    application:study:0/3CXParkOrbit local:127.0.0.1:5482 remote:127.0.0.1:1118
    11:45:02.843 [EC200002]: Media server is connected: application:study:0/MediaServer
    local:127.0.0.1:5482 remote:127.0.0.1:1116
    11:45:00.781 [EC200004]: IVR server is connected: application:study:0/IVRServer
    local:127.0.0.1:5482 remote:127.0.0.1:1113
    11:44:59.265 [CM504001]: Ext.103: new contact is registered. Contact(s):
    [sip:103@127.0.0.1:1089;rinstance=82ffca1b77790507/103]
    11:44:58.687 [CM504008]: Fax Service: registered as sip:888@192.168.1.3:5060 with contact
    sip:888@192.168.1.3:5100;user=phone
    11:44:53.906 [CM504004]: Registration succeeded for: 10000@Draytel
    11:44:51.921 [CM504003]: Sent registration request for 10000@Draytel
    11:44:51.843 IP(s) added:[192.168.1.3]
    11:44:51.625 [EC200006]: Conference server is connected:
    application:study:0/3CXConferenceRoom local:127.0.0.1:5482 remote:127.0.0.1:1101
    11:44:46.375 [CM504004]: Registration succeeded for: 10000@Draytel
    11:44:44.437 [CM504003]: Sent registration request for 10000@Draytel
    11:44:44.375 [CM506002]: Resolved SIP external IP:port ([ V4 5.61.196.247:5060 UDP target
    domain=unspecified mFlowKey=0 ]) on Transport [ V4 192.168.1.3:5060 UDP target
    domain=unspecified mFlowKey=0 ]
    11:44:43.484 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to
    STUN server [ V4 199.192.206.228:3478 UDP target domain=unspecified mFlowKey=0 ] over
    Transport [ V4 192.168.1.3:5060 UDP target domain=unspecified mFlowKey=0 ]
    11:44:42.125 Failed to obtain short path name for [C:\Documents and Settings\All
    Users\Application Data\3CX\Bin\Cert]
    11:44:42.125 [CM501006]: Default Local IP address: [192.168.1.3]
    11:44:42.109 [CM501002]: Version: 10.0.23053.0
    11:44:42.109 [CM501001]: Start 3CX PhoneSystem Call Manager
    11:44:42.109 [CM501010]: License Info: Load Failed - Error licence Licence: 27 System: 2
    11:44:41.796 [EC200001]: Configuration server is connected:
    application:study:5485/DBProvider local:127.0.0.1:1083 remote:127.0.0.1:5485
    11:44:41.765 [CM501007]: *** Started Calls Controller thread ***
     

    Attached Files:

  6. lneblett

    lneblett Well-Known Member

    Joined:
    Sep 7, 2010
    Messages:
    2,083
    Likes Received:
    61
    In looking at the logs, I see a number of:
    Reason: Not Registered
    11:55:49.359 [CM503017]: Call(1): Target is not registered: Ext.101.

    Can you see if extension 101 in the 3CX Extension Status page shows "green". If not then we will not be able to make calls until it is green = registered. Do not worry about the recvonly statement. Not an issue. As far as CODECs go, it may be getting set by 3CX. You can go to the extension tab and then the provisioning page and change the order of the preferred codec accordingly. WHile there, then go to the Other page and ensure that the Disable outbound calls is not checked. The G711u (PCMU) is more common in the States whereas the G711a (PCMA) is more so in the EU/UK. They devices negotiate to find a compatible CODEC to use so likely either is fine. I was just not sure what the ATA could support.

    I also saw where a call in and was routed to 101, whereupon 101 rejected the call.

    Is there a way to eliminate the STUN settings that continue to show on the Status diagnostics page? I do not know if the device merely checks to see if a server can be contacted or if it is actually trying to use the STUN server.

    There is a lot of activity taking place within the log making it somewhat problematic to follow.
     
  7. jonathanc

    Joined:
    Sep 3, 2012
    Messages:
    64
    Likes Received:
    1
    I think the frequent "Not registered" entries in the log occur when I am trying out new settings in the Flexor's "Control Panel". I think this is probably also the reason for 101 rejecting a call - it's me trying out yet another combination in an effort to find one that works.

    Yes, Extension 101 is green (= registered) unless I put anything at all in the "SIP Outbound Proxy" box of the Flexor's Manual Settings page, when it turns red. I can confirm that when it's green the phone attached to the Flexor rings and can receive incoming calls, but cannot make outgoing calls or elicit any response from the 3CX PBX such as menu prompts.

    I have tried emptying all the STUN settings, and still no outbound calls were possible. I agree the logs are confusing: partly it's because of my many attempts to find a solution, but partly it's just the way the system is operating (or not!).

    The only settings in the "Other" page for extension 101 are Current Status: Available; Supports Re-Invite (checked); Support 'Replaces' header (checked); and Disallow use of extension outside the LAN (checked). I seized on this last one and unchecked it, but that didn't produce any different results; besides, it's also checked for the extensions which are working.

    Frankly, I'm on the verge of giving up and just accepting that the Flexor isn't compatible with 3CX - they don't seem to be talking to one another even on the most basic level of prompts. It's a shame, because the Flexor does its job very well when talking to DrayTEL direct - except that you can't transfer calls to another extension because it isn't an extension.

    Reluctantly, I guess I'll either have to forego the ability to transfer calls or else save up my pennies and invest in some guaranteed-compatible ATAs (or SIP phones, of course).

    But I am really grateful for all your help - and, of course, more than willing to try out any fresh ideas!

    All the very best

    jonathanc
     
  8. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,749
    Likes Received:
    285
    I suspect that your problems may be something to do with an internal dialplan on the unit.

    Given this...

    "have tried using the "#" key as a "send" key to no avail. Also, when the ATA is configured
    for direct connection to DrayTEL it is not necessary to press any key after dialling the
    number."

    The dialplan may be set by the Regional settings choice, or there may be some manual settings in there somewhere. If these were designed for a VoIP provider, to send to customers, with pre-set options (dialplans), then there may not be anything you can do.
     
  9. lneblett

    lneblett Well-Known Member

    Joined:
    Sep 7, 2010
    Messages:
    2,083
    Likes Received:
    61
    I found another manual and it does seem as if the "#" key is set as a send by default. And there is a 4 second timeout. I could not find dial plan settings or many of the others settings that a typical ata usually has. The only thing Icansuggest at this point is a wireshark capture. We know the sip gets through for the registration to occur, but all else either never occurs or is getting sent to somewhere other than 3cx.
     
  10. jonathanc

    Joined:
    Sep 3, 2012
    Messages:
    64
    Likes Received:
    1
    Many thanks, leejor, but that fact that I can configure it for DrayTEL seems to me to suggest that the unit has not been shipped with a pre-set, internal dialplan - unless I've missed your point.

    At your suggestion I modified the Regional Settings in 3CX to reflect my location: no change.

    lneblett, as you say, the sip seems to be getting through but nothing else - at least, not to 3CX. And yet it does to DrayTEL - a company whose service I have found excellent, but which is not the most flexible I've seen, so you'd think if they could handle whatever's coming out of the Flexor anybody could. Very strange. A Wireshark capture sounds a good idea - thank you - although I'm supposed to be working all over the weekend and on Monday, so unless I can steal even more time it looks as though that will have to wait until Tuesday.

    Thanks again, both of you. Have a good weekend.
     
  11. jonathanc

    Joined:
    Sep 3, 2012
    Messages:
    64
    Likes Received:
    1
    Sorry to post twice in a row, but I forgot to say that I also entered the appropriate regional settings in the Flexor, which is what I think you meant, leejor.

    I also forgot to say that it seems to me that what tells the Flexor where to send outgoing data is whatever is entered in its 'SIP Outbound Proxy' settings box; but whatever you enter in there - extension number, IP address of PC runnning 3CX, extension number@IP address, DrayTEL account details in various forms, nat.draytel.org - 3CX deregisters the extension.

    Apologies for the double post, but I thought it might save time.
     
  12. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,749
    Likes Received:
    285
    In theory, you should be able to leave the Outbound Proxy setting blank, and the SIP Registrar would be used. Of course every SIP device is going to behave differently. If anything were to be required, it should simply be the local IP of the 3CX server.

    This log...

    12:48:18.984 [CM504002]: Ext.101: a contact is unregistered. Contact(s): []
    12:47:06.703 [CM504001]: Ext.101: new contact is registered. Contact(s):

    So, unless you unplugged the ATA at 12:48:18, this leads me to believe that the device wants to be told how long to remain registered, and is not responding to the 30 minute re-registration time that 3CX should be sending. There is normally a manual setting that you can change, unless, perhaps, if the (your?) ATA is only meant to be used with certain VoIP providers. I had once bought a couple of unlocked (Motorola ATAs, I believe), that would eventually stop re-registering with 3CX. There was nothing in the device settings that would change that. They were originally designed to work with one particular VoIP provider.

    I'm not sure that this is the case with the Flexor, but it is a possibility. You may want to do some Google searches on using the Flexor with other PBX's. You may find some ideas on changing the settings.

    Do you have any 3CX logs of an outbound call attempt, the previous one was all incoming, then sent to Ext. 101, which was not registered. What happens when you try to place a call on the Flexor? Any 3Cx log at all?
     
  13. jonathanc

    Joined:
    Sep 3, 2012
    Messages:
    64
    Likes Received:
    1
    leejor, I'm sorry I clouded the issue by varying several parameters in the period covered by my last log. I've now conducted a clear-cut experiment as follows.

    I left the ATA's Outbound Proxy setting blank as you suggested.

    At 1810 I connected the PC to the ATA (and thereby to the LAN).

    At 1815 I made an incoming call from a PSTN phone: the phone which is connected to the ATA rang, I lifted the handset and had a brief but fascinating conversation with myself before hanging up.

    At 1820 I used the phone connected to the ATA to dial out to the PSTN number: after the DTMF sequence there was silence. I waited 5 seconds then pressed the "#" key. Still silence. So I hung up.

    The log is given below. Extension 102 is the ATA; extension 103 is 3CXPhone on the PC running 3CX Phone System.

    As you can see, 3CX seems unaware of any activity after the incoming call - strange.

    Entering the local IP of the 3CX server in the Flexor's Outbound Proxy box simply causes 3CX to deregister the extension.

    I do hope it doesn't turn out that I've been incredibly stupid all along and failed to do something obvious; but I can't see it at the moment.


    18:15:19.321 [CM503008]: Call(2): Call is terminated
    18:15:11.524 [CM503007]: Call(2): Device joined: sip:102@192.168.1.6:5060
    18:15:11.508 [CM503007]: Call(2): Device joined: sip:8115773@draytel.org:5060
    18:15:05.602 [CM505001]: Ext.102: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Camrivox Flexor 151 2.36] PBX contact: [sip:102@192.168.1.3:5060]
    18:15:05.586 [CM503002]: Call(2): Alerting sip:102@192.168.1.6:5060
    18:15:05.492 [CM503025]: Call(2): Calling Ext:Ext.102@[Dev:sip:102@192.168.1.6:5060]
    18:15:05.430 [CM503004]: Call(2): Route 1: Ext:Ext.102@[Dev:sip:102@192.168.1.6:5060]
    18:15:05.430 [CM503010]: Making route(s) to <sip:102@192.168.1.3:5060>
    18:15:05.414 [CM505003]: Provider:[Draytel] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [voip] PBX contact: [sip:8115773@5.61.196.247:1043]
    18:15:05.399 [CM503001]: Call(2): Incoming call from 01994419834@(Ln.10000@Draytel) to <sip:102@192.168.1.3:5060>
    18:15:04.508 [CM503012]: Inbound any hours rule (Personal) for 10000 forwards to DN:102
    18:10:19.727 [CM504001]: Ext.102: new contact is registered. Contact(s): [sip:102@192.168.1.6:5060/102]
    18:10:15.602 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server [ V4 199.192.206.228:3478 UDP target domain=unspecified mFlowKey=0 ] over Transport [ V4 192.168.1.3:5060 UDP target domain=unspecified mFlowKey=0 ]
    18:10:10.758 [CM504004]: Registration succeeded for: 10000@Draytel
    18:10:09.071 [CM504001]: Ext.103: new contact is registered. Contact(s): [sip:103@127.0.0.1:1066;rinstance=cb09a4359c3c9aa2/103]
    18:10:08.930 [CM504003]: Sent registration request for 10000@Draytel
    18:10:08.821 IP(s) added:[192.168.1.3]
     
  14. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,749
    Likes Received:
    285
    So, if I'm understanding this correctly...you were able to receive a call on the ATA. This issue of it un-registering is still there or not?

    You are not seeing any sign of a dialled call in the 3CX logs? If not then it may be trying to send it elsewhere.

    If you want to pursue this...the next thing I would do is connect to connect a hub (you can't use a switch, it must be an older hub) between the ATA and your network, plug a PC running Wireshark into the hub as well and see what, if anything is being sent out after you place a call. It may give some clues as to what is going on and if there is a chance to do anything about it.

    As I mentioned earlier, you may find some help on other sites, from people trying to use this device with other VoIP PBX's or providers. Perhaps there is a hidden menu somewhere that allows for more a detailed configuration.
     
  15. jonathanc

    Joined:
    Sep 3, 2012
    Messages:
    64
    Likes Received:
    1
    Thanks, leejor. Yes, whenever anything at all is entered in the SIP Outbound Proxy settings box on the Flexor, 3CX deregisters the extension.

    And no, there is no sign in the 3CX log of any attempt to make an outgoing call via the Flexor.

    Your suggestion of a hub and Wireshark sounds an excellent one, and if I had an old-type hub and a bit more time it would be very interesting to discover just what is coming out of the Flexor - if anything.

    However, I don't have an old hub, and I can't help feeling that since the unit cost under £20 I'd be better off cutting my losses and going for a 3CX-recommended SIP phone rather than spending more time battling with this recalcitrant ATA.

    I hate being defeated, and it would be satisfying to get to the bottom of the problem. However, I think I'll just have to put it on the back burner for now.

    Thanks again for all your help.
     
  16. lneblett

    lneblett Well-Known Member

    Joined:
    Sep 7, 2010
    Messages:
    2,083
    Likes Received:
    61
    I think your decision to move along to something else is likely the prudent one. While I can't say that I saw all the available settings, I did not get the feeling that the device was truly made for custom installations that might require settings to enable optimization for the lines or the applications. It would have been a shame to get the device working only to discover call quality issues where you didn't have the settings to overcome. Further, I suppose there is always the risk that as 3CX evolves, given the unsupported nature of the device, there could have been a change that might have put you back to square one. Both Grandstream and Patton make excellent ATAs ar fairly reasonable prices.
     
  17. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,749
    Likes Received:
    285
    Hold on to it, do a search of the device, on the net once in a while. One day you may come across someone else that has managed to "crack" it. Keep an eye open for an old hub at a thrift store/flea market/rummage/boot sale, they usually go for not much more than some change.
     
  18. jonathanc

    Joined:
    Sep 3, 2012
    Messages:
    64
    Likes Received:
    1
    Will do!

    Thanks
     
Thread Status:
Not open for further replies.