Interesting issue with # key

Discussion in '3CX Phone System - General' started by UncleScar, Aug 8, 2013.

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

    Joined:
    Aug 8, 2013
    Messages:
    4
    Likes Received:
    0
    Hello all,

    Bit of an odd one this, we have an intermittent issue with the # key even during calls it occasionally prompts us to "Please enter the number you wish to transfer this call to" however we cannot find any corresponding setting in the 3CX control panel for a feature-code etc.

    I've replicated this issue with our Granstream physical phones and the 3cx windows soft-phone.

    Here's a dump of the log file when I managed to capture the prompt(I've sanitized some of the data);

    08/08/2013 14:20:41:143 | Call from "USERNAME"<sip:209@192.168.1.10:5060;user=phone>;tag=4a9a3856fc56ca23 to <sip:%23@192.168.1.10:5060;user=phone>;tag=09258f4d
    08/08/2013 14:20:41:143 | UasSession 1681653 started
    08/08/2013 14:20:41:143 | Added leg L:C:1625.1[No endpoint yet]
    08/08/2013 14:20:41:143 | Legs count: 1
    08/08/2013 14:20:41:143 | IncomingCall: C:1625 from <sip:209@192.168.1.10:5060> to <sip:#@192.168.1.10:5060>
    08/08/2013 14:20:41:143 | Look for contact: sip:209@192.168.1.25:5060;transport=udp;user=phone
    08/08/2013 14:20:41:143 | Source endpoint: Ext.209; dev=Dev(43):[sip:209@192.168.1.25:5060;transport=udp;user=phone / 209]; disp.name=USERNAME
    08/08/2013 14:20:41:143 | Device (1010201299) is used in 1 calls: [1625]
    08/08/2013 14:20:41:143 | Outbound URI is used: sip:209@192.168.1.25:5060;transport=udp;user=phone
    08/08/2013 14:20:41:144 | MSEndpoint created
    08/08/2013 14:20:41:145 | NAT/ALG check:L:1625.1[Extn] REQUEST 'INVITE' - basic check passed. No information for extended checks

    08/08/2013 14:20:41:145 | Leg L:1625.1[Extn] has external party ID {}
    08/08/2013 14:20:41:145 | [CM503001]: Call(C:1625): Incoming call from Extn:209 to <sip:#@192.168.1.10:5060>
    08/08/2013 14:20:41:145 | [CM500002]: Call(C:1625): Info on incoming INVITE from Extn:209:
    Invite-IN Recv Req INVITE from 192.168.1.25:5060 tid=181d54008a42f442 Call-ID=93da659461942971@192.168.1.25:
    INVITE sip:%23@192.168.1.10:5060;user=phone SIP/2.0
    Via: SIP/2.0/UDP 192.168.1.25:5060;branch=z9hG4bK181d54008a42f442
    Max-Forwards: 70
    Contact: <sip:209@192.168.1.25:5060;transport=udp;user=phone>
    To: <sip:%23@192.168.1.10:5060;user=phone>
    From: "USERNAME"<sip:209@192.168.1.10:5060;user=phone>;tag=4a9a3856fc56ca23
    Call-ID: 93da659461942971@192.168.1.25
    CSeq: 21546 INVITE
    Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, OPTIONS, INFO, SUBSCRIBE, UPDATE, PRACK, MESSAGE
    Content-Type: application/sdp
    Proxy-Authorization: Digest username="209",realm="3CXPhoneSystem",algorithm=MD5,uri="sip:%23@192.168.1.10:5060;user=phone",nonce="414d535c08142c2897:0edf7c8082249dff540e232c71dc9382",response="3bc0476e13f2aa3491c5edcc5bceb039"
    Supported: replaces, timer, path
    User-Agent: Grandstream GXP2020 1.2.5.3
    Content-Length: 379
    X-Grandstream-PBX: true
    P-Early-Media: Supported

    v=0
    o=209 8000 8001 IN IP4 192.168.1.25
    s=SIP Call
    c=IN IP4 192.168.1.25
    t=0 0
    m=audio 5014 RTP/AVP 0 8 18 97 2 4 3 101
    a=sendrecv
    a=rtpmap:0 PCMU/8000
    a=rtpmap:8 PCMA/8000
    a=rtpmap:18 G729/8000
    a=rtpmap:97 iLBC/8000
    a=fmtp:97 mode=20
    a=rtpmap:2 G726-32/8000
    a=rtpmap:4 G723/8000
    a=rtpmap:3 GSM/8000
    a=ptime:20
    a=rtpmap:101 telephone-event/8000
    a=fmtp:101 0-11

    08/08/2013 14:20:41:145 | StatusNotification: SE:1625.1{Calling}; Skip=0
    08/08/2013 14:20:41:145 | Issue: [Pres:209; act=Alerting;0;836670]
    08/08/2013 14:20:41:145 | Reported(Insert): SE:1625.1{Calling}
    08/08/2013 14:20:41:146 | Inbound DID: ''; Phonebook Name: ''
    08/08/2013 14:20:41:146 | [CM505001]: Endpoint Extn:209: Device info: Device Identified: [Man: Grandstream;Mod: GXP Series;Rev: General] Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Grandstream GXP2020 1.2.5.3] PBX contact: [sip:209@192.168.1.10:5060]
    08/08/2013 14:20:41:146 | OnOffer from "USERNAME"<sip:209@192.168.1.10:5060;user=phone>;tag=4a9a3856fc56ca23
    08/08/2013 14:20:41:146 | Remote SDP is set for leg L:1625.1[Extn]
    08/08/2013 14:20:41:146 | Call(C:1625): Invite
    08/08/2013 14:20:41:146 | SelectRouteReq
    08/08/2013 14:20:41:146 | [CM503010]: Call(C:1625): Making route(s) from Extn:209 to <sip:#@192.168.1.10:5060>
    08/08/2013 14:20:41:146 | [Flow] Building target endpoint to # from "USERNAME" <sip:209@192.168.1.10:5060>
    08/08/2013 14:20:41:146 | Looking for outbound rule: dialed = [#], processed: [#]; from-ext:
    08/08/2013 14:20:41:146 | Rule EM_No_999: mask=999; exts=; prior=5; numlen=3; type=0; from: 209
    08/08/2013 14:20:41:146 | Rule EM_No_112: mask=112; exts=; prior=10; numlen=3; type=0; from: 209
    08/08/2013 14:20:41:146 | Rule EM_No_101: mask=101; exts=; prior=15; numlen=3; type=0; from: 209
    08/08/2013 14:20:41:146 | Rule Rule for Outbound: mask=0; exts=; prior=20; numlen=; type=0; from: 209
    08/08/2013 14:20:41:146 | Rule Voipfone: mask=9; exts=; prior=25; numlen=; type=0; from: 209
    08/08/2013 14:20:41:146 | Rule Rule for Grandstream_GXW4104: mask=7; exts=; prior=31; numlen=; type=0; from: 209
    08/08/2013 14:20:41:146 | [Flow] Target endpoint for # can not be built!
    08/08/2013 14:20:41:146 | Call(C:1625): from Extn:209 to # doesn't match any outbound rule. No outbound rule could be selected.
    08/08/2013 14:20:41:146 | [CM503014]: Call(C:1625): No known route from Extn:209 to target: <sip:#@192.168.1.10:5060>
    08/08/2013 14:20:41:146 | [CM503016]: Call(C:1625): Attempt to reach <sip:#@192.168.1.10:5060> from Extn:209 has failed. Reason: Not Found
    08/08/2013 14:20:41:146 | [CM503020]: Call(C:1625): Normal call termination. Call originator: Extn:209. Reason: Not found
    08/08/2013 14:20:41:146 | StatusNotification: SE:1625.1{OnHook}; Skip=0
    08/08/2013 14:20:41:146 | Issue: [Pres:209; act=Open;0;836671]
    08/08/2013 14:20:41:146 | Reported(Delete): SE:1625.1{OnHook}
    08/08/2013 14:20:41:148 | Call(C:1625) is terminated
    08/08/2013 14:20:41:193 | SendMsg from <sip:%23@192.168.1.10:5060;user=phone>;tag=09258f4d to "USERNAME"<sip:209@192.168.1.10:5060;user=phone>;tag=4a9a3856fc56ca23
    08/08/2013 14:20:41:193 | Notify dialog-info: Extn:209: sip:209@192.168.1.25:5060;transport=udp;user=phone, Call(C:1625)
    08/08/2013 14:20:41:193 | Call(C:1625): DlgID:1625-2303, entry state: 0
    08/08/2013 14:20:41:193 | Call(C:1625): DlgID:1625-2303, exit state: 3
    08/08/2013 14:20:41:193 | L:1625.1[Extn] Sending: OnSendResp Send 404/INVITE from 0.0.0.0:0 tid=181d54008a42f442 Call-ID=93da659461942971@192.168.1.25:
    SIP/2.0 404 Not Found
    Via: SIP/2.0/UDP 192.168.1.25:5060;branch=z9hG4bK181d54008a42f442
    To: <sip:%23@192.168.1.10:5060;user=phone>;tag=09258f4d
    From: "USERNAME"<sip:209@192.168.1.10:5060;user=phone>;tag=4a9a3856fc56ca23
    Call-ID: 93da659461942971@192.168.1.25
    CSeq: 21546 INVITE
    Warning: 499 SERVER.local "Not found"
    Content-Length: 0


    08/08/2013 14:20:41:193 | Terminated from "USERNAME"<sip:209@192.168.1.10:5060;user=phone>;tag=4a9a3856fc56ca23 to <sip:%23@192.168.1.10:5060;user=phone>;tag=09258f4d; reason: Rejected
     
  2. UncleScar

    Joined:
    Aug 8, 2013
    Messages:
    4
    Likes Received:
    0
    Surely we can't be the only people experiencing this issue?
    It's an essentially stock install and it happens across a variety of devices, while not resulting in a loss of service it is incredibly infuriating.
     
  3. eQDoBBs

    Joined:
    Aug 14, 2012
    Messages:
    37
    Likes Received:
    3
    Does no-one experience this issue?

    When you make a call and an auto receptionist answers with a menu of options and asks for you to press # to confirm an input we get this response from 3CX server.
     
  4. SY

    SY Well-Known Member
    3CX Support

    Joined:
    Jan 26, 2007
    Messages:
    1,825
    Likes Received:
    2
    Log says that the request to make a call to "#" is coming to PBX. PBX rejects it without any interactions.
    User-Agent is specified as "Grandstream GXP2020 1.2.5.3". Address of the device - 192.168.1.25
    Does this problem appear if call is initiated by other phones or coming from external lines (PSTN/Voip providers)?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. UncleScar

    Joined:
    Aug 8, 2013
    Messages:
    4
    Likes Received:
    0
    SY,

    This problem occurs regardless of device used.
    We've used multiple handsets and soft-phones and we still encounter the issue.
     
  6. SY

    SY Well-Known Member
    3CX Support

    Joined:
    Jan 26, 2007
    Messages:
    1,825
    Likes Received:
    2
    UncleScar and eQDoBBs

    Could you please report this issue to 3cx support team?
    It is a kind of mystery and it is very interesting to find an entity which is able to say: "Please enter the number you wish to transfer this call to" - when you press '#'...
    3CX Phone System never tells this phrase. So, it is, really, the "INTERESTING ISSUE WITH # KEY"

    Thanks
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  7. craigreilly

    craigreilly Well-Known Member

    Joined:
    Feb 1, 2012
    Messages:
    2,947
    Likes Received:
    178
    Is a gateway in use?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
Thread Status:
Not open for further replies.