DID's CID only shows main or "trunk" line

Discussion in '3CX Phone System - General' started by fujiconsulting, Jul 23, 2012.

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

    Joined:
    Mar 17, 2009
    Messages:
    3
    Likes Received:
    0
    I cannot get the CID to reflect the DID dialed when forwarding a call. I am running V11 and i have a Sangoma A101 T1 card installed. When placing a call to any of the DID's, the CID displays the main line only. I have checked with my local Telco and they are in fact sending the DID's (well the last four digits) so i should by all accounts be seeing the actual DID dialed and not the trunk. From what i have found and read, it should be as easy as making a change in one of the From: fields in the Outbound Parameters section of the outbound gateway. Now i have been working with Sangoma support for over a month now and this is what i have gotten from them:

    "I had a look over all of these logs and you are not sending out the DID number when you push the call out, you are only sending out the called number and not the calling (DID). So you should be setting the calling or caller id or did in full, so put all the digits for the number and not just the last 4 and send this out when you push the call out the PRI.

    This has to be configured from the 3CX side. If you need any help with this 3CX will be able to assist you with this.

    Now once this is done if you are certain you are pushing the DID/caller id to us then send us the same logs again and we'll have a look over them for you."

    This is the output from the server itself when placing a call to be forwarded to another number:

    "To: "2606"<sip:2606@192.168.200.16:5060>;tag=a137bd3c
    From: "ALASKA DIGITEL "<sip:907*****62@127.0.0.1:5066>;tag=pxip-callid-1343025980-470947-9961-179ds-7983-e307c200
    Call-ID: 1c905407-d492-11e1-b5ef-9074ccc2bf3f@LWV-VPSRV
    CSeq: 18007 CANCEL
    Content-Length: 0
    22-07-2012 22:46:21.926 L:8.2[Line:10014>>6323854] got Early-Media EarlyMedia Recv 180/INVITE from 127.0.0.1:5066 tid=1c5837247d431d5d Call-ID=ODkwMTMxNDViZmU3YzU2ZTMxODc1YzdlOTI4MTk1MGU.:
    SIP/2.0 180 Ringing
    Via: SIP/2.0/UDP 127.0.0.1:5060;branch=z9hG4bK-d8754z-1c5837247d431d5d-1---d8754z-;rport=5060
    Contact: <sip:NetborderExpressGateway@127.0.0.1:5066;transport=udp>
    To: <sip:*****54@127.0.0.1:5066>;tag=ds-99-e3098737
    From: "ALASKA DIGITEL "<sip:10014@127.0.0.1:5066>;tag=274fcc51
    Call-ID: ODkwMTMxNDViZmU3YzU2ZTMxODc1YzdlOTI4MTk1MGU."

    Now, the above output is where i think the problem is. It shows the call as being routed correctly, but from what i understood from the conversation with the support tech at Sangoma was that the port ID of 10014, is what is being sent for CID from 3CX but i'm not entirely sure. If anyone could offer me some advice on how to solve this i would greatly appreciate it.
     
  2. fujiconsulting

    Joined:
    Mar 17, 2009
    Messages:
    3
    Likes Received:
    0
    Update:
    PLEASE HELP!!!!

    Ok, I can see the number of the DID in the server activity log (I set it in the inbound rule name), but when the call is forwarded the CID still shows up and the main truck line (10014 in the logs, but I am assuming the gateway pulls the number because I don't have it set anywhere). Sangoma support suggested I change the Contact : User Part sip field:
    "In order to accomplish what you'd like, you need to ensure that the "Contact" header 'User Part' of the SIP Invite from your PBX -> NBE on the third leg of the call contains the DID of the original inbound call (i.e. the ***-2606) number which was originally dialed.
    Please let me know if you are having any problems accomplishing this.
    Thanks."

    I have had no luck and I’m sure they are going to refer me back to 3CX support so I’m hoping you guys can help. Below is the output from the server activity log. I have masked all but the last four digits of the numbers. The DID dialed ends in 2602 and the call was placed from ******7478. As you can see, the call is supposed to be forwarded to ***3854. The call goes thru just fine but when the call connects, the main trunk line is presented (10014 is presented as the dev hence the CID of that line showing up). Am I fighting a losing battle????
     

    Attached Files:

Thread Status:
Not open for further replies.