Help with new SaskTel Trunk

FreePBX Providers
1

Running FPBX 17, Asterisk 21 on a new box, and I am setting up a SIP trunk from our local telco - SaskTel. My experience is limited on trunks from provider, but I have setup iax2 and pjsip trunks between pbx’s, etc. so the concept isn’t lost on me. I’m getting limited support from the provider but they have supplied these settings:

  • SIP Transport Type - UDP

  • SIP Port Used - 5060

  • RTP Ports

    • UDP 49000-49200 - always used for DSL network access

  • DID Number Range – xxx-xxx-xxxx

  • Inbound Digits - 10

  • Voice Codecs Available - G.711u

  • Number of Trunks (channels) - 1

  • DTMP Type - RFC-2833:RTP Payload for DTMF digits

  • Customer PBX IP
    IP Address: xxx.xxx.xxx.xxx
    IP Gateway: xxx.xxx.xxx.xxx
    Subnet Mask: xxx.xxx.xxx.xxx
    SBC Access Side IP
    IP Address: xxx.xxx.xxx.xxx
    IP Gateway: xxx.xxx.xxx.xxx
    Subnet Mask: xxx.xxx.xxx.xxx
    SBC Voice Core IP
    IP Address: xxx.xxx.xxx.xxx
    IP Gateway: xxx.xxx.xxx.xxx
    Subnet Mask: xxx.xxx.xxx.xxx

I’ve tried a few combinations setting up a pjsip trunk and as a result the trunk is listed as unavailable or nonqual. Provider said to use ‘SBC Access Side IP’ as the SIP server in FPBX. I tried that and set authentication several ways with no joy.

2

Is “Customer PBX IP” private or public? Is “SBC Access Side IP” in the same subnet? Does this path provide internet access? Do you have a separate NIC for this path?

Can you ping that IP from the PBX?

Registration and Authentication should both be set to None.

3

I’d have to dig into the customer PBX IP, currently it comes from the telco router, anyone’s guess if its public or private. The IP’s are not on the same subnet, and I don’t have any internet access and i cannot ping their IP… I even put setup a Windows box to see if i could ping that IP with no luck. There is a separate NIC in the box for this trunk. Thanks, I have tried the authentication for none.

4

A simple web search and details of the initial digits should remove the need to guess. Also a whois search that returns IANA will generally indicate a private (or shared) - which can probably be considered private in the current context) address.

It’s basically something anyone managing a network beyond that of a casual home user should know, for their network.

5

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.