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

ipo server edition to cm 2

Status
Not open for further replies.

chrisag

Programmer
Sep 12, 2012
190
CY
Hi all
I have one server edition R10.1 and cm isR6.2
I have connected them with h323 and from cm i have incoming calls but from the ipo side no outgoing calls.
Do i need networking channels?
From what i write server edition has unlimited licenses, is that correct?
 
You have free channels to an expansion (included in the server edition license for that expansion) but you still need licenses when connecting to a separate system.

"Trying is the first step to failure..." - Homer
 
The way i read it, the only supported method to CM, is through Session Manager, then you would need the CM license.


 
That's if you wanna use it as a branch, but then it's administered through System Manager.

You can connect it to CM with either H.323 or SIP, but you'll need licenses for it.

"Trying is the first step to failure..." - Homer
 
That's what I thought
I will add the voice networking license and we will see
Thanks everyone
 
Hi again
I spoke with Avaya and they said that h323 license are not needed for server edition
Did anyone connect server edition with h323 with another system?
 
Exactly what did you ask them?

"Trying is the first step to failure..." - Homer
 
This is the answer I get

With Server Edition Networking Licenses are obsolete as they are bundled in as part of the SE license so you should be able to generate a H323 trunk to the CM and allocate channels which match the need for the link. Note VCM channels are needed which the SE already has but be aware of the VCM resource also.
 
Another thing is when I make an outbound call I get this error in monitor
Cause=34, No cct/chan available
 
Yes I did connect a IPO SE (9.0) to a cm.

And no, I do not have networking licenses.

And yes, this is working.

But, how did you setup the H323 trunk?
Did you setup routes to the trunk?
 
Thanks Okkie for the info.
The configuration on the ipo side is very simple maybe is a problem on the cm side.
Also you enable qsig and I have been told that qsig is not supported on server edition is that correct?
 
qsig is a PRI connection so would require an IP500V2 expansion server with a PRI card

I cant see any reason why it should not be supported bu you should check Avaya's documentation to be sure


Do things on the cheap & it will cost you dear
 
I have one server edition with links to a CM and they are just using basic H323 lines.

| ACSS SME |
 
Just an update, Avaya confirmed that ipo is not require license for h323 but qsig is not supported on server edition
 
I've configured QSIG PRI on server edition expansion systems several times, almost always when doing a phased migration from the old system that doesn't speak IP.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top