Home » Forums » trixbox forums » Trunks
support

Inbound Caller ID on new T1

RKCMUser
Posts: 11
 Member Since:
2008-07-11
Submitted by RKCMUser on Fri, 08/01/2008 - 3:19pm.

Hi All!

I recently installed a new T1 (configured as a ESF / B8ZS with E&M wink). Hardware is a Sangoma A101. Trix is 2.6.1.

I am unable to see inbound caller IDs. Any inbounds show "Unknown" on my displays. Is there a "quick fix" to turn it on?

Please let me know. We need to have this turned up ASAP!

Thanks!

‹ Outbound CallerID Issue In from one trunk out to another ›


SkykingOH
Posts: 3534
 Member Since:
2007-12-17
There are several threads on
Fri, 08/01/2008 - 5:01pm

There are several threads on how to display inband (DTMF) caller ID. None of the fixes are easy.

Will your carrier allow you to change your change the signalling on your T1 to ISDN (PRI)?

--

Scott

aka "Skyking"



RKCMUser
Posts: 11
 Member Since:
2008-07-11
Afraid someone would say that...
Fri, 08/01/2008 - 8:11pm

Perhaps I can ask the carrier to change to a PRI, but is there a way to make it work with E&M? If so, is there someone out there that can correct it (for a fee. of course!).

PLMK!

A



SkykingOH
Posts: 3534
 Member Since:
2007-12-17
It's not the E&M it's the
Fri, 08/01/2008 - 8:52pm

It's not the E&M it's the caller ID delivered on DTMF that is the problem. There was an old thread that someone got it working. I just did a quick search and could not find the keywords.

Do you know the format they are sending the AND and CallerID?

Follow up, this is the thread I was referring to. It should give you an idea of the level of complexity.

--

Scott

aka "Skyking"



jfinstrom
Posts: 1236
 Member Since:
2007-03-07
If you want caller ID on T1
Fri, 08/01/2008 - 9:08pm

If you want caller ID on T1 you should use loop(kewl) or PRI. As a general rule no others support caller ID.

http://www.trixbox.org/forums/trixbox-forums/trunks/e-m-t1-not-ge...

http://readlist.com/lists/lists.digium.com/asterisk-users/12/6283...

http://lists.digium.com/pipermail/asterisk-users/2005-January/078...

--


Support | my after-hours blog



SkykingOH
Posts: 3534
 Member Since:
2007-12-17
James - It's not so much
Fri, 08/01/2008 - 9:18pm

James -

It's not so much the start that is the issue, you can send inband called ID with loop (immediate) or wink start trunks.

My probelm is understanding what the Zap driver does with DTMF delivered during the initial signaling of the call. If I could figure that out we could sort out the received DTMF digits and move them to the FreePBX callerID variable and all should be good.

Thoughts?

--

Scott

aka "Skyking"



jfinstrom
Posts: 1236
 Member Since:
2007-03-07
The zap driver does (drum
Fri, 08/01/2008 - 11:29pm

The zap driver does (drum roll) Nothing....

Layers:(over simplified)

----------------
ASTERISK (well its asterisk it just sort of does its thing)
----------------
CHAN_ZAP/LIBPRI (caller ID all audio processed here.)
----------------
ZAPTEL(soon DAHDI) (Audio Flow Controlled, Paths open and closed etc)
-----------------
kernel module(driver) (Audio passed through)
-----------------
Hardware (physical link, signaling)

--


Support | my after-hours blog



SkykingOH
Posts: 3534
 Member Since:
2007-12-17
Thanks James, I need to look
Sat, 08/02/2008 - 7:12am

Thanks James, I need to look at chan_zap to see what it is doing with received DTMF prior to answer.

Scott

--

Scott

aka "Skyking"



RKCMUser
Posts: 11
 Member Since:
2008-07-11
Found the problem
Sat, 10/04/2008 - 11:29am

The provider needed to turn on CallerID (they swore up and down that it was on). Once I got them on the call, Trixbox picked it up.

THANKS!



Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.