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.

3CX and Cisco Router

Discussion in '3CX Phone System - General' started by Stormblue, May 9, 2011.

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

    Joined:
    May 9, 2011
    Messages:
    2
    Likes Received:
    0
    Hi everyone,
    We are trying to get our brand new 3CX up and running. Right now, we have a problem with the setup of our Cisco 2811 router with the E1-Card inside.
    Does anyone have a config example, how to setup the Cisco box to talk to the 3CX?

    Here's the error from the 3CX log:
    *****snip*****
    20:15:31.344 [CM500002]: Unidentified incoming call. Review INVITE and adjust source identification:
    INVITE sip:420xxx@192.168.60.100:5060 SIP/2.0
    Via: SIP/2.0/UDP 192.168.60.1:5060;branch=z9hG4bKFA898;x-route-tag="tgrp:xxx"
    Max-Forwards: 70
    Contact: <sip:1723232xxx@192.168.60.1:5060>
    To: <sip:420xxx@192.168.60.100>
    From: <sip:1723232xxx@192.168.60.100>;tag=27001210-10BF
    Call-ID: 28A777D7-799F11E0-8609BE80-9495B42D@192.168.60.1
    CSeq: 101 INVITE
    Expires: 300
    Min-SE: 1800
    Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
    Date: Mon, 09 May 2011 18:15:30 GMT
    Supported: 100rel, timer, resource-priority, replaces, sdp-anat
    Timestamp: 1304964930
    User-Agent: Cisco-SIPGateway/IOS-12.x
    Allow-Events: telephone-event
    Content-Length: 0
    Remote-Party-ID: <sip:1723232xxx@192.168.60.1>;party=calling;screen=yes;privacy=off
    Cisco-Guid: 681863951-2040467936-2449211428-335708344

    20:15:31.344 [CM302001]: Authorization system can not identify source of: SipReq: INVITE 420xxx@192.168.60.100:5060 tid=FA898 cseq=INVITE contact=1723232xxx@192.168.60.1:5060 / 101 from(wire)
    *****/snip*****

    Any help would be appreciated...
    Thanks,
    Oliver
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  2. davidbenwell

    davidbenwell Active Member

    Joined:
    Apr 27, 2010
    Messages:
    704
    Likes Received:
    0
    can you run the 3CX Firewall Checker

    you can find this within the 3CX console under the settings menu

    post the resaults here for us to check

    you may find this URL useful http://www.3cx.com/blog/voip-howto/cisco-voip-configuration/
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. Stormblue

    Joined:
    May 9, 2011
    Messages:
    2
    Likes Received:
    0
    Hi,
    the output from the firewall checker is at the end of this post.
    Just as a reminder: I don't have a problem with the internet connection. This is working fine. But I do have a problem with our phone connection. And the Cisco router is not a firewall, but a PBX gateway.

    Some more information, that might be helpful:
    - both systems, 3cx and the router are in the same subnet (router: 192.168.60.1, 3cx 192.168.60.100)
    - There's no firewall between the systems
    - We use a dedicated public IP to allow the recommended ports to the 3cx and have already successfully enabled a bridge to a partner company, also running a 3cx. So the connection to the internet is working fine.

    All the best,
    Oliver

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

    <11:12:09>: Phase 1, checking servers connection, please wait...
    <11:12:09>: Stun Checker service is reachable. Phase 1 check passed.
    <11:12:09>: Phase 2a, Check Port Forwarding to UDP SIP port, please wait...
    <11:12:16>: UDP SIP Port is set to 5060. Response received correctly with no translation. Phase 2a check passed.

    <11:12:16>: Phase 2b. Check Port Forwarding to TCP SIP port, please wait...
    <11:12:21>: TCP SIP Port is set to 5060. Response received correctly with no translation. Phase 2b check passed.

    <11:12:21>: Phase 3. Check Port Forwarding to TCP Tunnel port, please wait...
    <11:12:25>: TCP TUNNEL Port is set to 5090. Response received correctly with no translation. Phase 3 check passed.

    <11:12:25>: Phase 4. Check Port Forwarding to RTP external port range, please wait...
    <11:12:35>: UDP RTP Port 9000. Response received correctly with no translation. Phase 4-01 check passed.
    <11:12:40>: UDP RTP Port 9001. Response received correctly with no translation. Phase 4-02 check passed.
    <11:12:44>: UDP RTP Port 9002. Response received correctly with no translation. Phase 4-03 check passed.
    <11:12:49>: UDP RTP Port 9003. Response received correctly with no translation. Phase 4-04 check passed.
    <11:12:53>: UDP RTP Port 9004. Response received correctly with no translation. Phase 4-05 check passed.
    <11:12:58>: UDP RTP Port 9005. Response received correctly with no translation. Phase 4-06 check passed.
    <11:13:02>: UDP RTP Port 9006. Response received correctly with no translation. Phase 4-07 check passed.
    <11:13:07>: UDP RTP Port 9007. Response received correctly with no translation. Phase 4-08 check passed.
    <11:13:11>: UDP RTP Port 9008. Response received correctly with no translation. Phase 4-09 check passed.
    <11:13:16>: UDP RTP Port 9009. Response received correctly with no translation. Phase 4-10 check passed.
    <11:13:20>: UDP RTP Port 9010. Response received correctly with no translation. Phase 4-11 check passed.
    <11:13:25>: UDP RTP Port 9011. Response received correctly with no translation. Phase 4-12 check passed.
    <11:13:29>: UDP RTP Port 9012. Response received correctly with no translation. Phase 4-13 check passed.
    <11:13:34>: UDP RTP Port 9013. Response received correctly with no translation. Phase 4-14 check passed.
    <11:13:38>: UDP RTP Port 9014. Response received correctly with no translation. Phase 4-15 check passed.
    <11:13:43>: UDP RTP Port 9015. Response received correctly with no translation. Phase 4-16 check passed.
    <11:13:47>: UDP RTP Port 9016. Response received correctly with no translation. Phase 4-17 check passed.
    <11:13:52>: UDP RTP Port 9017. Response received correctly with no translation. Phase 4-18 check passed.
    <11:13:56>: UDP RTP Port 9018. Response received correctly with no translation. Phase 4-19 check passed.
    <11:14:01>: UDP RTP Port 9019. Response received correctly with no translation. Phase 4-20 check passed.
    <11:14:05>: UDP RTP Port 9020. Response received correctly with no translation. Phase 4-21 check passed.
    <11:14:10>: UDP RTP Port 9021. Response received correctly with no translation. Phase 4-22 check passed.
    <11:14:14>: UDP RTP Port 9022. Response received correctly with no translation. Phase 4-23 check passed.
    <11:14:19>: UDP RTP Port 9023. Response received correctly with no translation. Phase 4-24 check passed.
    <11:14:23>: UDP RTP Port 9024. Response received correctly with no translation. Phase 4-25 check passed.
    <11:14:28>: UDP RTP Port 9025. Response received correctly with no translation. Phase 4-26 check passed.
    <11:14:32>: UDP RTP Port 9026. Response received correctly with no translation. Phase 4-27 check passed.
    <11:14:37>: UDP RTP Port 9027. Response received correctly with no translation. Phase 4-28 check passed.
    <11:14:41>: UDP RTP Port 9028. Response received correctly with no translation. Phase 4-29 check passed.
    <11:14:46>: UDP RTP Port 9029. Response received correctly with no translation. Phase 4-30 check passed.
    <11:14:56>: UDP RTP Port 9030. Response received correctly with no translation. Phase 4-31 check passed.
    <11:15:00>: UDP RTP Port 9031. Response received correctly with no translation. Phase 4-32 check passed.
    <11:15:05>: UDP RTP Port 9032. Response received correctly with no translation. Phase 4-33 check passed.
    <11:15:09>: UDP RTP Port 9033. Response received correctly with no translation. Phase 4-34 check passed.
    <11:15:14>: UDP RTP Port 9034. Response received correctly with no translation. Phase 4-35 check passed.
    <11:15:18>: UDP RTP Port 9035. Response received correctly with no translation. Phase 4-36 check passed.
    <11:15:23>: UDP RTP Port 9036. Response received correctly with no translation. Phase 4-37 check passed.
    <11:15:27>: UDP RTP Port 9037. Response received correctly with no translation. Phase 4-38 check passed.
    <11:15:32>: UDP RTP Port 9038. Response received correctly with no translation. Phase 4-39 check passed.
    <11:15:36>: UDP RTP Port 9039. Response received correctly with no translation. Phase 4-40 check passed.
    <11:15:41>: UDP RTP Port 9040. Response received correctly with no translation. Phase 4-41 check passed.
    <11:15:45>: UDP RTP Port 9041. Response received correctly with no translation. Phase 4-42 check passed.
    <11:15:50>: UDP RTP Port 9042. Response received correctly with no translation. Phase 4-43 check passed.
    <11:15:54>: UDP RTP Port 9043. Response received correctly with no translation. Phase 4-44 check passed.
    <11:15:59>: UDP RTP Port 9044. Response received correctly with no translation. Phase 4-45 check passed.
    <11:16:03>: UDP RTP Port 9045. Response received correctly with no translation. Phase 4-46 check passed.
    <11:16:08>: UDP RTP Port 9046. Response received correctly with no translation. Phase 4-47 check passed.
    <11:16:12>: UDP RTP Port 9047. Response received correctly with no translation. Phase 4-48 check passed.
    <11:16:17>: UDP RTP Port 9048. Response received correctly with no translation. Phase 4-49 check passed.
    <11:16:21>: UDP RTP Port 9049. Response received correctly with no translation. Phase 4-50 check passed.


    Application exit code is 0
    ***** /snip *****
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  4. willow

    willow Member

    Joined:
    Mar 1, 2011
    Messages:
    471
    Likes Received:
    0
    you may want to check your DID setup on the 3cx. when you built the sip trunk provider on the 3cx you had to use 1 number for the authenticaiton. did you test that number and does it work?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. netswork

    netswork Active Member

    Joined:
    Mar 11, 2011
    Messages:
    577
    Likes Received:
    1
    If you are able to get this to work I would be extremley interested in a copy/example of your configuration. I am needing to do the same thing with a T1 interface. I have tried this previously with asterisk and was unable to ever get a working configuration. I have seen one post in these forums about someone who got it to work but outbound DTMF would not pass. I have not seen that persons configuration though.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  6. netswork

    netswork Active Member

    Joined:
    Mar 11, 2011
    Messages:
    577
    Likes Received:
    1
    I found this post in another discussion, not sure if it might help.

    Hi all,

    can anyone provide a working example for a connection between a 3cx system and a Cisco 2811 (IOS 124.22T) router with PRI ?

    My config example:

    dial-peer voice 20000 voip
    description xxxx
    destination-pattern xxxx..
    voice-class codec 1
    session protocol sipv2
    session target ipv4:192.168.60.100
    dtmf-relay rtp-nte
    no vad

    sip-ua
    credentials username 20000 password xxxxxxx realm 3CXPhoneSystem
    authentication username 20000 password xxxxxx retry invite 3
    retry response 3
    retry bye 3
    retry cancel 3
    timers expires 300000
    registrar ipv4:192.168.60.100 expires 300
    sip-server ipv4:192.168.60.100:5060

    i have an outbound pots peer aswell

    unfortunately, the router get´s blacklisted on the 3cx system...
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  7. netswork

    netswork Active Member

    Joined:
    Mar 11, 2011
    Messages:
    577
    Likes Received:
    1
    I found this post back from 2007 in these forums....let me know if this helps at all:


    I have a Cisco 2621XM router and have successfully configured it so that it acts as my VoIP gateway.

    Hardware configuration is as follows:

    NM-HD-2V with 1 2-port VIC2-2FXO card
    IOS version: c2600-ipvoicek9-mz.124-9.T5.bin

    Here's the necessary configuration to get things working on the Cisco router with 3CX PBX.

    The code below tells the router what kind of VoIP service to use, which is set to sip

    voice service voip
    sip

    Next, define the codecs you wish to you in order of preference.

    voice class codec 1
    codec preference 1 g711ulaw
    codec preference 2 g729r8 bytes 40
    codec preference 3 g723r63 bytes 96
    codec preference 4 g726r16 bytes 80

    Next configure your voice ports. This example is only for the first voice port. The last line is the most important as it tell the port what extension to dial on inbound call. The opx parameter tells the router that the extension is an off premise extension.

    voice-port 1/0/0
    no battery-reversal
    timing hookflash-out 50
    connection plar opx 999

    Next program your dial-peers. Pick any arbitrary number for your dial-peers but they should make some sense to you. I've chosen 20000 for my voip dial-peer, which is used for inbound calls. If you have more than one voip dial-peer, set the preference order.

    dial-peer voice 20000 voip
    preference 1
    destination-pattern 99.
    voice-class codec 1
    session protocol sipv2
    session target ipv4:192.168.253.5 --> address of 3CX server
    dtmf-relay rtp-nte
    no vad

    Next program your POTS dial-peer.

    dial-peer voice 10000 pots
    preference 1 --> use if you have multiple POTS dial-peers
    destination-pattern .T
    port 1/0/0 --> matches your dial-peer with physcial port

    Next program the SIP user agent parameters. The "authentication" parameter is used to authenticate the Cisco router against the gateway you programmed in the 3CX server.

    sip-ua
    authentication username 10000 password 091D1E594955
    retry invite 3
    retry response 3
    retry bye 3
    retry cancel 3
    timers expires 300000
    registrar ipv4:192.168.253.5 expires 300
    sip-server ipv4:192.168.253.5:5060

    The above should work for any Cisco router that supports VoIP.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  8. netswork

    netswork Active Member

    Joined:
    Mar 11, 2011
    Messages:
    577
    Likes Received:
    1
    I got some friends to send me some configs...keep in mind this is for a cisco call manager but it is still using this router as a SIP gateway so it should be very similar.


    voice call send-alert
    !
    voice service voip
    address-hiding
    allow-connections sip to sip
    redirect ip2ip
    fax protocol t38 ls-redundancy 0 hs-redundancy 0 fallback pass-through g711ulaw
    h323
    sip
    header-passing error-passthru
    asserted-id pai
    midcall-signaling passthru
    privacy-policy passthru
    g729 annexb-all
    !
    !
    !
    voice class codec 1
    codec preference 1 g729r8
    codec preference 2 g711ulaw
    voice translation-rule 1
    rule 1 /^91\(.*\)/ /\1/
    rule 2 /^9\(.*\)/ /\1/

    voice translation-profile DIGITSTRIP_9
    translate called 1

    dial-peer voice 100 voip
    description Inbound SIP Dial-Peer for XXXXXXXXXX DIDs to Publisher from ATT
    preference 2
    destination-pattern ..........
    rtp payload-type nse 99
    rtp payload-type nte 100
    voice-class codec 1
    voice-class sip profiles 1
    session protocol sipv2
    session target ipv4:10.x.x.x
    dtmf-relay rtp-nte
    fax-relay sg3-to-g3
    !
    dial-peer voice 101 voip
    description Inbound SIP Dial-Peer for XXXXXXXXXX DIDs to Subscriber01 from A
    preference 1
    destination-pattern ..........
    rtp payload-type nse 99
    rtp payload-type nte 100
    voice-class codec 1
    voice-class sip profiles 1
    session protocol sipv2
    session target ipv4:10.x.x.x
    dtmf-relay rtp-nte
    fax-relay sg3-to-g3
    !
    dial-peer voice 200 voip
    description Outbound SIP Dial-Peer for National Dialing to ATT Primary
    translation-profile outgoing DIGITSTRIP_9
    preference 1
    destination-pattern 9[2-9]..[2-9]......
    rtp payload-type nse 99
    rtp payload-type nte 100
    voice-class codec 1
    voice-class sip privacy-policy passthru
    voice-class sip early-offer forced
    voice-class sip profiles 1
    session protocol sipv2
    session target ipv4:12.x.x.x
    incoming called-number .
    dtmf-relay rtp-nte
    fax-relay sg3-to-g3
    fax rate 14400
    !
    dial-peer voice 201 voip
    description Outbound SIP Dial-Peer for National Dialing to ATT Secondary
    translation-profile outgoing DIGITSTRIP_9
    preference 2
    destination-pattern 9[2-9]..[2-9]......
    rtp payload-type nse 99
    rtp payload-type nte 100
    voice-class codec 1
    voice-class sip privacy-policy passthru
    voice-class sip early-offer forced
    voice-class sip profiles 1
    session protocol sipv2
    session target ipv4:12.x.x.x
    incoming called-number .
    dtmf-relay rtp-nte
    fax-relay sg3-to-g3
    fax rate 14400
    !
    dial-peer voice 202 voip
    description Outbound SIP Dial-Peer for LongDistance Dialing to ATT Primary
    translation-profile outgoing DIGITSTRIP_9
    preference 1
    destination-pattern 91[2-9]..[2-9]......
    rtp payload-type nse 99
    rtp payload-type nte 100
    voice-class codec 1
    voice-class sip privacy-policy passthru
    voice-class sip early-offer forced
    voice-class sip profiles 1
    session protocol sipv2
    session target ipv4:12.x.x.x
    dtmf-relay rtp-nte
    fax-relay sg3-to-g3
    fax rate 14400
    !
    dial-peer voice 203 voip
    description Outbound SIP Dial-Peer for LongDistance Dialing to ATT Secondary
    translation-profile outgoing DIGITSTRIP_9
    preference 2
    destination-pattern 91[2-9]..[2-9]......
    rtp payload-type nse 99
    rtp payload-type nte 100
    voice-class codec 1
    voice-class sip privacy-policy passthru
    voice-class sip early-offer forced
    voice-class sip profiles 1
    session protocol sipv2
    session target ipv4:12.x.x.x
    dtmf-relay rtp-nte
    fax-relay sg3-to-g3
    fax rate 14400
    !
    dial-peer voice 204 voip
    description Outbound SIP Dial-Peer for InterNational Dialing to ATT Primary
    translation-profile outgoing DIGITSTRIP_9
    preference 1
    destination-pattern 9011T
    rtp payload-type nse 99
    rtp payload-type nte 100
    voice-class codec 1
    voice-class sip early-offer forced
    voice-class sip profiles 1
    session protocol sipv2
    session target ipv4:12.x.x.x
    dtmf-relay rtp-nte
    fax-relay sg3-to-g3
    fax rate 14400
    !
    dial-peer voice 205 voip
    description Outbound SIP Dial-Peer for InterNational Dialing to ATT Secondar
    translation-profile outgoing DIGITSTRIP_9
    preference 2
    destination-pattern 9011T
    rtp payload-type nse 99
    rtp payload-type nte 100
    voice-class codec 1
    voice-class sip early-offer forced
    voice-class sip profiles 1
    session protocol sipv2
    session target ipv4:12.x.x.x
    dtmf-relay rtp-nte
    fax-relay sg3-to-g3
    fax rate 14400
    !
    dial-peer voice 206 voip
    description Outbound SIP Dial-Peer for Emergency Dialing to ATT Primary
    translation-profile outgoing DIGITSTRIP_9
    preference 1
    destination-pattern 911
    rtp payload-type nse 99
    rtp payload-type nte 100
    voice-class codec 1
    voice-class sip early-offer forced
    voice-class sip profiles 1
    session protocol sipv2
    session target ipv4:12.x.x.x
    dtmf-relay rtp-nte
    fax-relay sg3-to-g3
    fax rate 14400
    !
    dial-peer voice 207 voip
    description Outbound SIP Dial-Peer for Emergency Dialing to ATT Secondary
    translation-profile outgoing DIGITSTRIP_9
    preference 2
    destination-pattern 911
    rtp payload-type nse 99
    rtp payload-type nte 100
    voice-class codec 1
    voice-class sip early-offer forced
    voice-class sip profiles 1
    session protocol sipv2
    session target ipv4:12.x.x.x
    dtmf-relay rtp-nte
    fax-relay sg3-to-g3
    fax rate 14400
    !
    dial-peer voice 208 voip
    description Outbound SIP Dial-Peer for Information Dialing to ATT Primary
    translation-profile outgoing DIGITSTRIP_9
    preference 1
    destination-pattern 9411
    rtp payload-type nse 99
    rtp payload-type nte 100
    voice-class codec 1
    voice-class sip early-offer forced
    voice-class sip profiles 1
    session protocol sipv2
    session target ipv4:12.x.x.x
    dtmf-relay rtp-nte
    fax-relay sg3-to-g3
    fax rate 14400
    !
    dial-peer voice 209 voip
    description Outbound SIP Dial-Peer for Emergency Information to ATT Secondar
    translation-profile outgoing DIGITSTRIP_9
    preference 2
    destination-pattern 9411
    rtp payload-type nse 99
    rtp payload-type nte 100
    voice-class codec 1
    voice-class sip early-offer forced
    voice-class sip profiles 1
    session protocol sipv2
    session target ipv4:12.x.x.x
    dtmf-relay rtp-nte
    fax-relay sg3-to-g3
    fax rate 14400
    !
    !
    sip-ua
    no remote-party-id
    retry invite 2
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  9. smtharrison

    Joined:
    Mar 13, 2012
    Messages:
    17
    Likes Received:
    1
    Any of you guys been able to setup a cisco router as a T1 gateway? Have a cisco voip supported router with both a chanelized and regular T1 hwic. noob with T1's in general. Thanks!
     
Thread Status:
Not open for further replies.