3CX running SIP on different port than 5060

Discussion in '3CX Phone System - General' started by synologic, Sep 24, 2012.

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

    Joined:
    Sep 24, 2012
    Messages:
    2
    Likes Received:
    0
    Hi,

    i have a free install of 3CX running on a port other than 5060, specifically 5063. There's no technical reason for this since the system runs on a closed network. It also appears that running on 5060 it works just fine.

    The problem i encounter, is that from time to time, i get Not Acceptable Here error when calling from an outside number to a local number, with a very strange reason:

    24-09-2012 18:00:48.533 [MS105000] C:210.2: No RTP packets were received:remoteAddr=192.168.0.128:21372,extAddr=0.0.0.0:0,localAddr=192.168.0.30:7432
    24-09-2012 18:00:46.830 [CM503007]: Call(C:210): Extn:102 has joined, contact <sip:102@192.168.0.128:5063>
    24-09-2012 18:00:46.830 Leg L:210.2[Extn] is terminated: Cause: 200 BYE from PBX
    24-09-2012 18:00:45.486 Leg L:210.1[Line:10002<<NUMBER_REMOVED] is terminated: Cause: 200 BYE from PBX
    24-09-2012 18:00:45.439 [CM503020]: Call(C:210): Normal call termination. Call originator: Line:10002<<NUMBER_REMOVED. Reason: Terminated
    24-09-2012 18:00:45.439 [CM503016]: Call(C:210): Attempt to reach <sip:102@192.168.0.30:5063> from Line:10002<<NUMBER_REMOVED has failed. Reason: Not Acceptable HereReason Unknown
    24-09-2012 18:00:45.095 [CM503025]: Call(C:210): Calling T:Extn:102@[Dev:sip:102@192.168.0.128:5063]
    24-09-2012 18:00:45.064 [CM503027]: Call(C:210): From: Line:10002<<NUMBER_REMOVED ("NUMBER_REMOVED" <sip:NUMBER_REMOVED@192.168.0.110:5063>) to T:Extn:102@[Dev:sip:102@192.168.0.128:5063]
    24-09-2012 18:00:45.064 [CM503004]: Call(C:210): Route 1: T:Extn:102@[Dev:sip:102@192.168.0.128:5063]
    24-09-2012 18:00:45.064 [CM505003]: Provider:[NUMBER_REMOVED] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Sippy] PBX contact: [sip:NUMBER_REMOVED@IP_REMOVED:5063]
    24-09-2012 18:00:45.064 [CM503001]: Call(C:210): Incoming call from Line:10002<<NUMBER_REMOVED to <sip:102@192.168.0.30:5063>
    24-09-2012 18:00:44.783 [CM503012]: Inbound office hours rule (unnamed) for 10002 forwards to DN:102

    It seems the call fails because the PBX receives Ringing message from the terminal being called :)

    Since switching back to 5060 the problem seems resolved, this is not a critical issue, however, changing the SIP port might prove useful someday depending on the setups.

    Anybody has any insight on this issue ?

    Regards,
    Viorel
     
  2. SY

    SY Well-Known Member
    3CX Support

    Joined:
    Jan 26, 2007
    Messages:
    1,825
    Likes Received:
    2
    I don't think that SIP port is related to the problem
    What is the "terminal" (102) where from this "ringing" comes?
    Initiator is Sippy, it is obvious ;)

    Verbose log can explain situation, if you need we can check it together
    Use code ctag for logs.
    Regards :)
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. synologic

    Joined:
    Sep 24, 2012
    Messages:
    2
    Likes Received:
    0
    Just a quick reply since there will be a few days since i can take 3CX down and provide verbose logging, 102 is a phone (chinese unknown brand).

    The call path is from outside number (sip provider) -> ring group -> extension (single extension in the ring group).
    It only happens when i put the sip port on 5063, honestly i haven't tried other ports since i had to put the system back up.

    If there's any other tests you have in mind, please let me know, i will take down the system in the weekend and test / provide logs.
     
Thread Status:
Not open for further replies.