The Adtran community holiday season is starting next week! The holiday period will span from December 21, 2024 to January 6, 2025. During this time, responses to feedback form submissions may be delayed. If you are encountering product issues, you can reach out to Adtran support at any time.
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
rcraig114
New Contributor

Inbound from SIP to PRI issue

Jump to solution

I am doing some testing with migrating from Verizon to our internal SIP trunks. Its SIP to the Adtran from CUCM, then out to PBX via PRI. I am having a hard time getting the call to actually go out the PRI and not back out verizon. Any issues with the below config?

** This is the Verizon trunk that is working now**

voice grouped-trunk "SIP TRUNK GROUP"

  trunk T25

  accept $ cost 0

  deny list FAX_USERS

  deny list NETWORK_TRUNKS

  permit list ALL_USERS

  !deny all other trunks

  !deny all other ani

!

!

** PBX PRI **

voice grouped-trunk PRI

  trunk T02

  trunk T03

  accept $ cost 0

  permit list NETWORK_TRUNKS

  !deny all other trunks

  !deny all other ani

!     

!

** SIP Trunk from CUCM to Adtran. Inbound call from CUCM should go out PRI to PBX.**   

voice grouped-trunk CUCM-PRI

  trunk T26

  trunk T27

  accept $ cost 0

  permit list PRI

  deny list FAX_USERS

  deny list NETWORK_TRUNKS

  !deny all other trunks

  !deny all other ani

Tags (1)
0 Kudos
1 Solution

Accepted Solutions
Anonymous
Not applicable

Re: Inbound from SIP to PRI issue

Jump to solution

Looks good. With your config like you said, all calls will go out Verizon sip trunk unless that trunk is busy or down, then it will failover to the CUCM trunks.

You should test an outbound call to confirm your setup though.

-Mark

View solution in original post

0 Kudos
9 Replies
Anonymous
Not applicable

Re: Inbound from SIP to PRI issue

Jump to solution

Really need to see your whole config. Can you attach it and debug as txt files. Make sure you remove any passwords/logins

Can you also attach output of debug of following commands:

Debug voice verbose

Debug sip stack messages

Debug isdn l2-formatted

Debug sip cldu

-Mark

Re: Inbound from SIP to PRI issue

Jump to solution

No problem. Thanks for responding so quickly. Please see attached. Let me know what I missed. I have been able to do this with SIP to POTs on Adtran, but going through the PRI seems to be different (not sure why).

Robert

Re: Inbound from SIP to PRI issue

Jump to solution

OK, files attached.

Robert

Anonymous
Not applicable

Re: Inbound from SIP to PRI issue

Jump to solution

So looks like the call is coming in on T26 from the CUCM

Rx: UDP src=10.100.38.12:5060 dst=10.193.5.114:5060

Your PRI grouped-trunk is configured to only permit calls from NETWORK_TRUNKS which is just T25 and T30. So the call is never going out the PRI.

You can see in your dial plan debug here that the call is going out the SIP TRUNK GROUP because SABR is matching on the “permit list ALL_USERS” entry.

07:05:54.737 SB.CALL 29248 Idle Called the call routine with 9517358115

07:05:54 SB.TGMgr Trunk lists configured in TrunkGroup SIP TRUNK GROUP FAX deny SABR Routing

07:05:54 SB.TGMgr Testing Trunk Access List FAX_USERS

07:05:54 SB.TGMgr Testing Trunk Access List NETWORK_TRUNKS

07:05:54 SB.TGMgr Testing Trunk Access List ALL_USERS

07:05:54 SB.TGMgr Trunk Access List ALL_USERS is Permitted

07:05:54 SB.TGMgr Trunk lists configured in TrunkGroup SIP TRUNK GROUP permit SABR Routing

07:05:54 SB.TGMgr For dialed number 9517358115, against template $, on TrunkGroup SIP TRUNK GROUP, the score is 500

07:05:54 SB.TGMgr Testing Trunk Access List NETWORK_TRUNKS

07:05:54 SB.TGMgr Trunk lists configured in TrunkGroup PRI deny SABR Routing

07:05:54 SB.TGMgr Testing Trunk Access List FAX_USERS

07:05:54 SB.TGMgr Testing Trunk Access List NETWORK_TRUNKS

07:05:54 SB.TGMgr Trunk lists configured in TrunkGroup CUCM-PRI deny SABR Routing

Your SABR configuration is all messed up. On your grouped-trunk CUCM-PRI, you are “permit list PRI” but you don’t have a PRI list. A non-create SABR list is a deny list which you see with this debug:

07:05:54 SB.TGMgr Trunk lists configured in TrunkGroup CUCM-PRI deny SABR Routing

What exactly are you trying to accomplish with your SABR configuring?

If you want calls to go out the PRI from the CUCM trunks then you need to create a SABR list like

Voice trunk-list CUCM

Trunk T26

Trunk T27

Then apply it via:

Voice grouped-trunk PRI

Permit list CUCM

If you tell me what you are trying to accomplish with your SABR config, I can help you fix your configuration.

Here is a config guide for SABR: https://supportforums.adtran.com/docs/DOC-1862

-Mark

Re: Inbound from SIP to PRI issue

Jump to solution

Ahhh, I knew I missed something. Ok, I will do that. One thing I want to confirm though. If I allow the CUCM list on the PRI group, will calls coming from the PRI go out CUCM (or even have the chance to go out) or only go through Verizon?

Robert

jayh
Honored Contributor
Honored Contributor

Re: Inbound from SIP to PRI issue

Jump to solution

An alternative way of doing this, if you don't need SABR which tends to complicate things, is to configure the voice grouped-trunk PRI to just have the dial patterns of the DID groups on the PBX. Rather than:

voice grouped-trunk CUCM-PRI

  trunk T26

  trunk T27

  accept $ cost 0

  permit list PRI

  deny list FAX_USERS

  deny list NETWORK_TRUNKS

  !deny all other trunks

  !deny all other ani

Set it up as:

voice grouped-trunk CUCM-PRI

  trunk T26

  trunk T27

  accept 311-555-23XX cost 0

(Assuming that you have DIDs of 311-555-2300 throught 311-555-2399.)

The most specific match will take the route. SABR is for routing based on the source of the call in addition to the destination. This is usually not needed unless you have a need to route calls differently based on the source trunk or ANI. In most cases you will only need to route based on the destination.

Anonymous
Not applicable

Re: Inbound from SIP to PRI issue

Jump to solution

Robert,

You will need to create the following SABR list to allow outbound calls from the PRI to CUCM. You will also need to modify the cost on the PRI/SIP trunks.

Here is the commands to create PRI group:

Voice trunk-list PRI

Trunk T02

Trunk T03

Then whichever trunk you want to be the backup, go into that group-trunk and add these commands:

Accept $ cost 100

For example if you want the Verizon sip trunk to be used as backup and all calls to go to the CUCM then add the following:

Voice group-trunk “SIP TRUNK GROUP”

Accept $ cost 100

Let me know if you have any other questions or to review your config when done.

-Mark

Re: Inbound from SIP to PRI issue

Jump to solution

OK, what I have now is below. Theoretically, all calls from Verizon should go to Verizon. All calls from PRI should hit Verizon first, then CUCM as a backup. Correct?

voice trunk-list CUCM

  trunk T26

  trunk T27

!

voice trunk-list NETWORK_TRUNKS

  trunk T25

  trunk T30

!

voice trunk-list PRI

  trunk T02

  trunk T03

!

voice trunk T02 type isdn

  description "PRI CONNECTION 1"

  resource-selection circular descending

  busy-out monitor track WANTRACK

  caller-id-override number-inbound 9517358115

  connect isdn-group 1

  no early-cut-through

  match dnis "195127250XX" substitute "50XX"

  match dnis "19517358115" substitute "8115"

  modem-passthrough

  rtp delay-mode adaptive

  codec-list 729-711

!

voice trunk T03 type isdn

  description "PRI CONNECTION 2"

  resource-selection circular descending

  busy-out monitor track WANTRACK

  caller-id-override number-inbound 9517358115

  connect isdn-group 2

  no early-cut-through

  match dnis "195127250XX" substitute "50XX"

  match dnis "19517358115" substitute "8115"

  modem-passthrough

  rtp delay-mode adaptive

  codec-list 729-711

!

voice trunk T25 type sip

  description "SIP Trunk"

  sip-server primary XXXXXXX.globalipcom.com

  sip-server rollover service-unavailable-or-timeout

  outbound-proxy primary pcn10018.XXXXXXX.globalipcom.com

  domain "dartcontainer1.globalipcom.com"

  trust-domain

  codec-list 729-711 both

!      

voice trunk T26 type sip

  description "CUCM"

  sip-server primary 10.100.38.12

  codec-list 729-711 both

  transfer-mode network

!

voice trunk T27 type sip

  description "CUCM"

  sip-server primary 10.201.38.12

  codec-list 729-711 both

  transfer-mode network

!

!

!

voice grouped-trunk "SIP TRUNK GROUP"

  trunk T25

  accept $ cost 0

  deny list FAX_USERS

  deny list NETWORK_TRUNKS

  permit list ALL_USERS

  !deny all other trunks

  !deny all other ani

!

!

voice grouped-trunk PRI

  trunk T02

  trunk T03

  accept $ cost 0

  permit list NETWORK_TRUNKS

  permit list CUCM

  !deny all other trunks

  !deny all other ani

!

!

voice grouped-trunk CUCM-PRI

  trunk T26

  trunk T27

  accept $ cost 100

  permit list PRI

  deny list FAX_USERS

  deny list NETWORK_TRUNKS

  !deny all other trunks

  !deny all other ani

!

Anonymous
Not applicable

Re: Inbound from SIP to PRI issue

Jump to solution

Looks good. With your config like you said, all calls will go out Verizon sip trunk unless that trunk is busy or down, then it will failover to the CUCM trunks.

You should test an outbound call to confirm your setup though.

-Mark

0 Kudos