S8300/SES-SIP (Co-Resident) HELP

[kokolatas]

Hi, i would like some help on the configuration procedures of the S8300/SES-SIP (Co-Resident).
From CM perspective i have configured the trunk and signaling group.
From SES web maintenance i have done all the necessary SIP Programming as mentioned on the 'Administering SIP Enablement Services on the Avaya S8300 Server' document.

i have install the license .xml file using the eth0 mac address.

My problem is that the SIP ROLE as shown in web maintenance is unknown.

what should i do next?

 

[kokolatas]

any ideas here?

 

[Avayell]

I am also interested about that unknown thing. Any help appreciated.

 

[kank]

get in to queue man!!

 

[Mitch672]

Try this:
Administering SIP Enablement Services on the Avaya S8300 Server

http://support.avaya.com/japple/css...eID=348581&temp.bucketID=159898&PAGE=Document

Click on the very firswt link on the SES webpage, and setup the SIP domain, and follow each link, until it is all setup. You will also have to use the WebLM, and have access to RFA, and have an RFA Transaction # for "SIP" to be able to license it.

Mitch


AVAYA Certified Specialist

 

[kokolatas]

hi.

I have done all those things.

i install the .xml license via the weblm but on CM's Maintenance web bage, on the process status there the 'partial up' message for sip. the SIP Role is also 'unknown'. this is the point i have stack.
i have read a lot of documents,including the one you advise but there is no guileless about that issue.

i may do the installation steps over again from the beginning but i really think there is something missing.

 

[JayNEC]

This might help:

SIP Enablement Services: SipServer process stays down on Co-Resident SES-CM


Document Id: KB01045000
Last Modified Date: 11-05-2008
Support Goal(s): SIP Enablement Services
Access Level: External Entitled


Version-Release

SES-5.0.0.0-825.30

CM combined home-edge
Details


The statapp command shows that the SipServer is OFF: SipServer 0/34 OFF

Description (Problem Clarification)


It is not possible to start the SipServer. The following alarm is logged:
avCCSProxyStartFailed:network-man init err=8012errno=98Address already in use

Cause


Wrong trunk/signaling group administration. There is one trunk group which connects theSIP Enablement Services(SES) and the Communication Manager (CM) components of the Co-Resident server and there are multiple other Session Initiation Protocol (SIP) trunks going to destinations other then the SES. On these other SIP trunks, the 'Near-end Listen Port' is set to 5060 or 5061.

Problem Fix/Workaround/Solution

You need to remove all the trunk/signaling groups which have 'Near-end Listen Port' set to 5060 or 5061 except for the one connecting the SES and the CM together.
Resolution Plan

Remove all the trunk/signaling groups which have'Near-end Listen Port' set to 5060 or 5061 except for the one connecting the SES and the CM together.

Avaya -- Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy

 

[Mitch672]

did you go in, and configure the SIP server? sounds like you didn't, as the SIP roles are setup when you configure it... the trunks don't matter to get the SIP roles setup, I have done it many many times now.

Mitch


AVAYA Certified Specialist

 

[kank]

I have also problem configuring ses on 8300. I follow up the document but there is no WebLM step on the document. Only thing is you choose the Sip license Host and I give the IP adress of the 8300. Is this enough or should I load a license for it?