cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
curtc
New Contributor

908 inbound caller ID not working

Jump to solution

Hello,

I've got a 908 connecting to a SIP trunk carrier and 6 analog lines to the PBX.  All works OK but There is no inbound caller ID where I know the carrier is sending it for other native SIP trunks.  I've got to be doing something wrong in the Adtran.  Can someone assist?

Thanks!

voice trunk T01 type sip

  match dnis "NXX-NXX-XXXX" substitute "1-NXX-NXX-XXXX"

  match dnis "011$" substitute "$"

  sip-server primary gw1.SIP.Carrier

  sip-server secondary gw2.SIP.Carrier

 

!

!

voice grouped-trunk SIP

  trunk T01

  accept $ cost 0

!

!

voice user 10001

  connect fxs 0/1

  no cos

  password encrypted "4145659f5fe924b3de59c00a79337ee"

  sip-authentication password encrypted "4145659adcfe924b3de59c00a79337ee"

!

!

!

voice user 10002

  connect fxs 0/2

  no cos

  password encrypted "4145659f50aadcfb3de59c00a79337ee"

  sip-authentication password encrypted "3135e1c931c586b963c832c6893169202"

!

!

!

voice user 10003

  connect fxs 0/3

  no cos

  password encrypted "2c28de028117529157565b9b766ed74"

  sip-authentication password encrypted "1410d98cc28d33d16eaa509eb5aef8ed3"

!

!

!

voice user 10004

  connect fxs 0/4

  no cos

  password encrypted "3f3b802c6899a4539120dbd1042cd80022"

  sip-authentication password encrypted "3034d300a227d973efc7fb1c319c1eec"

!

!

!

voice user 10005

  connect fxs 0/5

  no cos

  password encrypted "292d291c308f6d48be17ad71b507967cd"

  sip-authentication password encrypted "353137ad172c81782ec3266d6bc6f99f"

!

!

!

voice user 10006

  connect fxs 0/6

  no cos

  password encrypted "4642275d03ad2627ceb8fe320bf9b29"

  sip-authentication password encrypted "3135e1c7f186b963c832c6893169202"

!

!

voice ring-group 20002

  type linear

  num-rings 0

  member 10002

  login-member 10002

!

!

voice ring-group 20003

  type linear

  num-rings 0

  member 10003

  login-member 10003

!

!

voice ring-group 20004

  type linear

  num-rings 0

  member 10004

  login-member 10004

!

!

voice ring-group 20005

  type linear

  num-rings 0

  member 10005

  login-member 10005

!

!

voice ring-group 20006

  type linear

  num-rings 0

  member 10006

  login-member 10006

!

!

voice ring-group 14185555555

  type linear

  description MainInboundNumber

  num-rings 0

  member 10001

  login-member 10001

  coverage  internal 20002

  coverage  internal 20003

  coverage  internal 20004

  coverage  internal 20005

  coverage  internal 20006

0 Kudos
1 Solution

Accepted Solutions
Anonymous
Not applicable

Re: 908 inbound caller ID not working

Jump to solution

Curt,

It should be on by default.

Try using this debug command and see what the output is on an inbound call.

# debug voice toneservices

Sample debug with caller-id

13:41:46.486 TONESERVICES.EVENTS fxs 0/2 - empty - Caller-ID Generation: Request resource

13:41:46.487 TONESERVICES.EVENTS fxs 0/2 - Dsp 0/1.1 - Caller-ID Generation: DSP channel allocated for the resource

13:41:46.487 TONESERVICES.EVENTS fxs 0/2 - Dsp 0/1.1 - Caller-ID Generation: constructed

13:41:49.034 TONESERVICES.EVENTS fxs 0/2 - Dsp 0/1.1 - Caller-ID Generation: starting Caller-ID alert and sending Caller-ID information:

13:41:49.035 TONESERVICES.EVENTS fxs 0/2 - Dsp 0/1.1 - Caller-ID Generation:   chars = ".$..12141341..2569631001..Mark Freeman9"

13:41:49.035 TONESERVICES.EVENTS fxs 0/2 - Dsp 0/1.1 - Caller-ID Generation:   bytes = "80 24 01 08 31 32 31 34 31 33 34 31 02 0A 32 35 36 39 36 33 31 30 30 31 07 0C 4D 61 72 6B 20 46 72 65 65 6D 61 6E 39"

13:41:49.035 TONESERVICES.EVENTS fxs 0/2 - Dsp 0/1.1 - Caller-ID Generation: TDM map

Tiger(config-2000)#

13:41:50.032 TONESERVICES.EVENTS fxs 0/2 - Dsp 0/1.1 - Caller-ID Generation: received Caller-ID Done event

13:41:50.032 TONESERVICES.EVENTS fxs 0/2 - Dsp 0/1.1 - Caller-ID Generation: stopping

13:41:50.032 TONESERVICES.EVENTS fxs 0/2 - Dsp 0/1.1 - Caller-ID Generation: TDM unmap

13:41:50.032 TONESERVICES.EVENTS fxs 0/2 - Dsp 0/1.1 - Caller-ID Generation: release

Tiger(config-2000)#

Tiger(config-2000)#

Tiger(config-2000)#

View solution in original post

0 Kudos
7 Replies
Anonymous
Not applicable

Re: 908 inbound caller ID not working

Jump to solution

Curt,

It should be on by default.

Try using this debug command and see what the output is on an inbound call.

# debug voice toneservices

Sample debug with caller-id

13:41:46.486 TONESERVICES.EVENTS fxs 0/2 - empty - Caller-ID Generation: Request resource

13:41:46.487 TONESERVICES.EVENTS fxs 0/2 - Dsp 0/1.1 - Caller-ID Generation: DSP channel allocated for the resource

13:41:46.487 TONESERVICES.EVENTS fxs 0/2 - Dsp 0/1.1 - Caller-ID Generation: constructed

13:41:49.034 TONESERVICES.EVENTS fxs 0/2 - Dsp 0/1.1 - Caller-ID Generation: starting Caller-ID alert and sending Caller-ID information:

13:41:49.035 TONESERVICES.EVENTS fxs 0/2 - Dsp 0/1.1 - Caller-ID Generation:   chars = ".$..12141341..2569631001..Mark Freeman9"

13:41:49.035 TONESERVICES.EVENTS fxs 0/2 - Dsp 0/1.1 - Caller-ID Generation:   bytes = "80 24 01 08 31 32 31 34 31 33 34 31 02 0A 32 35 36 39 36 33 31 30 30 31 07 0C 4D 61 72 6B 20 46 72 65 65 6D 61 6E 39"

13:41:49.035 TONESERVICES.EVENTS fxs 0/2 - Dsp 0/1.1 - Caller-ID Generation: TDM map

Tiger(config-2000)#

13:41:50.032 TONESERVICES.EVENTS fxs 0/2 - Dsp 0/1.1 - Caller-ID Generation: received Caller-ID Done event

13:41:50.032 TONESERVICES.EVENTS fxs 0/2 - Dsp 0/1.1 - Caller-ID Generation: stopping

13:41:50.032 TONESERVICES.EVENTS fxs 0/2 - Dsp 0/1.1 - Caller-ID Generation: TDM unmap

13:41:50.032 TONESERVICES.EVENTS fxs 0/2 - Dsp 0/1.1 - Caller-ID Generation: release

Tiger(config-2000)#

Tiger(config-2000)#

Tiger(config-2000)#

0 Kudos
Anonymous
Not applicable

Re: 908 inbound caller ID not working

Jump to solution

Curt,

If you don't see it, then can you send the following debug in a reply.

Debug sip stack messages

debug sip cldu

debug voice verbose

Thanks!

curtc
New Contributor

Re: 908 inbound caller ID not working

Jump to solution

That's what I thought.  The report was put in as no CID was working, and the first end user we tested with confirmed that there was no number even though there was.  Sigh.  After further communication and testing with the end customer, they ARE in fact getting the CID numbers.  It's just that it looks like the CNAM is sending "GRP WIRELESS CA", or "GRP Company Name CL", or just "G-CA".  It's the name they are having an issue with.  This has got to be the carrier.  Sorry for the hassle.

Anonymous
Not applicable

Re: 908 inbound caller ID not working

Jump to solution

no worries, post back if you need anything else!

-Mark

curtc
New Contributor

Re: 908 inbound caller ID not working

Jump to solution

If I look at the SIP Trace, it just says From: "wireless caller".   However, the Adtran I think is putting the GRP in there since it is in a ring group.  Can I remove that text?

16:27:37.546 TONESERVICES.EVENTS fxs 0/1 - Dsp 0/1.2 - Caller-ID Generation: starting Caller-ID alert and sending Caller-ID information:

16:27:37.547 TONESERVICES.EVENTS fxs 0/1 - Dsp 0/1.2 - Caller-ID Generation:   chars = ".'..05081627..6144192006..GRP_WIRELESS CA7"

Anonymous
Not applicable

Re: 908 inbound caller ID not working

Jump to solution

The Addition of GRP_ is used to let the caller know that the call is coming in via  ring group instead of a direct call to the voice user.

If you do a "show run voice ring-group verbose" you will see the prefix command below:

Tiger#show run voice ring-group verbose

Building configuration...

!

!

voice ring-group 6351

  type linear

  num-rings 2

  max-rolls 0

  max-inbound 1

  no coverage

  no did

  prefix "GRP"

  sip-identity 1234 T01

  sip-identity 2345 T01

If you want to turn it off, go into each ring-group that you have configured and enter:

no prefix

Let me know if you need anything else.

-Mark

curtc
New Contributor

Re: 908 inbound caller ID not working

Jump to solution

That sounds exactly like what we need.  Thank you!!!