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.


Discussion in '3CX Phone System - General' started by ivan308, May 9, 2011.

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

    May 9, 2011
    Likes Received:
    With the default Inbound Parameters I have an issue with Inbound Caller ID with Unknown Name and Unknown Number showing on the analog phone display connected to a Grandstream HT-268 and 5060;nf=e showing up on X-lite 4.

    I was able to get CallerName to show the number by setting P-Asserted Identity : User Part to CallerName and it appears as +1321xxxxxxx. Still get Unknown Number showing so it looks like the system is only populating CallerName and not CallerNum.

    Could it be because there is a + before the number and hence cannot be populated into a numeric field ?

    VOIP provider is Flowroute.

    Please see below for verbose log of call.

    Is there anyway to debug and see the value of variables ?

    23:27:39.441  Currently active calls - 1: [38]
    23:27:38.994  [CM503025]: Call(38): Calling Ext:Ext.5150@[Dev:sip:5150@]
    23:27:38.990  [MS210002] C:38.2:Offer provided. Connection(transcoding mode):
    23:27:38.908  [CM503004]: Call(38): Route 1: Ext:Ext.5150@[Dev:sip:5150@]
    23:27:38.906  [CM503010]: Making route(s) to <sip:5150@>
    23:27:38.905  [MS210000] C:38.1:Offer received. RTP connection:
    23:27:38.902  Remote SDP is set for legC:38.1
    23:27:38.901  [CM505003]: Provider:[FlowRoute] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [] PBX contact: [sip:58517501@]
    23:27:38.887  [CM503001]: Call(38): Incoming call from +13214800086@(Ln.10003@FlowRoute) to <sip:5150@>
    23:27:38.799  [CM503012]: Inbound any hours rule (*) for 10003 forwards to DN:5150
    23:27:38.798  Looking for inbound target: called=+13216043023; caller=+13214800086
    23:27:38.793  [CM500002]: Info on incoming INVITE:
      INVITE sip:13216043023@ SIP/2.0
      Via: SIP/2.0/UDP;branch=z9hG4bKaeda.509776d0495dfb7d6a9c0a6069fac054.0
      Via: SIP/2.0/UDP;branch=z9hG4bKaeda.c65f2305609bd0634567c4ae1c2b3fa4.0
      Via: SIP/2.0/UDP;branch=z9hG4bKaeda.4a737d8b85181dcca657981aa718cb1c.0
      Via: SIP/2.0/UDP;branch=z9hG4bK0bB92aa1d9fa5e086dd
      Max-Forwards: 90
      Record-Route: <sip:;lr>
      Record-Route: <sip:;lr>
      Contact: <sip:+13214800086@>
      To: <sip:+13216043023@>
      From: <sip:+13214800086@>;tag=gK0b14ecdb
      Call-ID: 1678476564_109103228@
      CSeq: 16968 INVITE
      Accept: application/sdp, application/isup, application/dtmf, application/dtmf-relay, multipart/mixed
      P-Asserted-Identity: <sip:+13214800086@pstn>
      Content-Length: 0
    23:27:09.429  Currently active calls [none]
  2. archie

    archie Well-Known Member
    3CX Support

    Aug 18, 2006
    Likes Received:
    Re: Inbund Caller ID Issue

    Yes, '+' can be an issue. Enable E.164 preprocessing to eliminate it.
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
Thread Status:
Not open for further replies.