Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

BCM50 outgoing call over SIP Trunk to Avaya IPO

Status
Not open for further replies.

bbaits25

Technical User
Aug 7, 2013
135
US
I have a SIP Trunk setup today at from our Branch (BCM50) to our IPO (HQ). If I wanted to setup where the branch location wanted to dial out of our phone system, how can this be done? To dial out of out of HQ (Avaya) phone system is "9" then the number. I tried the following below,

Dialing Plan --> Routing
-Route:002
-External #:9
-Use Pool:BlocA
-DN Type:public

Destination Codes:
-Destination code: 8
-Normal Route:002
-Absorbed Length:All


I was musing the BCM Monitoring and noticed that the user gets 6 digits in (7 digits cause of the 9xxxxxx)then it hangs up. Somewhere i'm missing the allowed digits across the SIP trunk?
 
Have you explored the Resources/SIP Trunks heading and added account and Routing etc?


________________________________________
We take the time to try to answer your questions for free, please return the favor and take the time to answer back and include any resolution you found elsewhere, thanks.

=----(((((((((()----=

small-logo-sig.png

Toronto Canada
 
Also Dialing Plan Networking DN lenght.

________________________________________
We take the time to try to answer your questions for free, please return the favor and take the time to answer back and include any resolution you found elsewhere, thanks.

=----(((((((((()----=

small-logo-sig.png

Toronto Canada
 
In resource under "SIP Trunk" in the Public tab under routing table

- Name - External Call
- Destination Digits - 11
- Account - BCMtoIPO


Under Account

- These are all checked: Support 100rel, allow update, Null IP to hold, Enable SDP Options Query, Allow Refer, Support Replaces, Enable Connected Identitym Standard SIP Caps exchange

- ITSP Association method "From Head Domain Match"


For the Dialing Plan

- DN Prefix: 8
- DN Length: 11
 
I think the rule of thumb is Routing Table should match Destination Code.

My SIP is a true SIP Trunk from a carrier but this might help....
Dialing Plan:
Dest code is 95
Absorb is 0
Default Prefix DN lenght is 13

SIP Trunking:
Routing Table is 95
Public/Accounts/Advanced Outbound Called Characters to Absorb = 2


But I see you have Dest code of 8 to use Route 002 however Route 002 is told to dial 9 (External)?
That means you need to dial 8 to get out of the BCM which in turn dials 9 automatically for the IP Office Dest code?

I could be dead wrong for your setup but there is a guide for what you want which might say otherwise:



________________________________________
We take the time to try to answer your questions for free, please return the favor and take the time to answer back and include any resolution you found elsewhere, thanks.

=----(((((((((()----=

small-logo-sig.png

Toronto Canada
 
Yes curly your right, the 8 is to get out of the BCM and "9" is in front so it make an external call out of the Avaya IPO.
 
Unless i'm doing something wrong on this, but I see when the user dials "8" it puts a "9" in front of the number they want to call so.

-user dials 8
- in bcm monitor I see (9xxxxxx) then drops the call.


I've set this up between IPO's but just use #*9 for the shortcode to dial out of our HQ's phone system and it works. I don't know if the BCM is rejecting the amount of numbers it sends out or if the Avaya IPO is dropping it.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top