Avaya Support Forums  

Go Back   Avaya Support Forums > IP Telephony and Convergence

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 08-23-2013, 08:47 AM
katarj katarj is offline
Aspiring Member
 
Join Date: Aug 2013
Posts: 2
katarj has 10 reputation points
Default 9608 is showing [Feature Status Subscription failed. Error code= 404]

I have been trying to start the push agent on Avaya IP phone 9608. The crash log shows:
165>Aug 22 19:08:56 172.17.0.61 MSM: -04:00 2013 000 1 .TEL | 0 Registration process for SM[0] has been started.
<165>Aug 22 19:08:56 172.17.0.61 AST: -04:00 2013 000 1 .TEL | 0 Feature Status Subscription failed. Error code= 404.
<165>Aug 22 19:08:56 172.17.0.61 CONTACT: -04:00 2013 000 1 .TEL | 0 UpdateContacts-No data source -OR- Avaya Environment is [0]
<165>Aug 22 19:08:57 172.17.0.61 PUSHADAP: -04:00 2013 000 1 .TEL | 0 CVxPushAdaptor::StartWebServer, Cannot start Goahead webserver. port (-1) is an invalid port. PUSHCAP will be set to 00000.
<165>Aug 22 19:08:56 172.17.0.61 NETADAP: -04:00 2013 000 1 .TEL | 0 IP address of Adaptor eth0 = 172.17.0.61.
<165>Aug 22 19:08:57 172.17.0.61 PPMDATA: -04:00 2013 000 1 .TEL | 0 getContactList: Encountered SOAP Fault.



Environment:
Call manager: Asterisk 1.8
Firmware version on Avaya :6.2.2

According to my understanding of avaya environment, I have already added the server where asterisk is running to the TPSLIST in 46xxsettings.txt. Also, the extension has been added to the user.conf and sip.conf of asterisk configuration.

For SIP logs at the asterisk side , this is the debug log when phone logins:
<------------>
Really destroying SIP dialog '1_52166cf63910e5a3-5bd32610_S@172.17.0.61' Method: SUBSCRIBE
Really destroying SIP dialog '1_52166cf63910e5a3-5bd32610_R@172.17.0.61' Method: REGISTER

<--- Transmitting (no NAT) to 172.17.0.61:5060 --->
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 172.17.0.61:5060;branch=z9hG4bK1_52166e094306ad16-5bd336e0_R103;received=172.17.0.61
From: <sip:103@172.17.0.10>;tag=-3f291f052166e09-5bd322a8_F103172.17.0.61
To: <sip:103@172.17.0.10>;tag=as4eefb442
Call-ID: 1_52166e0939110b3c-5bd323cc_R@172.17.0.61
CSeq: 1 REGISTER
Server: Asterisk PBX 1.8.13.1~dfsg-1ubuntu2
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="0383559b"
Content-Length: 0


<------------>
Scheduling destruction of SIP dialog '1_52166e0939110b3c-5bd323cc_R@172.17.0.61' in 32000 ms (Method: REGISTER)
Sending to 172.17.0.61:5060 (no NAT)

<--- Transmitting (no NAT) to 172.17.0.61:5060 --->
SIP/2.0 200 OK
Via: SIP/2.0/UDP 172.17.0.61:5060;branch=z9hG4bK2_52166e0926522642-5bd327b7_R103;received=172.17.0.61
From: <sip:103@172.17.0.10>;tag=-3f291f052166e09-5bd322a8_F103172.17.0.61
To: <sip:103@172.17.0.10>;tag=as4eefb442
Call-ID: 1_52166e0939110b3c-5bd323cc_R@172.17.0.61
CSeq: 2 REGISTER
Server: Asterisk PBX 1.8.13.1~dfsg-1ubuntu2
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Expires: 900
Contact: <sip:103@172.17.0.61;transport=udp;avaya-sc-enabled>;expires=900
Date: Fri, 23 Aug 2013 00:01:14 GMT
Content-Length: 0


<------------>
Scheduling destruction of SIP dialog '1_52166e0939110b3c-5bd323cc_R@172.17.0.61' in 32000 ms (Method: REGISTER)

<--- Transmitting (no NAT) to 172.17.0.61:5060 --->
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 172.17.0.61:5060;branch=z9hG4bK1_52166e09-38f1f4c2-5bd32f66_S103;received=172.17.0.61
From: <sip:103@172.17.0.10>;tag=-f7cc74c52166e09-5bd32024_F103172.17.0.61
To: <sip:103@172.17.0.10>;tag=as3aecb239
Call-ID: 1_52166e0942cdc121-5bd323cd_S@172.17.0.61
CSeq: 1 SUBSCRIBE
Server: Asterisk PBX 1.8.13.1~dfsg-1ubuntu2
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="3ac4c477"
Content-Length: 0


<------------>
Scheduling destruction of SIP dialog '1_52166e0942cdc121-5bd323cd_S@172.17.0.61' in 32000 ms (Method: SUBSCRIBE)
Sending to 172.17.0.61:5060 (no NAT)
Looking for 103 in demo (domain 172.17.0.10)

<--- Transmitting (no NAT) to 172.17.0.61:5060 --->
SIP/2.0 404 Not Found
Via: SIP/2.0/UDP 172.17.0.61:5060;branch=z9hG4bK2_52166e09-64f4697a-5bd3245b_S103;received=172.17.0.61
From: <sip:103@172.17.0.10>;tag=-f7cc74c52166e09-5bd32024_F103172.17.0.61
To: <sip:103@172.17.0.10>;tag=as3aecb239
Call-ID: 1_52166e0942cdc121-5bd323cd_S@172.17.0.61
CSeq: 2 SUBSCRIBE
Server: Asterisk PBX 1.8.13.1~dfsg-1ubuntu2
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Content-Length: 0
Reply With Quote
  #2  
Old 08-27-2013, 04:06 PM
sinhar sinhar is offline
Member
.
 
Join Date: Mar 2012
Posts: 8
sinhar has 10 reputation points
Default

To get more idea and fix, please open a trouble ticket with Avaya (if not done till now). Engineer will have the whole picture and move towards fixing the issue quickly.
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 03:24 AM.

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.