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.

Outgoing MSN Mapping with Patton 4554

Discussion in '3CX Phone System - General' started by silvano, Oct 26, 2008.

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

    Joined:
    Sep 27, 2008
    Messages:
    5
    Likes Received:
    0
    Hi. I've been desperately looking for a way to configure Outgoing MSN Mapping on a Patton SmartNode 4554 connected to my 3CX V6.

    My problem: I have 2 ISDN BRIs connected to the Patton. One should make and receive calls for an office, the other one should make and receive calls for another office. Both BRIs have a couple MSNs. I want calls made from a given office to be routed to a specific BRI and use a specific MSN, and not be routed to the first available BRI and use the default (main) MSN.

    I found this post, which actually discusses *Incoming* MSN Mapping, and in a code snippet I found an inspiration.
    http://www.3cx.com/forums/incoming-msn-mapping-2066.html#p8240

    I used the config file made with 3CX to configure the Patton 4554. Then I added a routing-table that should pick calls made by extension 64 and route them to the given interface, which is IF_ISDN_1, applying a mapping-table to substitute the internal extension number (64) with the wanted MSN. The problem is… it doesn't work at all! :roll:

    Please help! Am I missing something? (…of course I am) This Patton-thing is powerful but not very user friendly :shock:

    Here's my routing configuration. I'm very new to the Patton so I'm not sure it's enough.

    Code:
      routing-table called-e164 RT_ISDN_TO_SIP_0
        route default dest-interface IF_SIP_0 MP_REM_CLIR
    
      routing-table called-e164 RT_ISDN_TO_SIP_1
        route default dest-interface IF_SIP_1 MP_REM_CLIR
    
      routing-table calling-e164 RT_SIP_TO_ISDN
        route 64 dest-interface IF_ISDN_1 MAP_SIP_TO_MSN
    
      mapping-table calling-pi to calling-e164 MP_REM_CLIR
        map restricted to ""
    
      mapping-table calling-e164 to calling-e164 MAP_SIP_TO_MSN
        map 64 to 51227677
        map 63 to 512915856
    I also attach my complete config file for the Patton 4554

    Code:
    context cs switch
    
      routing-table called-e164 RT_ISDN_TO_SIP_0
        route default dest-interface IF_SIP_0 MP_REM_CLIR
    
      routing-table called-e164 RT_ISDN_TO_SIP_1
        route default dest-interface IF_SIP_1 MP_REM_CLIR
    
      routing-table calling-e164 RT_SIP_TO_ISDN
        route 64 dest-interface IF_ISDN_1 MAP_SIP_TO_MSN
    
      mapping-table calling-pi to calling-e164 MP_REM_CLIR
        map restricted to ""
    
      mapping-table calling-e164 to calling-e164 MAP_SIP_TO_MSN
        map 64 to 51227677
        map 63 to 512915856
    
      interface isdn IF_ISDN_0
        route call dest-table RT_ISDN_TO_SIP_0
    
      interface isdn IF_ISDN_1
        route call dest-table RT_ISDN_TO_SIP_1
    
      interface sip IF_SIP_0
        bind gateway GW_SIP_0
        service default
        route call dest-interface IF_ISDN_0
        early-connect
        early-disconnect
        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
    
      interface sip IF_SIP_1
        bind gateway GW_SIP_1
        service default
        route call dest-interface IF_ISDN_1
        early-connect
        early-disconnect
        remote-party-id called-party
        address-translation outgoing-call request-uri user-part fix 10002 host-part to-header target-param none
        address-translation incoming-call called-e164 request-uri
    
    context cs switch
      no shutdown
    
    gateway sip GW_SIP_0
      bind interface IF_IP_LAN router
    
      service default
        domain 192.168.1.2
        defaultserver manual 192.168.1.2 loose-router
        registration-lifetime 300
        registration manual 192.168.1.2
        user 10001 authenticate password dZ8edXkjFnM= encrypted default register
    
    gateway sip GW_SIP_0
      no shutdown
    
    gateway sip GW_SIP_1
      call-signaling-port 5062
      bind interface IF_IP_LAN router
    
      service default
        domain 192.168.1.2
        defaultserver manual 192.168.1.2 loose-router
        registration-lifetime 300
        registration manual 192.168.1.2
        user 10002 authenticate password iAaKwKfxX4Q= encrypted default register
    
    gateway sip GW_SIP_1
      no shutdown
    
    port ethernet 0 0
      encapsulation ip
      bind interface IF_IP_LAN router
      no shutdown
    
    port bri 0 0
      clock auto
      encapsulation q921
    
      q921
        uni-side auto
        encapsulation q931
    
        q931
          protocol dss1
          uni-side user
          bchan-number-order ascending
          encapsulation cc-isdn
          bind interface IF_ISDN_0 switch
    
    port bri 0 0
      no shutdown
    
    port bri 0 1
      clock auto
      encapsulation q921
    
      q921
        uni-side auto
        encapsulation q931
    
        q931
          protocol dss1
          uni-side user
          bchan-number-order ascending
          encapsulation cc-isdn
          bind interface IF_ISDN_1 switch
    
    port bri 0 1
      no shutdown
     
  2. silvano

    Joined:
    Sep 27, 2008
    Messages:
    5
    Likes Received:
    0
    Anyone?

    At least do you know whether it is possible to "chose" which ISDN channel to use from the 3CX interface?
     
  3. mschmidt

    Joined:
    Oct 25, 2007
    Messages:
    8
    Likes Received:
    0
    I have exactly the same situation now, has anyone found yet a working solution? It would be very strange if it couldn't be done, because it's one of the most basic ISDN features.

    Thank you very much in advance!
     
  4. silvano

    Joined:
    Sep 27, 2008
    Messages:
    5
    Likes Received:
    0
    It seems very basic to me, too… :shock:
    Did you find any information?
     
  5. mschmidt

    Joined:
    Oct 25, 2007
    Messages:
    8
    Likes Received:
    0
    No, sorry, no information yet. I haven't had much time for research, so as a quick fix I configured anonymous calls, but that's of course not satisfying.
     
Thread Status:
Not open for further replies.