Avaya 9608G SIP phone registration with Aterisk 1.8 (Free PBX)

Hi All

Has anyone ever successfully registered an Avaya 9608G sip phone on Asterisk?
I am trying to do so I first do a software upgrade to 6.4 in avaya ip phone. And configure SIP account in the IP phone
but it stuck with Acquiring Service…

Can anyone help me out, Thanks in advance

Asterisk Debug

<------------>

<— Transmitting (NAT) to 172.18.204.105:1056 —>
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 0.0.0.0;branch=z9hG4bK6_386d502c-3d293ea75e2bc5t2i3e102b725cd711m433h2e4z3t_R75320.0.0.0;received=172.18.204.105;rport=1056
From: sip:7532@172.17.0.24;tag=386d502c5e74ac5d4l506lm303m3i331u6om225b3c635p3l4h_F75320.0.0.0
To: sip:7532@172.17.0.24;tag=as6474e466
Call-ID: 6_386d502c2b6104c95yh4z1k1b55b6v231794h1z2k583t1r_R75320.0.0.0
CSeq: 6 REGISTER
Server: FPBX-2.8.1(1.8.7.0)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
WWW-Authenticate: Digest algorithm=MD5, realm=“asterisk”, nonce="4bc24840"
Content-Length: 0

<------------>
Scheduling destruction of SIP dialog ‘6_386d502c2b6104c95yh4z1k1b55b6v231794h1z2k583t1r_R75320.0.0.0’ in 32000 ms (Method: REGISTER)

e[KElastix*CLI>
e[0K
<— SIP read from UDP:172.18.204.105:1056 —>
REGISTER sip:172.17.0.24 SIP/2.0
From: sip:7532@172.17.0.24;tag=386d502c5e74ac5d4l506lm303m3i331u6om225b3c635p3l4h_F75320.0.0.0
To: sip:7532@172.17.0.24
Call-ID: 6_386d502c2b6104c95yh4z1k1b55b6v231794h1z2k583t1r_R75320.0.0.0
CSeq: 6 REGISTER
Max-Forwards: 70
Via: SIP/2.0/UDP 0.0.0.0;branch=z9hG4bK6_386d502c-3d293ea75e2bc5t2i3e102b725cd711m433h2e4z3t_R75320.0.0.0
Supported: eventlist,feature-ref,replaces,tdialog
Allow: INVITE,ACK,BYE,CANCEL,SUBSCRIBE,NOTIFY,MESSAGE,REFER,INFO,PUBLISH,UPDATE
User-Agent: Avaya one-X Deskphone 6.4.0.33 (33)
Contact: sip:7532@0.0.0.0;transport=udp;avaya-sc-enabled;q=1;expires=900;+avaya.gmtoffset=“0:00”;+avaya.js-ver=“1.0”;+avaya.model=“9608”;+avaya.sn=“16N51300701X”;+avaya.firmware=“S96x1_SALBR6_4_0r33_V4r83.tar”;+sip.instance=“urn:uuid:00000000-0000-1000-8000-d47856b0c536”;reg-id=1
Content-Length: 0

<------------->
— (12 headers 0 lines) —
Sending to 172.18.204.105:1056 (NAT)

<— Transmitting (NAT) to 172.18.204.105:1056 —>
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 0.0.0.0;branch=z9hG4bK6_386d502c-3d293ea75e2bc5t2i3e102b725cd711m433h2e4z3t_R75320.0.0.0;received=172.18.204.105;rport=1056
From: sip:7532@172.17.0.24;tag=386d502c5e74ac5d4l506lm303m3i331u6om225b3c635p3l4h_F75320.0.0.0
To: sip:7532@172.17.0.24
Call-ID: 6_386d502c2b6104c95yh4z1k1b55b6v231794h1z2k583t1r_R75320.0.0.0
CSeq: 6 REGISTER
Server: FPBX-2.8.1(1.8.7.0)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Content-Length: 0

<------------>

<— Transmitting (NAT) to 172.18.204.105:1056 —>
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 0.0.0.0;branch=z9hG4bK6_386d502c-3d293ea75e2bc5t2i3e102b725cd711m433h2e4z3t_R75320.0.0.0;received=172.18.204.105;rport=1056
From: sip:7532@172.17.0.24;tag=386d502c5e74ac5d4l506lm303m3i331u6om225b3c635p3l4h_F75320.0.0.0
To: sip:7532@172.17.0.24;tag=as6474e466
Call-ID: 6_386d502c2b6104c95yh4z1k1b55b6v231794h1z2k583t1r_R75320.0.0.0
CSeq: 6 REGISTER
Server: FPBX-2.8.1(1.8.7.0)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
WWW-Authenticate: Digest algorithm=MD5, realm=“asterisk”, nonce="4bc24840"
Content-Length: 0

<------------>
Scheduling destruction of SIP dialog ‘6_386d502c2b6104c95yh4z1k1b55b6v231794h1z2k583t1r_R75320.0.0.0’ in 32000 ms (Method: REGISTER)

e[KElastix*CLI>
e[0KReally destroying SIP dialog ‘1ad065e553c047847f4c1c812da0e490@172.25.14.24:5060’ Method: OPTIONS

e[KElastix*CLI>
e[0K
<— SIP read from UDP:172.18.204.105:1056 —>
REGISTER sip:172.17.0.24 SIP/2.0
From: sip:7532@172.17.0.24;tag=386d502c5e74ac5d4l506lm303m3i331u6om225b3c635p3l4h_F75320.0.0.0
To: sip:7532@172.17.0.24
Call-ID: 6_386d502c2b6104c95yh4z1k1b55b6v231794h1z2k583t1r_R75320.0.0.0
CSeq: 6 REGISTER
Max-Forwards: 70
Via: SIP/2.0/UDP 0.0.0.0;branch=z9hG4bK6_386d502c-3d293ea75e2bc5t2i3e102b725cd711m433h2e4z3t_R75320.0.0.0
Supported: eventlist,feature-ref,replaces,tdialog
Allow: INVITE,ACK,BYE,CANCEL,SUBSCRIBE,NOTIFY,MESSAGE,REFER,INFO,PUBLISH,UPDATE
User-Agent: Avaya one-X Deskphone 6.4.0.33 (33)
Contact: sip:7532@0.0.0.0;transport=udp;avaya-sc-enabled;q=1;expires=900;+avaya.gmtoffset=“0:00”;+avaya.js-ver=“1.0”;+avaya.model=“9608”;+avaya.sn=“16N51300701X”;+avaya.firmware=“S96x1_SALBR6_4_0r33_V4r83.tar”;+sip.instance=“urn:uuid:00000000-0000-1000-8000-d47856b0c536”;reg-id=1
Content-Length: 0

<------------->
— (12 headers 0 lines) —
Sending to 172.18.204.105:1056 (NAT)

<— Transmitting (NAT) to 172.18.204.105:1056 —>
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 0.0.0.0;branch=z9hG4bK6_386d502c-3d293ea75e2bc5t2i3e102b725cd711m433h2e4z3t_R75320.0.0.0;received=172.18.204.105;rport=1056
From: sip:7532@172.17.0.24;tag=386d502c5e74ac5d4l506lm303m3i331u6om225b3c635p3l4h_F75320.0.0.0
To: sip:7532@172.17.0.24
Call-ID: 6_386d502c2b6104c95yh4z1k1b55b6v231794h1z2k583t1r_R75320.0.0.0
CSeq: 6 REGISTER
Server: FPBX-2.8.1(1.8.7.0)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Content-Length: 0

<------------>

<— Transmitting (NAT) to 172.18.204.105:1056 —>
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 0.0.0.0;branch=z9hG4bK6_386d502c-3d293ea75e2bc5t2i3e102b725cd711m433h2e4z3t_R75320.0.0.0;received=172.18.204.105;rport=1056
From: sip:7532@172.17.0.24;tag=386d502c5e74ac5d4l506lm303m3i331u6om225b3c635p3l4h_F75320.0.0.0
To: sip:7532@172.17.0.24;tag=as6474e466
Call-ID: 6_386d502c2b6104c95yh4z1k1b55b6v231794h1z2k583t1r_R75320.0.0.0
CSeq: 6 REGISTER
Server: FPBX-2.8.1(1.8.7.0)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
WWW-Authenticate: Digest algorithm=MD5, realm=“asterisk”, nonce="4bc24840"
Content-Length: 0

<------------>
Scheduling destruction of SIP dialog ‘6_386d502c2b6104c95yh4z1k1b55b6v231794h1z2k583t1r_R75320.0.0.0’ in 32000 ms (Method: REGISTER)

e[KElastix*CLI>
e[0KRetransmitting #7 (no NAT) to 172.17.0.99:5060:
REGISTER sip:172.17.0.99 SIP/2.0
Via: SIP/2.0/UDP 172.17.0.24:5060;branch=z9hG4bK656ef72a
Max-Forwards: 70
From: sip:astcca@172.17.0.99;tag=as2ba46b07
To: sip:astcca@172.17.0.99
Call-ID: 4d60ebf06063fa9b7cf4e29b316290c3@127.0.0.1
CSeq: 40724 REGISTER
User-Agent: FPBX-2.8.1(1.8.7.0)
Expires: 120
Contact: sip:ldcca@172.17.0.24:5060
Content-Length: 0


e[KElastix*CLI>
e[0KREGISTER 10 headers, 0 lines
Reliably Transmitting (no NAT) to 172.17.0.99:5060:
REGISTER sip:172.17.0.99 SIP/2.0
Via: SIP/2.0/UDP 172.17.0.24:5060;branch=z9hG4bK2c81aecc
Max-Forwards: 70
From: sip:astcca@172.17.0.99;tag=as5118d870
To: sip:astcca@172.17.0.99
Call-ID: 4d60ebf06063fa9b7cf4e29b316290c3@127.0.0.1
CSeq: 40725 REGISTER
User-Agent: FPBX-2.8.1(1.8.7.0)
Expires: 120
Contact: sip:ldcca@172.17.0.24:5060
Content-Length: 0


Really destroying SIP dialog ‘4d60ebf06063fa9b7cf4e29b316290c3@127.0.0.1’ Method: REGISTER

e[KElastix*CLI>
e[0KRetransmitting #1 (no NAT) to 172.17.0.99:5060:
REGISTER sip:172.17.0.99 SIP/2.0
Via: SIP/2.0/UDP 172.17.0.24:5060;branch=z9hG4bK2c81aecc
Max-Forwards: 70
From: sip:astcca@172.17.0.99;tag=as5118d870
To: sip:astcca@172.17.0.99
Call-ID: 4d60ebf06063fa9b7cf4e29b316290c3@127.0.0.1
CSeq: 40725 REGISTER
User-Agent: FPBX-2.8.1(1.8.7.0)
Expires: 120
Contact: sip:ldcca@172.17.0.24:5060
Content-Length: 0


e[KElastix*CLI>
e[0K
<— SIP read from UDP:172.18.204.105:1056 —>
REGISTER sip:172.17.0.24 SIP/2.0
From: sip:7532@172.17.0.24;tag=386d502c5e74ac5d4l506lm303m3i331u6om225b3c635p3l4h_F75320.0.0.0
To: sip:7532@172.17.0.24
Call-ID: 6_386d502c2b6104c95yh4z1k1b55b6v231794h1z2k583t1r_R75320.0.0.0
CSeq: 6 REGISTER
Max-Forwards: 70
Via: SIP/2.0/UDP 0.0.0.0;branch=z9hG4bK6_386d502c-3d293ea75e2bc5t2i3e102b725cd711m433h2e4z3t_R75320.0.0.0
Supported: eventlist,feature-ref,replaces,tdialog
Allow: INVITE,ACK,BYE,CANCEL,SUBSCRIBE,NOTIFY,MESSAGE,REFER,INFO,PUBLISH,UPDATE
User-Agent: Avaya one-X Deskphone 6.4.0.33 (33)
Contact: sip:7532@0.0.0.0;transport=udp;avaya-sc-enabled;q=1;expires=900;+avaya.gmtoffset=“0:00”;+avaya.js-ver=“1.0”;+avaya.model=“9608”;+avaya.sn=“16N51300701X”;+avaya.firmware=“S96x1_SALBR6_4_0r33_V4r83.tar”;+sip.instance=“urn:uuid:00000000-0000-1000-8000-d47856b0c536”;reg-id=1
Content-Length: 0

<------------->
— (12 headers 0 lines) —
Sending to 172.18.204.105:1056 (NAT)

<— Transmitting (NAT) to 172.18.204.105:1056 —>
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 0.0.0.0;branch=z9hG4bK6_386d502c-3d293ea75e2bc5t2i3e102b725cd711m433h2e4z3t_R75320.0.0.0;received=172.18.204.105;rport=1056
From: sip:7532@172.17.0.24;tag=386d502c5e74ac5d4l506lm303m3i331u6om225b3c635p3l4h_F75320.0.0.0
To: sip:7532@172.17.0.24
Call-ID: 6_386d502c2b6104c95yh4z1k1b55b6v231794h1z2k583t1r_R75320.0.0.0
CSeq: 6 REGISTER
Server: FPBX-2.8.1(1.8.7.0)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Content-Length: 0

<------------>

<— Transmitting (NAT) to 172.18.204.105:1056 —>
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 0.0.0.0;branch=z9hG4bK6_386d502c-3d293ea75e2bc5t2i3e102b725cd711m433h2e4z3t_R75320.0.0.0;received=172.18.204.105;rport=1056
From: sip:7532@172.17.0.24;tag=386d502c5e74ac5d4l506lm303m3i331u6om225b3c635p3l4h_F75320.0.0.0
To: sip:7532@172.17.0.24;tag=as6474e466
Call-ID: 6_386d502c2b6104c95yh4z1k1b55b6v231794h1z2k583t1r_R75320.0.0.0
CSeq: 6 REGISTER
Server: FPBX-2.8.1(1.8.7.0)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
WWW-Authenticate: Digest algorithm=MD5, realm=“asterisk”, nonce="4bc24840"
Content-Length: 0

You appear to have configured a password in Asterisk, but not on the phone.

Also, any logs posted here need to be marked as unformatted text.

Sorry for that long post. Thank you; I configure a Chan_sip Extension in free pbx and configure the extension in avaya 9608G phone with the sip server TCP/UDP 5060 and the username and password but it is not getting register.

1 Like

I’ve given you one possibility, which is that you haven’t have asked Asterisk to check a password but haven’t told the peer any password.

The other possibility is that 172.18.204.105:1056 is not actually routing to the peer and the responses are getting lost.