Outgoing calls - patton 4552

Discussion in '3CX Phone System - General' started by hasler, Jan 14, 2009.

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

    Joined:
    Jan 7, 2009
    Messages:
    20
    Likes Received:
    0
    Hi.
    I'm new to 3cx.
    Actually I have installed the latest 3cx version an connected successfully the connected the patton 4552 R5.2 2008-11-14 SIP
    Incomings calls work but i can't make any outgoing call.
    I created an outgoing rule for the Patton 4552, but I had no luck with this.

    Here the log from an outgoing call

    13:25:52.206 [CM503008]: Call(37): Call is terminated

    13:25:52.175 [CM503015]: Call(37): Attempt to reach <sip:0474412104@192.168.1.3:5060> failed. Reason: Not Found

    13:25:52.160 [CM503004]: Call(37): Calling: Unknown:mad:[Dev]

    13:25:52.160 [CM503010]: Making route(s) to <sip:0474412104@192.168.1.3:5060>

    13:25:52.160 [CM505001]: Ext.10: Device info: Device Identified: [Man: 3CX Ltd.;Mod: 3CX VoIP Client;Rev: General] Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CX Phone 7.0.4184.0] Transport: [sip:192.168.1.3:5060]

    13:25:52.113 [CM503001]: Call(37): Incoming call from Ext.10 to <sip:0474412104@192.168.1.3:5060>

    13:25:52.113 [MS003005] C:37.1: Failed to create Endpoint: (destination=192.168.1.116)
    EndPoint: ID=00000036@(LOCAL)
    LOGID=C:37.1 Status: MSEP_FAILED
    RTP:192.168.1.3:7072
    RTCP:192.168.1.3:7073
    STUN RTP:0.0.0.0:0
    STUN RTCP:0.0.0.0:0
    Coder:
    NOT SET
    101:telephony-event
    Party ptime:20
    Party RTP:0.0.0.0:0
    Party RTCP:0.0.0.0:0
    Decoders:
    <empty>


    13:25:52.113 [MS003002] C:37.1: RTP socket 192.168.1.3:7072 binding failed with error code 10048

    13:25:52.050 [CM500002]: Info on incoming INVITE:

    INVITE sip:0474412104@192.168.1.3:5060 SIP/2.0

    Via: SIP/2.0/UDP 192.168.1.116:5070;branch=z9hG4bK-d8754z-c448d3348732c27e-1---d8754z-;rport=5070

    Max-Forwards: 70

    Contact: <sip:10@192.168.1.116:5070>

    To: <sip:0474412104@192.168.1.3:5060>

    From: "3CXPhone"<sip:10@192.168.1.3:5060>;tag=923d7963

    Call-ID: YjFlZWU2MTA1MGVhYWNmNWEzMTJkNWE5ZDI2NmU4NDc.

    CSeq: 2 INVITE

    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO

    Proxy-Authorization: Digest username="10",realm="3CXPhoneSystem",nonce="12876409551:39618de23dada391a18cfea858d1bd52",uri="sip:0474412104@192.168.1.3:5060",response="67dfef8912d63c864a7e78a431a0f950",algorithm=MD5

    Supported: replaces

    User-Agent: 3CX Phone 7.0.4184.0

    Content-Length: 0

    ============================

    Can you help me to resolve the problem.

    Thanks,

    Andreas
     
  2. alexmallia

    alexmallia New Member
    3CX Support

    Joined:
    Aug 4, 2008
    Messages:
    130
    Likes Received:
    0
    The problem is that the media is failing to bind due to some other application. Do you have DNS server running on this machine?

    Please check this article to see how to resolve the issue http://www.3cx.com/support/media-server.html

    regards
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. hasler

    Joined:
    Jan 7, 2009
    Messages:
    20
    Likes Received:
    0
    Hi,
    yes i have a DNS Server running on the machine (SBS 2003 server).
    I will install the 3cx phone system on a new pc with Windows XP to test.

    Thanks,

    Andreas
     
  4. hasler

    Joined:
    Jan 7, 2009
    Messages:
    20
    Likes Received:
    0
    I now installed the 3cx phone system to a xp pro machine.
    I regenerated the config file for the patton 4552 with the wizzard an imported it to the patton.
    The patton is registred in the 3cx (green led).

    I tried to make an outgoing call but the problem remains:



    22:09:20.108 [CM503008]: Call(2): Call is terminated

    22:09:20.108 [CM503015]: Call(2): Attempt to reach <sip:0474412104@192.168.1.10:5060> failed. Reason: Not Found

    22:09:20.093 [CM503004]: Call(2): Calling: Unknown:mad:[Dev]

    22:09:20.093 [CM503010]: Making route(s) to <sip:0474412104@192.168.1.10:5060>

    22:09:20.077 [CM505001]: Ext.11: Device info: Device Identified: [Man: 3CX Ltd.;Mod: 3CX VoIP Client;Rev: General] Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CX Phone 7.0.4184.0] Transport: [sip:192.168.1.10:5060]

    22:09:20.062 [CM503001]: Call(2): Incoming call from Ext.11 to <sip:0474412104@192.168.1.10:5060>


    Can somebody help me to resolve the problem.

    Thanks,

    Andreas
     
  5. William400

    William400 Well-Known Member

    Joined:
    Aug 21, 2006
    Messages:
    1,005
    Likes Received:
    0
    Hi

    Can you please enable Verbose mode and paste the full INVITE and the relative logging that shows the routing of the call.

    Please ensure you have setup your outbound rule correctly.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  6. hasler

    Joined:
    Jan 7, 2009
    Messages:
    20
    Likes Received:
    0
    Hi I can't set the verobse mode???
    I set the verbose mode and restarted the services but the the loggin mode remains on "medium"

    Thanks,

    Andreas
     
  7. alexmallia

    alexmallia New Member
    3CX Support

    Joined:
    Aug 4, 2008
    Messages:
    130
    Likes Received:
    0
    Go to the list of users of this machine and set the user ASPNET is set to be a member of the administrators group. After doing this restart IIS admin service, Reload the 3CX configuration, enable verbose and then restart the 3CX services.

    regards
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  8. hasler

    Joined:
    Jan 7, 2009
    Messages:
    20
    Likes Received:
    0
    Thanks, no it worked.

    Here the outgoing call with verbose set:


    11:51:07.643 [CM503008]: Call(3): Call is terminated

    11:51:07.628 [CM503015]: Call(3): Attempt to reach <sip:10@192.168.1.10:5060> failed. Reason: Not Registered

    11:51:07.628 [CM503015]: Call(3): Attempt to reach <sip:10@192.168.1.10:5060> failed. Reason: Not Registered

    11:51:07.628 [CM503016]: Call(3): Target is not registered: Ext:Ext.10

    11:51:07.612 [CM503010]: Making route(s) to <sip:10@192.168.1.10:5060>

    11:51:07.612 [MS210000] C:3.1:Offer received. RTP connection: 192.168.1.4:4874(4875)

    11:51:07.612 Remote SDP is set for legC:3.1

    11:51:07.596 [CM503001]: Call(3): Incoming call from 472843166@(Ln.10000@4552) to <sip:10@192.168.1.10:5060>

    11:51:07.534 [CM503012]: Inbound out-of-office hours rule (unnamed) for 10000 forwards to DN:10

    11:51:07.503 Looking for inbound target: called=474412104; caller=472843166

    11:51:07.472 [CM500002]: Info on incoming INVITE:

    INVITE sip:10000@192.168.1.10 SIP/2.0

    Via: SIP/2.0/UDP 192.168.1.4:5060;branch=z9hG4bKb823542e1

    Max-Forwards: 70

    Route: <sip:192.168.1.10;lr>

    Contact: <sip:472843166@192.168.1.4:5060>

    To: <sip:474412104@192.168.1.10>

    From: <sip:472843166@192.168.1.10>;tag=acfbc8e6937a320

    Call-ID: 7a0d11c055b13a136b0ad170b7ddd12c@192.168.1.10

    CSeq: 1314180523 INVITE

    Proxy-Authorization: Digest response="908597589eeac4900c8043ab9e1a5be4",username="10000",realm="3CXPhoneSystem",nonce="12876576667:159351244346fc827a7d01a281f62594",algorithm=MD5,uri="sip:10000@192.168.1.10"

    Supported: timer, replaces

    User-Agent: Patton SN4552 2BIS EUI MxSF v3.2.8.45 00A0BA043F63 R4.2 2007-09-19 SIP

    Content-Length: 0

    Remote-Party-ID: <sip:474412104@192.168.1.10>;party=called

    Thanks for your help,

    Andreas
     
  9. hasler

    Joined:
    Jan 7, 2009
    Messages:
    20
    Likes Received:
    0
    Hi,
    i trierd to change the outgoing rule.
    Now i do not get the error "not found", but the call doesn't go trough.
    In the log i get the following info.
    The number i call is normally reachable trough ISDN line.


    16:08:57.263 [CM503008]: Call(9): Call is terminated

    16:08:57.247 [CM503015]: Call(9): Attempt to reach <sip:0474410881@192.168.1.10;user=phone> failed. Reason: No Answer

    16:08:57.247 [CM503003]: Call(9): Call to sip:0474410881@192.168.1.4:5060 has failed; Cause: 408 Request Timeout; internal

    16:08:25.031 [MS210006] C:9.2:Offer provided. Connection(by pass mode): 192.168.1.13:59414(59415)

    16:08:25.015 [CM503004]: Call(9): Calling: Unknown:0474410881@(Ln.10000@4552)@[Dev:sip:10000@192.168.1.4:5060]

    16:08:25.000 [CM503010]: Making route(s) to <sip:0474410881@192.168.1.10;user=phone>

    16:08:25.000 [MS210000] C:9.1:Offer received. RTP connection: 192.168.1.13:59414(59415)

    16:08:25.000 Remote SDP is set for legC:9.1

    16:08:25.000 [CM505001]: Ext.12: Device info: Device Identified: [Man: Snom;Mod: 8xx series;Rev: General] Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [snom820/8.0.12] Transport: [sip:192.168.1.10:5060]

    16:08:24.984 [CM503001]: Call(9): Incoming call from Ext.12 to <sip:0474410881@192.168.1.10;user=phone>

    16:08:24.968 [CM500002]: Info on incoming INVITE:

    INVITE sip:0474410881@192.168.1.10;user=phone SIP/2.0

    Via: SIP/2.0/UDP 192.168.1.13:1025;branch=z9hG4bK-4eonpm3ixfux;rport=1024

    Max-Forwards: 70

    Contact: <sip:12@192.168.1.13:1025;line=p9b3o201>;reg-id=1

    To: <sip:0474410881@192.168.1.10;user=phone>

    From: "Büro TC"<sip:12@192.168.1.10>;tag=jo0ou8lqym

    Call-ID: 3c26e2db7452-puwhcelh49xi

    CSeq: 2 INVITE

    Session-Expires: 3600;refresher=uas

    Min-SE: 90

    Accept: application/sdp

    Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, SUBSCRIBE, PRACK, MESSAGE, INFO

    Proxy-Authorization: Digest username="12",realm="3CXPhoneSystem",nonce="12876592104:a71b6ccb8fd1fff78e73bc4a5d41635c",uri="sip:0474410881@192.168.1.10;user=phone",response="103e481931ece41ccace87636787383c",algorithm=MD5

    Supported: timer, 100rel, replaces, from-change

    User-Agent: snom820/8.0.12

    Allow-Events: talk, hold, refer, call-info

    Content-Length: 0

    P-Key-Flags: resolution="31x13", keys="4"

    Thanks,

    Andreas
     
Thread Status:
Not open for further replies.