UC520 Inbound Caller ID

Unanswered Question
Apr 23rd, 2009
User Badges:

Hi All,

We have a UC520 system installed, it works fine in and outbound calls. All outbound calls show our primary number as the CID, however right now incoming calls only show the calling number.


When I added this line to my PRI port:


interface Serial0/3/0:23

no isdn supp-service name calling


incoming caller ID now shows correctly, however now I am unable to make out bound calls.


I think these are all of the rules for outbound but am not sure why.

Below is what I assume are the pieces of configuration needed ?


voice translation-rule 1111

rule 1 /.*/ /xxxxxxxxxx/


voice translation-profile OUTGOING_TRANSLATION_PROFILE

translate calling 1111


voice translation-profile CALLER_ID_TRANSLATION_PROFILE

translate calling 1111



dial-peer voice 151 pots

corlist outgoing call-local

description ** T1 pots dial-peer **

translation-profile outgoing CALLER_ID_TRANSLATION_PROFILE

preference 5

destination-pattern 9[2-9]......

port 0/3/0:23

forward-digits 7

no sip-register

!

dial-peer voice 152 pots

corlist outgoing call-domestic

description ** T1 pots dial-peer **

translation-profile outgoing CALLER_ID_TRANSLATION_PROFILE

preference 5

destination-pattern 91[2-9]..[2-9]......

port 0/3/0:23

prefix 1

no sip-register

!

dial-peer voice 154 pots

description ** T1 pots dial-peer **-Emergency dial-peer

translation-profile outgoing CALLER_ID_TRANSLATION_PROFILE

preference 5

destination-pattern 9911

port 0/3/0:23

forward-digits 3

no sip-register

!

dial-peer voice 155 pots

description ** T1 pots dial-peer **-Emergency dial-peer

translation-profile outgoing CALLER_ID_TRANSLATION_PROFILE

preference 5

destination-pattern 911

port 0/3/0:23

forward-digits 3

no sip-register

!

dial-peer voice 156 pots

corlist outgoing call-local

description ** T1 pots dial-peer **

translation-profile outgoing CALLER_ID_TRANSLATION_PROFILE

preference 5

destination-pattern 9[2-9]11

port 0/3/0:23

forward-digits 3

no sip-register


Thank You.

Gary

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
paolo bevilacqua Thu, 04/23/2009 - 13:03
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    Founding Member

Take "debug isdn q931" with "term mon" it the various situations, that will clarify what's going on.

g.portellas Thu, 04/23/2009 - 17:59
User Badges:

Ok, I get this reject code - guess this is the reason.

268910: Apr 24 01:43:10.264: ISDN Se0/3/0:23 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x820C

Cause i = 0x82B2 - Requested facility not subscribed


paolo bevilacqua Fri, 04/24/2009 - 05:31
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    Founding Member

Ok, but one should check what exactly is the facility and why the clid is not correct when facility is not used.

g.portellas Fri, 04/24/2009 - 06:34
User Badges:

Morning,

I have attached the fail log - I tried working my way through it and comparing it against a connection when I don't use the "isdn supp-service name calling" line - wasn't sure what I should be looking for.


Thanks for your help.



Attachment: 
paolo bevilacqua Fri, 04/24/2009 - 10:46
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    Founding Member

Please take the traces with "debug isdn q931" ad indicated above, and nothing else.

Actions

This Discussion