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 SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

BCM450r6 SIP Trunks to IPO500 R8.0 2

Status
Not open for further replies.

MetlePro

Programmer
Nov 30, 2006
78
0
0
SR
Hi,

I have a BCM450r6 setup with 4 SIP trunks to a IPO500r8.
Following the instructions from the "Configuring Interoperability between Avaya IP Office and Avaya Business Communication Manager" Avaya Documents, I was able to make calls from the IPO to all the sets on the BCM450.
But I get a fast busy trying to call from any phone (Analog/IP) from the BCM450 to the IPO.

the Call doesn't reach the IPO on the system status.
On the BCM monitor I see the Trunk being picked when I dial the destination code, followed by a fast busy after the string completes.

Any help would be appreciated.

MetlePro

Pro refers to my company, not my status
 
Hey phoneguy,

Thanks for the help, But I did use that document to configure the system.

After setting it up neither system would dial out to the other. But after adding (Using the examples from the document)the shortcode 33xxx Dial 33N"@192.168.x.x". The IPOffice calls started coming through to the BCM450.

The by Private rec. OLI's are all configured on the target lines. But the BCM does receive calls, it's outgoing that gives problems.

Kind Regards,


Pro refers to my company, not my status
 
Destination digits in the bcm programmed correctly ?

ddcommllc.com
Avaya/Toshiba/SyntelSolutions

ACIS

"Will work for stars
 
Did you create the incoming call route in the ip office

ddcommllc.com
Avaya/Toshiba/SyntelSolutions

ACIS

"Will work for stars
 
Yes and yes,

I used the exact same examples as in the document.
The BCM destination code 26 is added to the route using BlocA.
If I add a second dial tone, you hear the second dialtone after pressing 26 and bcm monitor show the sip trunks being used to dial out.

The IPO has the incoming route set to any voice coming in on the linegroup to go to the set with "." in the destination.

But in the status monitor for the IPO you do not see any incoming call.

Should I post the exact config?
regards,

Pro refers to my company, not my status
 
Yea if you could

ddcommllc.com
Avaya/Toshiba/SyntelSolutions

ACIS

"Will work for stars
 
On the IPOffice:
SIP line:
ITSP Domain: <bcm IP>
Send caller ID: Diversion header
Rest is default

Transport:
ITSP Proxy: <bcm IP>
Protocol: UDP

SIP Uri:
Channel 1 , no registration, in/out group ID 33, max calls 4 (4 SIP trunks)

VoIP:
Default settings with Voice suppression and Reinvite allowed

*SIP trunks are enabled on LAN1 tab

Shortcode:
33xxx; Dial 33N"@<BCM IP> , Linegroup 33

Incoming Call route:
Any Voice, Line group 33
Destination: "." , Fallback: none

Telephony:
our Companding Law is set to A-law (Euro)

BCM:
Business name is set

Routing:
010, Pool BlocA, Public (unknown)
Destination Code:
26, Route 010, Absorb 0

Public Network:
Since this is the only digital trunk on the system and there are no other DID's programmed the Public network lenght to 5, Dialing plan: Public (Unknown)

at the Public DN Network Lengths:
DN 26, lenght 5

IPTrunking General>IP trunk settings:
Last redirected, Send name display

BCM public accounts:
Name: BCMtoIPO
Description: -
Sip domain: <IP IPO>
Reg. req.: No

Advanced: Is set according to the doc. (Defaults)

SIP Routing Table:
Name: BcmtoIPO
Destination Digits: 26
ITSP account: BCMtoIPO

Media parameters:
All Codecs, VAD is enabled, in-band RB enabled, rest default

All sets have their designated Target line assigned with 33xxx Public numbers and xxx priv numbers = their DN number.

All sets have access to BlocA, and no conflicting Line restrictions.

Hope this helps.






Pro refers to my company, not my status
 
and you have the networking licenses in both systems I assume?

ddcommllc.com
Avaya/Toshiba/SyntelSolutions

ACIS

"Will work for stars
 
and im assuming the ipo extensions start with 26?

ddcommllc.com
Avaya/Toshiba/SyntelSolutions

ACIS

"Will work for stars
 
Just the SIP trunk licenses as suggested.
Yes the IPO have 26xxx and the BCM 33xxx

Pro refers to my company, not my status
 
well that's your problem

you need mcdn licesnses in the bcm
and scn licenses in the ipo

ddcommllc.com
Avaya/Toshiba/SyntelSolutions

ACIS

"Will work for stars
 
I must have missed it in the document..

Thanks for the help

Pro refers to my company, not my status
 
You do not need SCN or MCDN keycodes.
These are only required for Private Networking.
This configuration is setup using public trunk types.

I would suggest rechecking your BCM configuration.
Specifically the IP address of the IPO in your BCM Public Account.
Make sure the codecs are identical for each side.

Can you ping from the BCM to the IPO?

Based on the symptom you describe it seems the BCM can't get to the IPO.

-SD-
 
Support dude

Everyone I've setup had the license

Have you been able to set them up without it?



ddcommllc.com
Avaya/Toshiba/SyntelSolutions

ACIS

"Will work for stars
 
Absolutely.
I have it running in my lab.
MCDN = Meridian Customer Defined Network; used between Nortel systems on a private voice network (can be SIP or H323).
SCN = Small Community Network; used between IP Office systems on a private voice network using H323 trunks.

The integration document is specific to connecting IP Office and BCM using SIP trunks.
I know that the doc shows some setup info for SCN and MCDN, but if you look closely, it's not to each other.
Not really sure why SCN is in there ... maybe just to show the setup.
The BCM is showing MCDN setup because the network diagram at the beginning of the documentation shows two BCM's (connected using MCDN) and one IP Office (connected to one BCM using SIP).
Since BCM only uses MCDN on trunks set to "Private", and IP Office can only use SCN on H323 trunks, neither option is required for a public SIP trunk connection between the IPO and BCM.

HTH!

-SD-
 
Hey There Supportdude,

I've been busy on another project, so I haven't had the time to sit down and go through the config thoroughly. But I did rechecked the IP addresses and everything is where it should be. All the codecs are the same, also the VAD / noise cancelation option on both are identical.
The Ping from Bcm to IPO passes with 0% losses.
As stated above the IPO is able to call the BCM, but not Vice versa.
Ports used are also checked and allowed.

I Will post a report tomorrow after I've sat down and went through the config again.
If you can think of anything I might've over looked. I'm all ears.

Kind Regards,

Pro refers to my company, not my status
 
Hi MetlePro,
The only other thing that comes to mind is what you may have configured on the User>SIP tab.
Each field should match the 5 digit extension you are trying to call.

I would suggest using IPO Monitor instead of SSA. The setup info is coming on a D channel, so you might not see it in SSA.
You might want to use the capture utility in BCM to grab a sniff of a couple of test calls.
The BCM FEPS log will also show information on why the call is not completing.

-SD-
 
Hi SupportDude,

Thanks for the suggestions. It was the USER>SIP tab I overlooked on the IPOffice config.
After changing that to the numbers being sent by the BCM it worked perfectly!

I went through the documentation again and saw it mentioned when they discuss the SIPLine> SIP URI tab. But it made sense since you have to define it on the BCM targetlines.

Anyways, thanks guys for Helping me through my first time setting up SIP lines.

Pro refers to my company, not my status
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top