Avaya Support Forums  

Go Back   Avaya Support Forums > Avaya Aura & Unified Communications

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 02-24-2017, 10:33 AM
thargi thargi is offline
Member
 
Join Date: Feb 2017
Posts: 8
thargi has 10 reputation points
Default SIP Phone Login and Registration

CM 6.0.1
ASM and SMGR 6.3

I am trying to set up an Avaya 9641g SIP phone in my environment. I have set the firmware on the phone to be SIP. I have set up the user profile and the communication profile in SMGR, and verified that the extension (8700) shows up in CM.
When I boot the phone, it goes through its bootup process, receives an IP from DHCP, and gets to the Enter username field. I dial 8700 and press enter. I get the Enter password field. I dial 8700 (the security code in CM endpoint profile) and press enter. Then I get "Request not allowed (403)" and a field with a blinking cursor. What is that all about?
Is the username field not wanting the extension and the password field not wanting the security code? If not, what is it looking for? Avaya's documentation on this is not good at all.
How do I get this SIP phone logged in and registered?

Thanks
Reply With Quote
  #2  
Old 02-24-2017, 11:36 AM
mlombardi1's Avatar
mlombardi1 mlombardi1 is offline
Legend
 
Join Date: Sep 2010
Location: New York
Posts: 407
mlombardi1 has 25 to 49 reputation pointsmlombardi1 has 25 to 49 reputation pointsmlombardi1 has 25 to 49 reputation points
Default

The "security code" field on the station object doesn't apply to SIP endpoints. The SIP equivalent is the Communication Profile Password in the SMGR user profile. Try setting that to 8700
Reply With Quote
  #3  
Old 02-24-2017, 01:59 PM
gwebster gwebster is offline
Guru
.
 
Join Date: Mar 2010
Location: Ottawa
Posts: 141
gwebster has 25 to 49 reputation pointsgwebster has 25 to 49 reputation points
Default

For anybody attempting to add SIP endpoints to their Avaya Aura system, have a look at https://downloads.avaya.com/css/P8/documents/100154012 and https://downloads.avaya.com/css/P8/documents/100182873.
Reply With Quote
  #4  
Old 02-24-2017, 02:08 PM
thargi thargi is offline
Member
 
Join Date: Feb 2017
Posts: 8
thargi has 10 reputation points
Default

Thanks for the information. After using the right password, it registered.
Of the three password sections in SMGR, I wasn't sure which one to use.

Thanks for the document references. I will look at those.
Reply With Quote
  #5  
Old 04-03-2017, 05:08 PM
sbrennan007 sbrennan007 is offline
Aspiring Member
 
Join Date: Jul 2010
Posts: 1
sbrennan007 has 10 reputation points
Default

Avaya Session Manager Password needs to be set to reflect the same...
Reply With Quote
  #6  
Old 05-26-2017, 06:01 AM
johns1224 johns1224 is offline
Brainiac
 
Join Date: Apr 2017
Posts: 56
johns1224 has 9 reputation points
Default

Thanks for sharing the documents, gwebster. Will look deeper into it.
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 02:54 PM.

This Forum is provided solely for the use and convenience of Avaya customers and partners. Use of the Forum is subject to the Terms and Use and Privacy Statement found at www.avaya.com. No other use is permitted. The Forum including all content posted is “AS IS” and Avaya expressly disclaims all warranties and/or guarantees as to its accuracy, reliability, usefulness, quality or non-infringement of intellectual property. Avaya reserves the right to remove any content posted on the Forum at any time and for whatever reason.

Avaya will not be liable for any content posted on this Forum, including, without limitation, any errors or omissions or for any losses or damages of any kind incurred as a result of use or reliance on any content, regardless of its origin.

You expressly understand and agree that you assume all risks associated with use or reliance on this content.