Dismiss Notice
We would like to remind you that we’re updating our login process for all 3CX forums whereby you will be able to login with the same credentials you use for the Partner or Customer Portal. Click here to read more.

problem making outbound calls

Discussion in '3CX Phone System - General' started by Tony Ng, Mar 5, 2015.

Thread Status:
Not open for further replies.
  1. Tony Ng

    Joined:
    Mar 5, 2015
    Messages:
    3
    Likes Received:
    0
    Hi!

    I am trying to get 3CX up and running with the few Avaya 1140e SIP phones.

    3CX recognize the 1140E's and i am able to set and extension on each sets.I also got the 3CX phone working as well as my iphone with the 3CX app.

    Now my problem is the 3CX can call the 1140e's i can pick up and talk but when i use the 1140e's to dial out to the 3CX phone on the computer it says (call denied,prohibited).

    My 1140e's can receive calls but they cant dial.

    I hope someone can help me out.

    Thank you!
     
  2. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    11,127
    Likes Received:
    330
    Could you post one of the 3CX server logs of a call?

    Are these sets located on the same LAN as the server?
     
  3. Tony Ng

    Joined:
    Mar 5, 2015
    Messages:
    3
    Likes Received:
    0
    Hi!

    All the sets are on the same LAN.
    I am not sure if this is the log you are looking for but here it is.

    05-Mar-2015 19:47:43.635 Leg L:107.1[Unknown:] is terminated: Cause: BYE from PBX
    05-Mar-2015 19:47:43.584 [CM502001]: Source info: From: <sip:105@avaya.com>;tag=83638dff87; To: <sip:103@avaya.com>
    05-Mar-2015 19:47:43.584 [CM503013]: Call(C:107): Incoming call rejected, caller is unknown; msg=Ivite-IN Recv Req INVITE from 192.168.1.120:5060 tid=0dc33c2dafb7910b0 Call-ID=3df62c61af2fdbc4:
    INVITE sip:103@avaya.com SIP/2.0
    Via: SIP/2.0/UDP 192.168.1.120:5060;branch=z9hG4bK0dc33c2dafb7910b0
    Max-Forwards: 70
    Contact: <sip:105@192.168.1.120>
    To: <sip:103@avaya.com>
    From: <sip:105@avaya.com>;tag=83638dff87
    Call-ID: 3df62c61af2fdbc4
    CSeq: 21897 INVITE
    Expires: 180
    Session-Expires: 1800
    Min-SE: 1800
    Accept: application/sdp
    Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, REFER, INFO, MESSAGE, NOTIFY, UPDATE
    Content-Type: application/sdp
    Proxy-Authorization: Digest username="105",realm="3CXPhoneSystem",nonce="414d535c0b098a2f60:cb80832bc6710309f24db8388ef0a436",uri="sip:103@avaya.com",response="5aaaf4ef2f7545d238a7c0db5c93829c",algorithm=MD5
    Supported: timer, replaces
    User-Agent: Avaya IP Phone 1140E (SIP1140e.04.03.12.00)
    Allow-Events: talk, hold
    Content-Length: 299
    Remote-Party-ID: <sip:105@avaya.com>;screen=yes;party=calling;privacy=off
    x-nt-GUID: 0016CA00FCF2
     
  4. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    11,127
    Likes Received:
    330
    Being all on the same LAN I would not expect to see domain names...

    To: <sip:103@avaya.com>
    From: <sip:105@avaya.com>;tag=83638dff87

    If you are actually using them in the datafill of the set, then that same Domain Name must be datafilled in the 3CX Server as well (it's in the advanced settings), or the call will be rejected for security reasons. This will usually only affect only calls from sets outside the LAN, as that is normally when one would normally expect to see it. Any internal set should be using the local IP of the server, unless you have some reason not to.
     
  5. Tony Ng

    Joined:
    Mar 5, 2015
    Messages:
    3
    Likes Received:
    0
    Thank you so much for the help!! I finally got the sets to work. Have a nice day!
     
Thread Status:
Not open for further replies.