Issues with Avaya Trunk and 3CX

Discussion in '3CX Phone System - General' started by BAYSHORE, May 8, 2012.

Thread Status:
Not open for further replies.
  1. BAYSHORE

    Joined:
    Jul 16, 2010
    Messages:
    5
    Likes Received:
    0
    We are trying to connect a AVAYA-SM-6.1.5.0.615006 into our 3CX using a SIP Trunk.

    We have set up the connection as a VOIP Provider and the connection goes green but when we send a call from Avaya to 3CX we get "Unidentified incoming call. Review INVITE and adjust source identification:
    INVITE sip:5084@10.210.2.9 SIP/2.0"

    When we run Wireshark we see we are getting a 407 Forbidden message

    We have set the Require Registration set to Do not require

    Part of the problem is the Hospitals Avaya can not send username and password down thier Trunk

    Here is part of the 3CX logs

    15:26:26.227 [CM500002]: Unidentified incoming call. Review INVITE and adjust source identification:
    INVITE sip:5084@192.168.2.9 SIP/2.0
    Via: SIP/2.0/UDP 192.168.7.7;rport=5060;branch=z9hG4bK0AC90766FFFFFFFFFD43ED2A056185061-AP;ft=192.168.7.7~13c4
    Via: SIP/2.0/UDP 192.168.7.102:15070;branch=z9hG4bK0AC90766FFFFFFFFFD43ED2A056185061
    Via: SIP/2.0/UDP 192.168.7.102:15070;branch=z9hG4bK0AC90766FFFFFFFFFD43ED2A156185059
    Via: SIP/2.0/UDP 192.168.7.102:15070;branch=z9hG4bK0AC90766FFFFFFFFFD43ED2A156185058
    Via: SIP/2.0/TLS 192.168.7.7;branch=z9hG4bK0AC9066BFFFFFFFFFD601EBC0392656698-AP-AP;ft=1929
    Via: SIP/2.0/TLS 192.168.6.7;branch=z9hG4bK0AC9066BFFFFFFFFFD601EBC0392656698-AP;ft=4493728
    Via: SIP/2.0/TLS 192.168.6.107:15080;branch=z9hG4bK0AC9066BFFFFFFFFFD601EBC0392656698
    Via: SIP/2.0/TLS 192.168.6.107:15080;branch=z9hG4bK0AC9066BFFFFFFFFFD601EBC1392656696
    Via: SIP/2.0/TLS 192.168.6.107:15080;branch=z9hG4bK0AC9066BFFFFFFFFFD601EBC1392656695
    Via: SIP/2.0/TLS 192.168.6.7;branch=z9hG4bK0AC90766FFFFFFFFFD43ED2A056185042-AP-AP;ft=498
    Via: SIP/2.0/TLS 192.168.7.7;branch=z9hG4bK0AC90766FFFFFFFFFD43ED2A056185042-AP;ft=1714731
    Via: SIP/2.0/TLS 192.168.7.102:15080;branch=z9hG4bK0AC90766FFFFFFFFFD43ED2A056185042
    Via: SIP/2.0/TLS 192.168.7.102:15080;branch=z9hG4bK0AC90766FFFFFFFFFD43ED2A156185040
    Via: SIP/2.0/TLS 192.168.7.102:15080;branch=z9hG4bK0AC90766FFFFFFFFFD43ED2A156185039
    Via: SIP/2.0/TLS 192.168.7.7;branch=z9hG4bK80f88f85d9a8e11a58c4f494bdc00-AP;ft=1390433
    Via: SIP/2.0/TLS 192.168.6.9;branch=z9hG4bK80f88f85d9a8e11a58c4f494bdc00
    Via: SIP/2.0/TLS 192.168.163.113:5061;branch=z9hG4bK58_4fa2a3b0-5621ac8f-60bab884_I2667142
    Max-Forwards: 50
    Route: <sip:192.168.2.9;lr;phase=terminating>
    Record-Route: <sip:1ed584a2@192.168.7.7;transport=udp;lr>
    Record-Route: <sip:192.168.7.102:15060;lr;sap=710381234*1*016asm-callprocessing.sar1711720714~1336073201676~-1015134509~1>
    Record-Route: <sip:1ed584a2@192.168.7.7;transport=tls;lr>
    Record-Route: <sip:3698c904@192.168.6.7;transport=tls;lr>
    Record-Route: <sip:192.168.6.107:15061;lr;sap=709457718*1*016asm-callprocessing.sar1795541258~1336073201639~-1455961976~1;transport=tls>
    Record-Route: <sip:3698c904@192.168.6.7;transport=tls;lr>
    Record-Route: <sip:1ed584a2@192.168.7.7;transport=tls;lr>
    Record-Route: <sip:192.168.7.102:15061;lr;sap=710381234*1*016asm-callprocessing.sar1711720714~1336073201639~-1015134513~1;transport=tls>
    Record-Route: <sip:1ed584a2@192.168.7.7;transport=tls;lr>
    Record-Route: <sip:192.168.6.9:5061;transport=tls;lr>
    Contact: "Nurse Station"<sip:2667142@192.168.6.9:5061;transport=tls>
    To: <sip:5084@192.168.2.9>
    From: "Nurse Station"<sip:2667142@192.168.2.9>;tag=80f88f85d9a8e11a38c4f494bdc00
    Call-ID: 80f88f85d9a8e11a48c4f494bdc00
    CSeq: 1 INVITE
    Session-Expires: 1200;refresher=uac
    Min-SE: 1200
    Alert-Info: <cid:internal@bayshore.com>;avaya-cm-alert-type=internal
    Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY, REFER, INFO, PRACK, PUBLISH
    Supported: 100rel, histinfo, join, replaces, sdp-anat, timer
    User-Agent: Avaya one-X Deskphone 6.0.3.8a AVAYA-SM-6.1.5.0.615006 Avaya CM/R016x.00.1.510.1
    P-Asserted-Identity: "Nurse Station" <sip:2667142@192.168.2.9>
    Content-Length: 0
    P-Charging-Vector: icid-value="79de9ce4-9374-42da-a700-32deb991c064"
    P-Location: SM;origlocname="PCO-CM";termlocname="Hill-Rom-Nurse-Call"



    ****************I changed the IP address and domain to protect the innocent**********************


    192.168.2.9 is the IP address of the 3CX server
    192.168.7.7 and 192.168.6.7 are the IP adresses of the Avaya PBX
    domain is bayshore.com

    *******************************************************************************************************************

    Thank you in advance for any help you can
     
  2. KerryG

    KerryG Active Member

    Joined:
    Jun 19, 2009
    Messages:
    960
    Likes Received:
    0
    You probably need to add the incoming number from the Avaya into the Source ID section of the 3CX trunk.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. SY

    SY Well-Known Member
    3CX Support

    Joined:
    Jan 26, 2007
    Messages:
    1,825
    Likes Received:
    2
    set of "Via" and "Record-Route" should be explained more then just
    Thanks
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  4. rayfield

    rayfield New Member

    Joined:
    May 4, 2010
    Messages:
    124
    Likes Received:
    2
    Shouldn't a connection like this be set up in 3CX as a "SIP Trunk", rather than a "VoIP Provider"?

    John Rayfield, Jr. CETma
     
Thread Status:
Not open for further replies.