I have an Avaya J179 that I just installed. First one on our network. Our other phones are H323 devices except for a few SIP intercoms and conference phones.
We're on Communication Manager 7.1.3 and System Manager 7.1.3.
Long story short, I can make outgoing calls, but incoming calls (external or internal) get a busy signal.
If I log into the same extension on one of our 9608 phones, it works fine.
If I log into the J179 with an extension I know works, now calling that extension will get a busy signal.
I ran a call trace on both a working extension (on a 9608) and the extension on this J179. Working call trace is extension 4601 and the non-working is 4602. (though if I use 4601 on the J179, it won't work)
What step could I have missed? Thanks for any advice!
Working
Non-working
We're on Communication Manager 7.1.3 and System Manager 7.1.3.
Long story short, I can make outgoing calls, but incoming calls (external or internal) get a busy signal.
If I log into the same extension on one of our 9608 phones, it works fine.
If I log into the J179 with an extension I know works, now calling that extension will get a busy signal.
I ran a call trace on both a working extension (on a 9608) and the extension on this J179. Working call trace is extension 4601 and the non-working is 4602. (though if I use 4601 on the J179, it won't work)
What step could I have missed? Thanks for any advice!
Working
Code:
16:16:21 TRACE STARTED 05/24/2019 CM Release String cold-01.0.532.0-24811
16:16:22 G711MU ss:off ps:20
rgn:1 [10.20.2.11]:50886
rgn:1 [10.20.1.2]:50054
16:16:24 dial 4061
16:16:24 term station 4061 cid 0x2c3c
16:16:24 Called party uses public-unknown-numbering
16:16:24 SIP>INVITE sip:[email protected] SIP/2.0
16:16:24 Call-ID: f2e3f79e7e7941e985d105056aa1092
16:16:24 SIP<SIP/2.0 100 Trying
16:16:24 Call-ID: f2e3f79e7e7941e985d105056aa1092
16:16:24 SIP<INVITE sip:[email protected] SIP/2.0
16:16:24 Call-ID: f2e3f79e7e7941e985d105056aa1092
16:16:24 SIP>INVITE sip:[email protected] SIP/2.0
16:16:24 Call-ID: f2e3f79e7e7941e985d105056aa1092
16:16:24 SIP<SIP/2.0 100 Trying
16:16:24 Call-ID: f2e3f79e7e7941e985d105056aa1092
16:16:24 SIP>SIP/2.0 100 Trying
16:16:24 Call-ID: f2e3f79e7e7941e985d105056aa1092
16:16:24 SIP<SIP/2.0 180 Ringing
16:16:24 Call-ID: f2e3f79e7e7941e985d105056aa1092
16:16:24 SIP>SIP/2.0 180 Ringing
16:16:24 Call-ID: f2e3f79e7e7941e985d105056aa1092
16:16:24 SIP<SIP/2.0 180 Ringing
16:16:24 Call-ID: f2e3f79e7e7941e985d105056aa1092
16:16:24 SIP>PRACK sip:[email protected];gsid=f2e3f262-7e79-41e9-85c
16:16:24 SIP>e-005056aa1092;epv=%3Csip:4061%40kcgc.gov%3Bgr%3De47298
16:16:24 SIP>30529cef7cda3536cb4500e1dc%3E SIP/2.0
16:16:24 Call-ID: f2e3f79e7e7941e985d105056aa1092
16:16:24 ring station 4061 cid 0x2c3c
16:16:24 Alerting party uses private-numbering
16:16:24 SIP<SIP/2.0 200 OK
16:16:24 Call-ID: f2e3f79e7e7941e985d105056aa1092
VOIP data from: [10.20.1.2]:50054
16:16:33 Jitter:1 0 0 0 0 0 0 0 0 0: Buff:19 WC:12 Avg:1
16:16:33 Pkloss:0 0 0 0 0 0 0 0 0 0: Oofo:0 WC:0 Avg:0
16:16:36 idle station 2554 cid 0x2c3c
16:16:55 TRACE COMPLETE station 2554 cid 0x0
Code:
16:02:45 TRACE STARTED 05/24/2019 CM Release String cold-01.0.532.0-24811
16:02:50 G711MU ss:off ps:20
rgn:1 [10.20.2.11]:50886
rgn:1 [10.20.1.2]:50050
16:02:52 dial 4062
16:02:52 term station 4062 cid 0x2822
16:02:52 Called party uses public-unknown-numbering
16:02:52 SIP>INVITE sip:[email protected] SIP/2.0
16:02:52 Call-ID: f730a07e7841e9824a05056aa1092
16:02:52 SIP<SIP/2.0 100 Trying
16:02:52 Call-ID: f730a07e7841e9824a05056aa1092
16:02:52 SIP<INVITE sip:[email protected] SIP/2.0
16:02:52 Call-ID: f730a07e7841e9824a05056aa1092
16:02:52 SIP>INVITE sip:[email protected] SIP/2.0
16:02:52 Call-ID: f730a07e7841e9824a05056aa1092
16:02:52 SIP<SIP/2.0 100 Trying
16:02:52 Call-ID: f730a07e7841e9824a05056aa1092
16:02:52 SIP>SIP/2.0 100 Trying
16:02:52 Call-ID: f730a07e7841e9824a05056aa1092
16:02:52 SIP<SIP/2.0 400 Bad Request (Invalid avaya-cm-line)
16:02:52 Call-ID: f730a07e7841e9824a05056aa1092
16:02:52 SIP>ACK sip:[email protected] SIP/2.0
16:02:52 Call-ID: f730a07e7841e9824a05056aa1092
16:02:52 SIP>SIP/2.0 400 Bad Request (Invalid avaya-cm-line)
16:02:52 Call-ID: f730a07e7841e9824a05056aa1092
16:02:52 SIP<SIP/2.0 400 Bad Request (Invalid avaya-cm-line)
16:02:52 Call-ID: f730a07e7841e9824a05056aa1092
16:02:52 SIP>ACK sip:[email protected] SIP/2.0
16:02:52 Call-ID: f730a07e7841e9824a05056aa1092
16:02:52 reorder station 4062 cid 0x2822
16:02:56 idle station 2554 cid
16:03:22 TRACE COMPLETE station 2554 cid 0x0
Comment