Jump to content

ocs

Members
 View Profile  See their activity

  • Posts

    3

  • Joined

  • Last visited

 Content Type 

Posts posted by ocs

  2. Matching incoming DID FXO to Trunk

    in Embedded

    Posted

    Well, essentially you can set the DID numbers that the FXO should report for the respective line. Then on the PBX you can use the inbound trunk rules to locate the hunt group. Probably it should be sufficient to assign the right alias name to the hunt group. Another obstable could be to choose the right 10- or 11-digit format.

     

    Thanks for replying. I have entered the DID numbers in the FXO ports and in the trunks I have put matching numbers into the trunks. Not sure how to put aliases into the hunt group - there is no field for this in my version and I could not find any documentation showing how these work.

     

    This is what I have in summary:

     

    PTSN Gateway.

     

    DID FXO Port 1: 55552935

    DID FXO Port 2: 55552937

    DID FXO Port 3: 55552941

     

     

    Trunk (1 of 3 setup)

    Name: Work 2935

    Type: SIP Gateway

    Direction: Inbound and outbound

     

    Account: 55552935@localhost

    Domain: localhost

    Username: 55552935

    outbound proxy: 127.0.0.1:5062

    Co Lines:

    .

    .

    All defaults here

    .

    .

    Global: Yes

    Remote Party/Privacy Indication: No Indication

    Rewrite global numbers: Check Domain Country Code

    Is Secure: Yes

    .

    .

    Send Call To Extension: 80 <<--- This is my hunt extension

     

    We are in Australia and I have country code set to 61 and area set to 3 (I have not put country code or area code in any of the settings for matching, just the 8 digit local numbers) and Change names in To/From-headers set to No in Domain Settings.

     

     

    Call Log looks like this:

     

    Call History

    Start From To Duration

    2009/03/09 18:45:12 0418555555 0355552935

    2009/03/09 18:45:51 0418555555 0355552935

     

     

    This is what is in the log file when receiving a call from our 2935 number: (it matches to the 2937 trunk. Infact any inbound call seems to match to the 2937 trunk)

     

    [5] 2009/03/09 20:41:42: Trunk 1 (Work 2935) has outbound proxy udp:127.0.0.1:5062

    [5] 2009/03/09 20:42:03: Trunk 13 (Home 2941) has outbound proxy udp:127.0.0.1:5062

    [5] 2009/03/09 20:42:23: Trunk 14 (Work 2937) has outbound proxy udp:127.0.0.1:5062

    [3] 2009/03/09 20:42:38: PSTN: Channel 2 going to RING

    [5] 2009/03/09 20:42:40: PSTN: eVAPI_CALLER_ID_DETECTED_EVENT

    [5] 2009/03/09 20:42:40: PSTN: Received on 2: DATE: 0309, TIME: 2142

    [5] 2009/03/09 20:42:40: PSTN: Received on 2: Caller-ID 0418555555

    [5] 2009/03/09 20:42:40: Identify trunk (IP address/port and domain match) 14

    [5] 2009/03/09 20:42:40: PSTN: Response code: 100

    [5] 2009/03/09 20:42:40: Trunk Work 2937 (global) sends call to account 80 in domain localhost

     

     

    I am pretty sure it is something very simple, as you say aliases or number format.

     

    Thanks, Richard

  3. Matching incoming DID FXO to Trunk

    in Embedded

    Posted

    Hi, just new to setting up pbxnsip on cs410 and all seems ok so far except we have 3 DID FXO lines that I can't get to be recognised as different inbound calls in the trunks.

     

    We want each FXO line to a different Hunt group extension so we can set different ring tones for each line etc.

     

    No matter what line we call in with it seems to pick the wrong trunk and therefore the wrong hunt extension.

     

    I have read the wiki on assigning DID numbers for FXO but it doesn't seem to match the version we are using which is V3.

     

    Thanks. I hope I have described our issue correctly.

     

    Richard

×
×
  • Create New...