Incoming MSN Mapping

[Dida28]

Hi,

i use the 3cx with the Call Router from Patton 4552.
The 3cx is connected with 2 PSTN Lines to ISDN.
ISDN > Patton > 3cx

All works fine now.

But i don't now how can i map/route incoming calls from specific MSNs to specific extensions. I can only route a specific PSTN-line to a specific Extension in the 3xc-configuration interface.

Is it possible to route MSNs to extensions?

Thank you...
Dida

 

[marcoluce]

Hi Dida,

Try using "Add DID" on 3CX. You can then specify what incoming number from the PSTN is sent to what extension. The Patton will take care of "hiding" the fact that the line is a MSN line and not DID. Check the 3CX server status log to see in what format (how many digits, including prefix etc) the MSN number arrives at 3CX, then enter the number as DID on 3CX accordingly.

-Marco

 

[archie]

What is MSN line, btw :?:

 

[telis]

MSN stands for Multi Subscriber Numbering

OK, first a bit of background.

ISDN lines come in either bundles of 2 lines (called ISDN2e) or variable size bundles of 8 to 30 lines (called ISDN30).

ISDN2e lines can come in two variants, Standard Access and System Access. The Standard variant is intended for connecting devices, like an ISDN modem, and/or a G5 fax machine (G5 faxes use ISDN). ISDN2e System lines are designed for connecting to a PBX.

MSN is an ISDN feature a bit similar to another ISDN feature, DDI. MSN only works on ISDN2 when it is Standard mode and allows one 2 line bundle to have up to 9 extra phone numbers. This allows you to have 10 devices attached each with their own phone number. So you could have say 10 G5 fax machines sharing two lines, each with it's own incoming phone number and no need for a PBX. (you only get two sockets on the BT box, you'll need an inexpensive adapter to expand this number to 10).

DDI performs the same role but you can have a pretty much unlimited number of phone numbers and these can span multiple ISDN bundles, so you could have 20 phones numbers over 3 ISDN2e bundles, or even 200 phone numbers over 6 ISDN30 bundles. The diadvantage is that in order for this to work you need a PBX (or equivalent like a ISDN/SIP gateway) to route the calls.

Hope this helps.

 

[Dida28]

Thanks for your replies.

now i'm sure, that i have a bundle of 2 lines (called ISDN2e).

MSN is an ISDN feature a bit similar to another ISDN feature, DDI. MSN only works on ISDN2 when it is Standard mode and allows one 2 line bundle to have up to 9 extra phone numbers. This allows you to have 10 devices attached each with their own phone number. So you could have say 10 G5 fax machines sharing two lines, each with it's own incoming phone number and no need for a PBX. (you only get two sockets on the BT box, you'll need an inexpensive adapter to expand this number to 10).

We have 1 "Main-Number" an 9 extra phonenumbers on this port.
I tryed to map with the Patton 4552 the incoming calls from specific MSN to a specific with following function (MSN 916313 -> ext. 101):

mapping-table called-e164 to called-e164 MAP_MSN_2_SIP
    map 916313 to 101

The other way arround it works fine. Outgoing calls will correctly assigned to the extensions with this function:

mapping-table calling-e164 to calling-e164 MAP_SIP_2_MSN
map 101 to 916313
    map 102 to 916313

In the log of the 3cx i see independent from different configuration
(and i tryed a lot of things) always the ext. of the patton PSTN line (10001)

19:45:39.415 CallConf::onIncoming [CM103002] Call(41): Incoming call from 0891576495 (Ln:10001@Patton ISDN) to sip:[email protected]

here is my configuration file of the Patton SN4552

context cs switch
  national-prefix 0
  international-prefix 00

  routing-table called-e164 RT_SPEED_DIAL
    route T dest-table RT_NR_BLOCKING MT_SPEED_DIAL

  routing-table called-e164 RT_NR_BLOCKING
    route default dest-table RT_CALL_ROUTING MT_SET_CNPN

  routing-table called-e164 RT_CALL_ROUTING
    route default dest-interface ISDN0 MAP_SIP_2_MSN

  routing-table called-e164 RT_INCOMING
    route default dest-interface SIPIF0 MAP_MSN_2_SIP

  mapping-table called-e164 to called-e164 MT_SPEED_DIAL

  mapping-table calling-e164 to calling-e164 MT_SET_CNPN

  mapping-table called-e164 to called-e164 MT_NR_TRANSLATION

  mapping-table calling-e164 to calling-e164 MAP_SIP_2_MSN
    map 101 to 916313
    map 102 to 916313

  mapping-table called-e164 to called-e164 MAP_MSN_2_SIP
    map 916313 to 101

  interface isdn ISDN0
    route call dest-table RT_INCOMING

  interface isdn ISDN1
    route call dest-interface SIPIF1

  interface isdn IF_S0_01

  interface sip SIPIF0
    bind gateway SIPGW0
    service default
    route call dest-table RT_CALL_ROUTING
    remote-party-id called-party
    address-translation outgoing-call to-header user-part fix 10001 host-part interface
    address-translation incoming-call called-e164 remote-party-id-header

  interface sip SIPIF1
    bind gateway SIPGW1
    service default
    route call dest-interface ISDN1
    remote-party-id called-party
    address-translation outgoing-call to-header user-part fix 10002 host-part interface
    address-translation incoming-call called-e164 request-uri

  interface sip IF_SIP_SERVICE
    service default

  service hunt-group SER_HG_PSTN_FALLBACK
    timeout 6
    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 no-route-to-destination
    route call 1 dest-interface IF_S0_00
    route call 2 dest-interface IF_SIP_SERVICE

context cs switch
  no shutdown

gateway sip SIPGW0
  bind interface IF_IP_LAN router

  service default
    domain 192.168.178.41
    authentication 10001 password dZ8edXkjFnM= encrypted default
    default-server 192.168.178.41 loose-router
    registration-lifetime 120
    registrar 192.168.178.41
    user 10001

gateway sip SIPGW0
  no shutdown

gateway sip SIPGW1
  call-signaling-port 5062
  bind interface IF_IP_LAN router

  service default
    domain 192.168.178.41
    authentication 10002 password iAaKwKfxX4Q= encrypted default
    default-server 192.168.178.41 loose-router
    registration-lifetime 120
    registrar 192.168.178.41
    user 10002

gateway sip SIPGW1
  no shutdown

 

[marcoluce]

Hi Dida,

Your configuration fixes the user part of the TO-Header to be 10001 (the line ID):

address-translation outgoing-call to-header user-part fix 10001 host-part interface

Please change this to

address-translation outgoing-call request-uri user-part fix 10001 host-part to-header target-param none

Make sure the old address-translation gets removed (edit the file off-line and download the config, or first remove the old address-translation). This fixes the Request URI to the line ID (3CX will still recognize the line based on this), and the TO-Header remains to be the "101" that you configured on the SmartNode.

Still, I believe that you could also directly configure the MSN number (916313) as DID on the 3CX.

Hope this helps
-Marco

 

[Dida28]

Hi Marco!

This was the solution of my problem. Now it works fine, thank you very much! :lol: :lol:

Nice greeting from Germany near Munich,
Dida