Hidden carrier configuration

[jkidd]

Hi team,

I'm helping a client setup with a new carrier. They want to blend their old carrier with a new one.

When I look in the carrier setup, there is only one carrier that is inactive. The dial prefix refers to a carrier I can't see. I've posted the asterisk log when placing a call. Can anyone explain what is going on in the background?

Also, I should note the OLD carrier is a SIM GSM dialler, so not sure if it's related to that device being used rather than a normal SIP trunk over a data link.

Code: Select all

[Jun 16 22:51:12]     -- Executing [59110422394070@default:1] AGI("Local/59110422394070@default-0004881c;2", "agi://127.0.0.1:4577/call_log") in new stack
[Jun 16 22:51:12]     -- AGI Script Executing Application: (EXEC) Options: (Set(_CAMPCUST=COLDLEAD))
[Jun 16 22:51:12]     -- <Local/59110422394070@default-0004881c;2>AGI Script agi://127.0.0.1:4577/call_log completed, returning 0
[Jun 16 22:51:12]     -- Executing [59110422394070@default:2] Dial("Local/59110422394070@default-0004881c;2", "DAHDI/R0/0422394070,,tTO") in new stack
[Jun 16 22:51:12]     -- Setting operator services mode to 1.
[Jun 16 22:51:12] DEBUG[7054]: sig_pri.c:1016 sig_pri_request: sig_pri_request 5
[Jun 16 22:51:12] DEBUG[7054]: sig_pri.c:6605 sig_pri_call: CALLER NAME: V6162251120002297123 NUM: 5164536886
[Jun 16 22:51:12]     -- Requested transfer capability: 0x00 - SPEECH
[Jun 16 22:51:12]     -- Called DAHDI/R0/0422394070
[Jun 16 22:51:16]     -- DAHDI/i1/0422394070-25445 is proceeding passing it to Local/59110422394070@default-0004881c;2
[Jun 16 22:51:16]     -- DAHDI/i1/0422394070-25445 is making progress passing it to Local/59110422394070@default-0004881c;2
[Jun 16 22:51:23]     -- DAHDI/i1/0422394070-25445 is ringing


Client Config

vicidial-2.9.441a-140612.1628.2.go
asterisk version: 1.8.23.0
8 core Intel(R) Xeon(R) CPU E5520
16 GIG RAM
OS - centos5

[williamconley]

1) Please post your installation method (yep, this could well be related in this case ... but you should always post it even if that's not the case). A link to the instructions used, or the name/version of the Distro if something like GoAutoDial X.X.

2) Have a look in the extensions.conf and any .conf files that contain the word "extensions" and any ".conf" files mentioned in the extensions.conf file as being "included".

3) PRI is a specialized installation, but the dialplan entry for it can still be removed from the hard-coded files ("extensions.conf" et. al) and placed in a carrier under Admin->Carriers for blending with SIP and IAX accounts. Just be sure to DUPE exactly what's there first, and make that work exactly the same way ... THEN begin making changes

4) and be sure to save what you had working ... along with the original .conf files (all of them! Be Safe!)

Happy Hunting!

[jkidd]

Thanks William! It was setup by another team and I"m just picking up the pieces after they failed to support them so I'm not sure how they installed it.

I think you are onto something with PRI config as it's using a GSM gateway via an E1 card.

Thanks again, really appreciate this forum and the support

[williamconley]

It was setup by another team and I"m just picking up the pieces after they failed to support them so I'm not sure how they installed it.

The splash screen (or "MOTD" for you techies) when you log in via ssh will often contain the version of the installer, or at least a Hint at the distro. Putting in your OS and Version would also be useful if that's not present.

Typing "history" at the CLI and SAVING the result to a text file may one day come in very handy (once it's gone ... it's gone). That is the footprint/tracks of the user who performed the install unless they were hiding the evidence.