Hello, I am using Elastix 126.96.36.199 with FreePBX 188.8.131.52. I have 4 trunks from various different providers. The issue i am facing is that when i get an incoming call through any of the trunk on the DID's (traditional numbers) that i have purchased from them, the destination comes up as "s". It does not show me the actual DID number through with the call came. I have tried numbers from Ozetell, Pennytel and some other providers but i get the same result. i mean the "Destination" shown in reports (which should be the DID through which the call came). The caller ID for a call comes up fine under source. So it displayes the right number under source in the same report but the "Destination" shows "s". Due to the above issue i am unable to land calls to different numbers on different destinations. I can only receive calls to one destination by setting up the incoming route to "Any DID/ Any CID". If i delete the "Any DID/ Any CID" route and just leave the route for the actual DID then i get a message that the number you have dialed is not in service". <b>Here are my configs:</b> <b> Pennytel </b> <b> PEER Details: </b> disallow=all allow=alaw&ulaw&gsm&g729 canredirect=no canreinvite=no host=sip.pennytel.com insecure=very secret=XXXXXXXXXXXX type=peer username=888XXXXXXX <b> User Context </b> 888XXXXXXX <b> User Details </b> canreinvite=no context=from-trunk fromuser=888XXXXXXX qualify=no secret=XXXXXXXXXX type=user username=888XXXXXXX <b>Registration String:</b> 888XXXXXXX:XXXXXXXXXXXX@sip.pennytel.com/888XXXXXXX <b> Oztell </b> <b> PEER Details: </b> disallow=all allow=ulaw&alaw canredirect=no dtmfmode=rfc2833 fromuser=899060xxxxx host= sip.syd.net2max.com insecure=very username=899060XXXXX secret=Password type=peer <b> User Context </b> 899060XXXXX <b> User Details </b> canreinvite=no context=from-trunk fromuser=899060XXXXX insecure=very qualify=no secret=Password type=user username=899060XXXXX <b>Registration String:</b> 899060XXXXXassword@sip.syd.net2max.com/899060XXXXX Can anyone please advise or suggest what can be done to fix the above issue?