Hello, trying to connect an Avaya 9621G to Freepbx.
UPDATE : Successful ! See the end of this post.
What I found is : Connecting in UDP does not seem to work well. When I try to connect (set username and password), the phone displays “Acquiring service…” forever.
The Avaya phone speaks on port 1025, and Asterisk tries to connect to 5060, although I have port=1025 in the phone config. I see lot of 0.0.0.0 adresses in the log. Here is SIP debug log (192.168.1.93 is the address of the phone) :
<--- SIP read from UDP:192.168.1.93:1025 --->
REGISTER sip:192.168.1.182 SIP/2.0
From: <sip:[email protected]>;tag=386ddfa8-32f830d71d5y635t5991d185n3gt3b392s3e6f5n2r_F490.0.0.0
To: <sip:[email protected]>
Call-ID: 15_386ddfa86c8d1c495hw37314h321s5b5a3p456i3m6f4t2e2e3c_R490.0.0.0
CSeq: 21 REGISTER
Max-Forwards: 70
Via: SIP/2.0/UDP 0.0.0.0;branch=z9hG4bK15_386ddfa81b77ea011s4ai4k4v2j5x1v5d3i243x4i1p10165g2w_R490.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 7.0.0.39 (39)
Contact: <sip:[email protected];transport=udp;avaya-sc-enabled>;q=1;expires=900;avaya-actions="presence.initiate-pubsub,presence.redirect";+avaya.gmtoffset="0:00";+avaya.js-ver="1.0";+avaya.model="9621";+avaya.sn="11WZ471604VR";+avaya.firmware="S96x1_SALBR7_0_0r39_V4r83.tar";+sip.instance="<urn:uuid:00000000-0000-1000-8000-2cf4c5eea0b0>";reg-id=1
Content-Length: 0
<------------->
--- (12 headers 0 lines) ---
Sending to 192.168.1.93:5060 (no NAT)
<--- Transmitting (no NAT) to 192.168.1.93:5060 --->
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 0.0.0.0;branch=z9hG4bK15_386ddfa81b77ea011s4ai4k4v2j5x1v5d3i243x4i1p10165g2w_R490.0.0.0;received=192.168.1.93
From: <sip:[email protected]>;tag=386ddfa8-32f830d71d5y635t5991d185n3gt3b392s3e6f5n2r_F490.0.0.0
To: <sip:[email protected]>;tag=as19942915
Call-ID: 15_386ddfa86c8d1c495hw37314h321s5b5a3p456i3m6f4t2e2e3c_R490.0.0.0
CSeq: 21 REGISTER
Server: FPBX-2.8.1(1.8.20.1)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="7f016178"
Content-Length: 0
So it is better to connect in TCP. I set it in the CRAFT procedure of the phone, in SIP menu and SIP Proxy Server configuration.
I added in Asterisk SIP settings :
tcpenable=yes
tcpbindaddr=0.0.0.0
I also set nat=no, as recommended in this post.
Now the situation is :
Communication seems OK in the log. The port is the same for sending and receiving, and I no longer see 0.0.0.0 addresses. On the phone, the message sent appears on the screen.
If I deliberately set a wrong password, I get : 403 Forbidden (Bad Auth)
If I set the right password, I get : 403 Forbidden.
And no reason is indicated for the error.
I am stuck there and don’t know what may be wrong.
=========================================================
UPDATE : I found the problem.
The log indicated that this extension was not set for TCP.
I added transport=tcp in the extension configuration (sip_additional.conf) and now the phone works in FreeBBX !
I am using Elastix 2.5
I will post later a more detailed report of all the steps necessary to have this beautiful phone work with FreePBX / Elastix