Configuring Patton SN-4634 VoIP gateway

Discussion in '3CX Phone System - General' started by Zeljko, Oct 10, 2007.

  1. Zeljko

    Joined:
    Sep 25, 2007
    Messages:
    10
    Likes Received:
    0
    Is there anybody that know how to configure Patton SN-4634 ISDN BRI gateway with 3CX?
    I was find on VoIP Gateway config. guides http://www.3cx.com/voip-gateways/smartnode-isdn.html that there is in Gateway Created section some button "Generate config file" but I can't find it.

    Please help!
     
  2. 5qg4

    5qg4 Active Member

    Joined:
    Jan 31, 2007
    Messages:
    643
    Likes Received:
    0
    Please try to modify the IP address, virtual extension and password of virtual extension this sample cfg file then import to your device. Please backup your existing cfg first. Hope this can help.

    WAN IP: 10.39.100.251
    Default gateway: 10.39.100.254
    PBX IP: 10.39.100.252
    virtual extension: 1001
    virtual extension PWD: 1001

    sample cfg for SN-4634
    -------------------------------
    cli version 3.20
    webserver port 80 language en
    sntp-client
    sntp-client server primary 10.39.100.252 port 123 version 4
    system hostname SN4634

    system

    ic voice 0

    system
    clock-source internal

    profile ppp default

    profile tone-set default

    profile voip default
    codec 1 g711alaw64k rx-length 20 tx-length 20
    codec 2 g711ulaw64k rx-length 20 tx-length 20

    profile pstn default

    profile sip default

    profile aaa default
    method 1 local
    method 2 none

    context ip router

    interface ETH0_0
    ipaddress 10.39.100.251 255.255.255.0
    tcp adjust-mss rx mtu
    tcp adjust-mss tx mtu

    interface ETH0_1
    ipaddress 192.168.1.1 255.255.255.0
    tcp adjust-mss rx mtu
    tcp adjust-mss tx mtu

    context ip router
    route 0.0.0.0 0.0.0.0 10.39.100.254 0

    context cs switch
    digit-collection timeout 4
    no digit-collection terminating-char
    address-completion timeout 20
    national-prefix 0
    international-prefix 00

    routing-table called-e164 TAB-OUT
    route .%T dest-service BRIHUNT MT_ITC

    mapping-table itc to itc MT_ITC
    map default to speech

    interface isdn BRI0_0
    route call dest-interface SIP_1
    address-complete-indication emit set

    interface isdn BRI0_1
    route call dest-interface SIP_1
    address-complete-indication emit set

    interface isdn BRI0_2
    route call dest-interface SIP_1
    address-complete-indication emit set

    interface isdn BRI0_3
    route call dest-interface SIP_1
    address-complete-indication emit set

    interface sip SIP_1
    bind gateway AST_1
    service default
    route call dest-table TAB-OUT
    remote-party-id called-party
    remote-party-id calling-party

    service hunt-group BRIHUNT
    drop-cause normal-unspecified
    drop-cause no-circuit-channel-available
    drop-cause network-out-of-order
    drop-cause temporary-failure
    drop-cause switching-equipment-congestion
    drop-cause access-info-discarded
    drop-cause circuit-channel-not-available
    drop-cause resources-unavailable
    drop-cause user-busy
    drop-cause destination-out-of-order
    route call 1 dest-interface BRI0_0
    route call 2 dest-interface BRI0_1
    route call 3 dest-interface BRI0_2
    route call 4 dest-interface BRI0_3
    route call 5 dest-interface BRI0_0
    route call 6 dest-interface BRI0_1
    route call 7 dest-interface BRI0_2
    route call 8 dest-interface BRI0_3

    context cs switch
    no shutdown

    gateway sip AST_1
    bind interface ETH0_0 router

    service default
    default-server 10.39.100.252 loose-router
    registration-lifetime 1000
    registrar 10.39.100.252
    user 1001 display-name 1001 password 1001

    gateway sip AST_1
    no shutdown

    port ethernet 0 0
    medium auto
    encapsulation ip
    bind interface ETH0_0 router
    no shutdown

    port ethernet 0 1
    medium auto
    encapsulation ip
    bind interface ETH0_1 router
    no shutdown

    port bri 0 0
    clock auto
    encapsulation q921

    q921
    protocol pp
    uni-side auto
    encapsulation q931

    q931
    protocol dss1
    uni-side user
    encapsulation cc-isdn
    bind interface BRI0_0 switch

    port bri 0 0
    no shutdown

    port bri 0 1
    clock auto
    encapsulation q921

    q921
    protocol pp
    uni-side auto
    encapsulation q931

    q931
    protocol dss1
    uni-side user
    encapsulation cc-isdn
    bind interface BRI0_1 switch

    port bri 0 1
    no shutdown

    port bri 0 2
    clock auto
    encapsulation q921

    q921
    protocol pp
    uni-side auto
    encapsulation q931

    q931
    protocol dss1
    uni-side user
    encapsulation cc-isdn
    bind interface BRI0_2 switch

    port bri 0 2
    no shutdown

    port bri 0 3
    clock auto
    encapsulation q921

    q921
    protocol pp
    uni-side auto
    encapsulation q931

    q931
    protocol dss1
    uni-side user
    encapsulation cc-isdn
    bind interface BRI0_3 switch

    port bri 0 3
    no shutdown

    port bri 0 4
    clock auto
    encapsulation q921

    q921
    protocol pmp
    uni-side auto
    encapsulation q931

    q931
    protocol dss1
    uni-side net

    port bri 0 4
    shutdown
     
  3. Zeljko

    Joined:
    Sep 25, 2007
    Messages:
    10
    Likes Received:
    0
    Patton SN4634 config problems

    Hi Ricky,

    Thank you very much for config file for Patton 4634, now is gateway registered but we still have a problems when we try to call ISDN numbers from outside.
    So we cannot get incoming calls via Patton gateway.

    This is server log for this problem:

    [CM010001] Line configuration does not allow identification of the source of this call. Check Advanced Options for Gateways and Providers and match a field to a correct value from the following: Contact IP: '192.168.178.70'; From: '6195094'; To: '013751277'; Rline: '013751277'; Contact: '6195094'

    Maybe we need to put MSN numbers somewhere in patton?
    If you know where is the problem please let me know.

    Thanks a lot!

    zeljko
     
  4. miraportuga

    miraportuga Member

    Joined:
    Aug 7, 2007
    Messages:
    297
    Likes Received:
    0
    Go to the patton gateway configuration under 3cx Web admin page, "Other Options", select "Use ip in contacts" and below put 192.168.178.70

    you should have no problem after that

    Cheers
     
  5. Zeljko

    Joined:
    Sep 25, 2007
    Messages:
    10
    Likes Received:
    0
    Patton SN4634 config problems

    Hi,

    we are change this option on 3CX but still don't work.

    this is new server log:
    [CM210001] Ambiguous configuration.3 source lines correspond to incoming call.INVITE Parameters: Contact IP: '192.168.178.70'; From: '6195094'; To: '013751277'; Rline: '013751277'; Contact: '6195094'. Line:CfgExtLine:1001 used as fallback!

    any other idea?

    zeljko
     
  6. miraportuga

    miraportuga Member

    Joined:
    Aug 7, 2007
    Messages:
    297
    Likes Received:
    0
    Tell me something, thats a 4 port gateway or something? (im not familiar with parrong devices)
    If so, on 3CX Web admin page you have 1 line? or 4 lines? for all 4 ports of the gateway ? If im not wrong you will have to do the same thing on each line you have set up there coming from patton....
    If that doesnt help then... i dont know :|

    Cheers
     
  7. Zeljko

    Joined:
    Sep 25, 2007
    Messages:
    10
    Likes Received:
    0
    Yes, this is ISDN 3BRI gateway (3 BRI digital lines) but each line have a 2 channels.
    So, we have 3 registered PSTN lines on 3CX and all are green.
    but cannot receive call throuth this gateway.
     
  8. 5qg4

    5qg4 Active Member

    Joined:
    Jan 31, 2007
    Messages:
    643
    Likes Received:
    0
    Hi Zeljko,

    All works except inbound calls? Or just can register 3CX box?
     
  9. Nick Galea

    Nick Galea Site Admin

    Joined:
    Jun 6, 2006
    Messages:
    1,677
    Likes Received:
    17
    Did you use the generated config file?

    Also check that your ISDN lines are point to point or point to multi point.

    Then check that the gateway is set to same, ie that it expects same type of lines. You have to issue a command to do this (dont have it handy but should be in config file or patton manual)

    Once thats checked, make inbound call check server status log and post here....
     
  10. Zeljko

    Joined:
    Sep 25, 2007
    Messages:
    10
    Likes Received:
    0
    Hi Ricky,

    Yes, outbound calls via this Patton IAD works fine, we only cannot get inbound calls. And all 3 BRI lines are registered.

    Zeljko
     
  11. 5qg4

    5qg4 Active Member

    Joined:
    Jan 31, 2007
    Messages:
    643
    Likes Received:
    0
    Hi Zeljko,

    Can you post the debug trace of SmartNode when use command below.
    #debug ccisdn error
    #debug ccisdn signaling
    #debug isdn error

    Then place one call to your SN. I just make sure that any DID into your SN.
     
  12. Zeljko

    Joined:
    Sep 25, 2007
    Messages:
    10
    Likes Received:
    0
    Hi Nick,

    The config file generated via 3CX definitelly don't work bcz. my Patton hang-on after we import this config file.
    On the other side the config file which I get from Ricky works but have problems with inbound calls only.

    Please check what is wrong with config script in 3CX vizard.
    Tray to make config from your side for Patton 4634.

    Zeljko
     
  13. deangelisg

    Joined:
    Nov 9, 2007
    Messages:
    4
    Likes Received:
    0
    Problem to call with 4634

    Hi, I installed patton 4634 with 3cx, on the patton there are 2 isdn point to multipoint, i check the configuration for isdn interface was appropiately for pmp, my problem is:
    on call incaming i can receive 4 calls togheter (2 for each isdn line)
    in outgoing i can call only 2 calls
    I try to change line on the bri, the patton call only on the bri 0/0.
    I post the configuration

    webserver port 80 language en

    system

    ic voice 0
    low-bitrate-codec g729

    system
    clock-source 0 0

    profile ppp default

    profile tone-set default

    profile voip default
    codec 1 g711alaw64k rx-length 20 tx-length 20
    codec 2 g711ulaw64k rx-length 20 tx-length 20

    profile pstn default

    profile sip default

    profile aaa default
    method 1 local
    method 2 none

    context ip router

    interface eth0
    ipaddress dhcp
    tcp adjust-mss rx mtu
    tcp adjust-mss tx mtu

    interface eth1
    ipaddress 192.168.4.151 255.255.255.0
    tcp adjust-mss rx mtu
    tcp adjust-mss tx mtu

    context cs switch

    interface isdn isdnif0
    route call dest-interface sipif0

    interface isdn isdnif1
    route call dest-interface sipif1

    interface sip sipif0
    bind gateway sipgw0
    service default
    route call dest-interface isdnif0
    remote-party-id called-party
    address-translation outgoing-call request-uri user-part fix 10000 host-part to-header target-param none
    address-translation incoming-call called-e164 request-uri

    interface sip sipif1
    bind gateway sipgw1
    service default
    route call dest-interface isdnif1
    remote-party-id called-party
    address-translation outgoing-call request-uri user-part fix 10001 host-part to-header target-param none
    address-translation incoming-call called-e164 request-uri

    context cs switch
    no shutdown

    gateway sip sipgw0
    bind interface eth1 router

    service default
    domain 192.168.4.200
    authentication 10000 password 10000 default
    default-server 192.168.4.200 loose-router
    registrar 192.168.4.200
    user 10000

    gateway sip sipgw0
    no shutdown

    gateway sip sipgw1
    bind interface eth1 router

    service default
    domain 192.168.4.200
    authentication 10001 password 10001 default
    default-server 192.168.4.200 loose-router
    registrar 192.168.4.200
    user 10001

    gateway sip sipgw1
    no shutdown

    port ethernet 0 0
    medium auto
    encapsulation ip
    bind interface eth0 router
    no shutdown

    port ethernet 0 1
    medium auto
    encapsulation ip
    bind interface eth1 router
    no shutdown

    port bri 0 0
    clock auto
    encapsulation q921

    q921
    protocol pmp
    uni-side auto
    encapsulation q931

    q931
    protocol dss1
    uni-side user
    encapsulation cc-isdn
    bind interface isdnif0 switch

    port bri 0 0
    no shutdown

    port bri 0 1
    clock auto
    encapsulation q921

    q921
    protocol pmp
    uni-side auto
    encapsulation q931

    q931
    protocol dss1
    uni-side user
    encapsulation cc-isdn
    bind interface isdnif1 switch

    port bri 0 1
    no shutdown

    port bri 0 2
    clock auto
    encapsulation q921

    q921
    protocol pmp
    uni-side auto
    encapsulation q931

    q931
    protocol dss1
    uni-side net

    port bri 0 2
    shutdown


    I disable the firewall and antivirus on the pc with 3cx. I have only one net card whit only one ipaddress

    Can anyone help me?
    Thanks
     
  14. marcovalli

    Joined:
    Feb 26, 2007
    Messages:
    14
    Likes Received:
    0
    PATTON 4634 BUSY TONE

    I have a Patton 4634 configured as follows:
    I have 2 ISDN lines connected on BR0/0 and BR0/1 (line A and line 8)

    Line A works correctly both calling and receiving phone calls.

    Line B, instead, allows me to call and receive but, when line is engaged and I receive a phone call, the person who is calling doesn’t hear the engaged signal but the free one.

    If I exchange the two lines on the PATTON, line B (in this case connected to BR0/0) works correctly, instead line A (connected to BR 0/1) has the same defect (doesn’t give the engaged signal)
     
  15. rnoguera

    Joined:
    Oct 25, 2007
    Messages:
    89
    Likes Received:
    0
    Marcovalli:

    If you have 2 BRI, you have 4 voice lines (2 on each BRI) and the "busy" tone should be heard only when you already have 2 calls established in a line...
     
  16. deangelisg

    Joined:
    Nov 9, 2007
    Messages:
    4
    Likes Received:
    0
    yes...is my case
     
  17. deangelisg

    Joined:
    Nov 9, 2007
    Messages:
    4
    Likes Received:
    0
    I solve the problem, for work fine on the 3cx configuration need to create another gateway with same ip of the first but with another port, in this case 5062 that use the patton 4634 with default for second gateway
     

Share This Page