# Setting up callcentric extension as an inbound trunk **URL:** \ **Category:** VitalPBX\ **Created:** [March 2, 2023, 4:50pm UTC](https://forums.vitalpbx.org/t/setting-up-callcentric-extension-as-an-inbound-trunk/2446 "2023-03-02T16:50:22Z")\ **Posts on this page:** 16\ **Page:** 1
**Author:** ![UTS\_Brian](https://forums.vitalpbx.org/user_avatar/forums.vitalpbx.org/uts_brian/32/674_2.png) [@UTS\_Brian](https://forums.vitalpbx.org/u/UTS_Brian)\ **Post date:** [March 2, 2023, 4:50pm UTC](https://forums.vitalpbx.org/t/setting-up-callcentric-extension-as-an-inbound-trunk/2446/1 "2023-03-02T16:50:22Z")
I have a client who is the regional reseller for a specific product, as part of being the reseller they get a VOIP extension that is advertised by the product vendor. This extension comes from CallCentric and as we move them to Vital PBX from their previous PBX we have been unable to get this set up as a trunk even though it worked fine in the old PBX so we know it’s possible. We have tried our best to use the instructions for setup found at this link [https://www.callcentric.com/support/device/vitalpbx](https://www.callcentric.com/support/device/vitalpbx) but it is for version 2 of VitalPBX so not everything lines up. Does anyone have this working on version 3 that can provide us some guidance? ---
**Author:** ![miguel](https://forums.vitalpbx.org/user_avatar/forums.vitalpbx.org/miguel/32/415_2.png) [@miguel](https://forums.vitalpbx.org/u/miguel)\ **Post date:** [March 2, 2023, 5:27pm UTC](https://forums.vitalpbx.org/t/setting-up-callcentric-extension-as-an-inbound-trunk/2446/2 "2023-03-02T17:27:19Z")
I recommend you use PJSIP and translate this vanilla configuration to VitalPBX GUI. [https://www.callcentric.com/support/device/asterisk/17\_pjsip](https://www.callcentric.com/support/device/asterisk/17_pjsip) ---
**Author:** ![UTS\_Brian](https://forums.vitalpbx.org/user_avatar/forums.vitalpbx.org/uts_brian/32/674_2.png) [@UTS\_Brian](https://forums.vitalpbx.org/u/UTS_Brian)\ **Post date:** [March 2, 2023, 5:40pm UTC](https://forums.vitalpbx.org/t/setting-up-callcentric-extension-as-an-inbound-trunk/2446/3 "2023-03-02T17:40:33Z")
Ok did that and am pretty much at the same spot, reports shows it is registered, but the phone rings and the CallCentric voicemail ends up eventually picking up. ---
**Author:** ![miguel](https://forums.vitalpbx.org/user_avatar/forums.vitalpbx.org/miguel/32/415_2.png) [@miguel](https://forums.vitalpbx.org/u/miguel)\ **Post date:** [March 2, 2023, 5:42pm UTC](https://forums.vitalpbx.org/t/setting-up-callcentric-extension-as-an-inbound-trunk/2446/4 "2023-03-02T17:42:33Z")
Are you making outbound or incoming calls? Have you analyzed the traffic using SNGREP? ---
**Author:** ![UTS\_Brian](https://forums.vitalpbx.org/user_avatar/forums.vitalpbx.org/uts_brian/32/674_2.png) [@UTS\_Brian](https://forums.vitalpbx.org/u/UTS_Brian)\ **Post date:** [March 2, 2023, 5:51pm UTC](https://forums.vitalpbx.org/t/setting-up-callcentric-extension-as-an-inbound-trunk/2446/5 "2023-03-02T17:51:45Z")
Inbound, Not familiar with SNGREP but I’ll look into it. ---
**Author:** ![miguel](https://forums.vitalpbx.org/user_avatar/forums.vitalpbx.org/miguel/32/415_2.png) [@miguel](https://forums.vitalpbx.org/u/miguel)\ **Post date:** [March 2, 2023, 5:54pm UTC](https://forums.vitalpbx.org/t/setting-up-callcentric-extension-as-an-inbound-trunk/2446/6 "2023-03-02T17:54:24Z")
Do the following: Execute the command below and then place the incoming call. You should see the incoming request arriving at your PBX. ```bash sngrep -c -r ``` Here’s a video about this tool. [![](https://forums.vitalpbx.org/uploads/default/original/2X/d/dc0bbdda9c06a926fb1ddf91d8817977fac3e397.jpeg "Monitor your SIP/PJSIP activity with SNGrep on VitalPBX") ](https://www.youtube.com/watch?v=8FnC7ihHDuI) ---
**Author:** ![UTS\_Brian](https://forums.vitalpbx.org/user_avatar/forums.vitalpbx.org/uts_brian/32/674_2.png) [@UTS\_Brian](https://forums.vitalpbx.org/u/UTS_Brian)\ **Post date:** [March 2, 2023, 6:08pm UTC](https://forums.vitalpbx.org/t/setting-up-callcentric-extension-as-an-inbound-trunk/2446/7 "2023-03-02T18:08:55Z")
OK here is the output, the call originated from another tennant on the same PBX so that is the first line, next one I assume is the call coming in, and the final REJECTED is probably my issue if I am reading this correctly? (I’ve fudged the IPs and Numbers) [] 3582 INVITE utso101@pbx1.utsoperator.c 12355302555@pbx1.utsopera 6 23.34.89.109:36274 209.159.192.50:5060 CALL SETUP [] 3588 INVITE [17755397555@209.151.192.2](mailto:17755397555@209.151.192.2) 12355302555@us-east-va.si 7 209.159.192.50:5060 34.56.36.35:5060 CALL SETUP [] 3606 INVITE 17755397555@sip.callcentr 12355302555@callcentric.c 3 123.87.123.67:5060 209.159.192.50:5060 REJECTED ---
**Author:** ![miguel](https://forums.vitalpbx.org/user_avatar/forums.vitalpbx.org/miguel/32/415_2.png) [@miguel](https://forums.vitalpbx.org/u/miguel)\ **Post date:** [March 2, 2023, 6:10pm UTC](https://forums.vitalpbx.org/t/setting-up-callcentric-extension-as-an-inbound-trunk/2446/8 "2023-03-02T18:10:20Z")
Is PJSIP running on port 5060? Would you mind sharing your trunk configurations? Remember to hide any sensitive information. ---
**Author:** ![UTS\_Brian](https://forums.vitalpbx.org/user_avatar/forums.vitalpbx.org/uts_brian/32/674_2.png) [@UTS\_Brian](https://forums.vitalpbx.org/u/UTS_Brian)\ **Post date:** [March 2, 2023, 6:16pm UTC](https://forums.vitalpbx.org/t/setting-up-callcentric-extension-as-an-inbound-trunk/2446/9 "2023-03-02T18:16:29Z")
Ignore the fact it is disabled, I enable it when testing and then switch it back to their old PBX as it is a live number. ![OIR_T_1](https://forums.vitalpbx.org/uploads/default/original/2X/b/bfc0438bc45b469b363c1c11b207cb3671f07baf.jpeg) ![OIR_T_2](https://forums.vitalpbx.org/uploads/default/original/2X/6/6fb812ddfa0b7a23c65008f24df3562fe6f86bb4.jpeg) ---
**Author:** ![PitzKey](https://forums.vitalpbx.org/user_avatar/forums.vitalpbx.org/pitzkey/32/420_2.png) [@PitzKey](https://forums.vitalpbx.org/u/PitzKey)\ **Post date:** [March 2, 2023, 6:17pm UTC](https://forums.vitalpbx.org/t/setting-up-callcentric-extension-as-an-inbound-trunk/2446/10 "2023-03-02T18:17:08Z")
The Asterisk log along with PJSIP debugging enabled will show you whats up. ---
**Author:** ![miguel](https://forums.vitalpbx.org/user_avatar/forums.vitalpbx.org/miguel/32/415_2.png) [@miguel](https://forums.vitalpbx.org/u/miguel)\ **Post date:** [March 2, 2023, 6:22pm UTC](https://forums.vitalpbx.org/t/setting-up-callcentric-extension-as-an-inbound-trunk/2446/11 "2023-03-02T18:22:22Z")
My observations: - **Contacts:** Should be empty - **Client URI:** [sip:1777MYCCID@sip.callcentric.net](mailto:sip:1777MYCCID@sip.callcentric.net) - **Server URI:** sip:sip.callcentric.net - **Contact User:** 1777MYCCID ---
**Author:** ![UTS\_Brian](https://forums.vitalpbx.org/user_avatar/forums.vitalpbx.org/uts_brian/32/674_2.png) [@UTS\_Brian](https://forums.vitalpbx.org/u/UTS_Brian)\ **Post date:** [March 2, 2023, 6:37pm UTC](https://forums.vitalpbx.org/t/setting-up-callcentric-extension-as-an-inbound-trunk/2446/12 "2023-03-02T18:37:23Z")
> [@miguel](#): > > - **Client URI:** [sip:1777MYCCID@sip.callcentric.net](mailto:sip:1777MYCCID@sip.callcentric.net) > - **Server URI:** sip:sip.callcentric.net > - **Contact User:** 1777MYCCID I tried these and it would no longer register at all, but I changed 1777MYCCID to 1777MYCCIDEXT on Client URI and Contact User and it now works. Thanks! ---
**Author:** ![miguel](https://forums.vitalpbx.org/user_avatar/forums.vitalpbx.org/miguel/32/415_2.png) [@miguel](https://forums.vitalpbx.org/u/miguel)\ **Post date:** [March 2, 2023, 6:41pm UTC](https://forums.vitalpbx.org/t/setting-up-callcentric-extension-as-an-inbound-trunk/2446/13 "2023-03-02T18:41:22Z")
> [@UTS\_Brian](#): > > I tried these and it would no longer register at all, but I changed 1777MYCCID to 1777MYCCIDEXT on Client URI and Contact User and it now works. I guess they explain that in their documentation: > **NOTE:** Any instance of **1777MYCCID** should be replaced with the 1777 number assigned to you by Callcentric. **EXT** is the three digit extension you are trying to register this UA to. > For example, 17770001234101 would register to extension 101 on account 17770001234. However, if you are registering towards the main/default extension of your Callcentric Account (extension 100), you can simply use your 1777 number _without_ the 3 digit extension suffix (example: 17770001234). You CANNOT register to your Callcentric Account by only using the extension number; the full 1777 number ALWAYS needs to be included. ---
**Author:** ![grand\_total](https://forums.vitalpbx.org/letter_avatar_proxy/v4/letter/g/779978/32.png) [@grand\_total](https://forums.vitalpbx.org/u/grand_total)\ **Post date:** [March 2, 2023, 7:45pm UTC](https://forums.vitalpbx.org/t/setting-up-callcentric-extension-as-an-inbound-trunk/2446/16 "2023-03-02T19:45:01Z")
> [@miguel](#): > > `sngrep -c -r` Such a useful tool, thanks for mentioning it, I’ve never heard of it before. ---
**Author:** ![UTS\_Brian](https://forums.vitalpbx.org/user_avatar/forums.vitalpbx.org/uts_brian/32/674_2.png) [@UTS\_Brian](https://forums.vitalpbx.org/u/UTS_Brian)\ **Post date:** [March 23, 2023, 2:02pm UTC](https://forums.vitalpbx.org/t/setting-up-callcentric-extension-as-an-inbound-trunk/2446/17 "2023-03-23T14:02:01Z")
Ok so this got very weird… If we call the Callcentric number and they answer they can’t hear the caller but the caller can hear them. Of course you’re going to say it’s a NAT issue EXCEPT they can hear the caller on all other lines which are through Flowroute. So that rules out the PBX to the phones and it must be the trunk right? BUT if we set up a test phone in our office we can hear the caller when we make a test call. So you would think that rules out the trunk to the PBX. We are at a loss of what could cause the issue. ---
**Author:** ![system](https://forums.vitalpbx.org/uploads/default/original/1X/672b458a1d454755270c2c16adc5316b641c3c6a.png) [@system](https://forums.vitalpbx.org/u/system)\ **Post date:** [April 22, 2023, 2:02pm UTC](https://forums.vitalpbx.org/t/setting-up-callcentric-extension-as-an-inbound-trunk/2446/18 "2023-04-22T14:02:36Z")
Closed on April 22, 2023, 2:02pm UTC This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.