I know I've seen this asked here before, none of the listed solutions worked for me. SIP trace from the phone below (IPs obscured)
Sep 26 15:07:47: TX 658 bytes Request msg REGISTER/cseq=56711 (tdta0x3286c8) to tcp xxx.xxx.xxx.xxx:5060:
REGISTER sip:xxx.xxx.xxx.xxx;transport=tcp SIP/2.0
Via: SIP/2.0/tcp xxx.xxx.xxx.xxx:16388;rport;branch=z9hG4bKPj63NybzFmMoQ1VuTboGP5pjQlFayjXZrm;alias
Max-Forwards: 70
From: <sip:1850@xxx.xxx.xxx.xxx>;tag=GG43E8YftusLCxGaZzgFZkQ2C4v-fblw
To: <sip:1850@xxx.xxx.xxx.xxx>
Call-ID: paDue5DRr6ckZrk5ldcoYgUEwd48r5D0
CSeq: 56711 REGISTER
User-Agent: Avaya B179 2.3.9
Supported: outbound, path
Contact: <sip:1850@xxx.xxx.xxx.xxx:5060;transport=TCP;ob>;reg-id=1;+sip.instance="<urn:uuid:00000000-0000-0000-0000-0000d55b02c6>"
Expires: 1800
Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS
Content-Length: 0
---------------------------------------------------------------------------------
Sep 26 15:07:47: RX 474 bytes Response msg 403/REGISTER/cseq=56711 (rdata0x329490) from tcp xxx.xxx.xxx.xxx:5060:
SIP/2.0 403 Forbidden
Via: SIP/2.0/tcp xxx.xxx.xxx.xxx:16388;rport;branch=z9hG4bKPj63NybzFmMoQ1VuTboGP5pjQlFayjXZrm;alias
From: <sip:1850@xxx.xxx.xxx.xxx>;tag=GG43E8YftusLCxGaZzgFZkQ2C4v-fblw
To: <sip:1850@xxx.xxx.xxx.xxx>;tag=f0e15f0932d3c4b0
Call-ID: paDue5DRr6ckZrk5ldcoYgUEwd48r5D0
CSeq: 56711 REGISTER
User-Agent: IP Office 6.1 (22)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, INFO, SUBSCRIBE, REGISTER, PUBLISH
Supported: timer
Content-Length: 0
The only thing I have not tried is rebooting the system. I also note we have IP office 8.1 but the 500 switches are R6.1. Wonder if it is compatibility. Can't get a straight answer from Avaya.
Sep 26 15:07:47: TX 658 bytes Request msg REGISTER/cseq=56711 (tdta0x3286c8) to tcp xxx.xxx.xxx.xxx:5060:
REGISTER sip:xxx.xxx.xxx.xxx;transport=tcp SIP/2.0
Via: SIP/2.0/tcp xxx.xxx.xxx.xxx:16388;rport;branch=z9hG4bKPj63NybzFmMoQ1VuTboGP5pjQlFayjXZrm;alias
Max-Forwards: 70
From: <sip:1850@xxx.xxx.xxx.xxx>;tag=GG43E8YftusLCxGaZzgFZkQ2C4v-fblw
To: <sip:1850@xxx.xxx.xxx.xxx>
Call-ID: paDue5DRr6ckZrk5ldcoYgUEwd48r5D0
CSeq: 56711 REGISTER
User-Agent: Avaya B179 2.3.9
Supported: outbound, path
Contact: <sip:1850@xxx.xxx.xxx.xxx:5060;transport=TCP;ob>;reg-id=1;+sip.instance="<urn:uuid:00000000-0000-0000-0000-0000d55b02c6>"
Expires: 1800
Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS
Content-Length: 0
---------------------------------------------------------------------------------
Sep 26 15:07:47: RX 474 bytes Response msg 403/REGISTER/cseq=56711 (rdata0x329490) from tcp xxx.xxx.xxx.xxx:5060:
SIP/2.0 403 Forbidden
Via: SIP/2.0/tcp xxx.xxx.xxx.xxx:16388;rport;branch=z9hG4bKPj63NybzFmMoQ1VuTboGP5pjQlFayjXZrm;alias
From: <sip:1850@xxx.xxx.xxx.xxx>;tag=GG43E8YftusLCxGaZzgFZkQ2C4v-fblw
To: <sip:1850@xxx.xxx.xxx.xxx>;tag=f0e15f0932d3c4b0
Call-ID: paDue5DRr6ckZrk5ldcoYgUEwd48r5D0
CSeq: 56711 REGISTER
User-Agent: IP Office 6.1 (22)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, INFO, SUBSCRIBE, REGISTER, PUBLISH
Supported: timer
Content-Length: 0
The only thing I have not tried is rebooting the system. I also note we have IP office 8.1 but the 500 switches are R6.1. Wonder if it is compatibility. Can't get a straight answer from Avaya.