" /> Unable to route to newly registered extension: dn <dn> is ignored: wrong dn(cfg) - Genesys CTI User Forum

Author Topic: Unable to route to newly registered extension: dn <dn> is ignored: wrong dn(cfg)  (Read 3509 times)

Offline elzazz

  • Newbie
  • *
  • Posts: 2
  • Karma: 0
Advertisement
Folks,

New to the forum and very glad to have found it. I am running into a problem with a set of newly registered extensions, whenever an agent uses a place attached to those extensions i see the following in the URS Log (i have replaced actual agent and dn number for generic stuff because of confidentiality):

tenant Resources Agent <Employee ID>: dn <extension number> (d 1) is ignored: wrong dn(cfg)

If i use the same agent logged in to a place/extension which was previously registered, i have no problems, it is just the new ones, which share the exact same configuration. I think i may have exceeded my agent seat license count, but i have no knowledge on how to tell. Anyone experienced anything similar?

Z.

Offline kubikle

  • Full Member
  • ***
  • Posts: 140
  • Karma: 7
From URS perspective this mesasage means that no such DN exists inconfiguration.
Check URS log for notiifcation from config server that such DN was created.

Offline Timur Karimov

  • Sr. Member
  • ****
  • Posts: 415
  • Karma: 2
Do you have multimedia installed in your system or it's just voice routing solution?
Check URS use_dn_type options value and correct DN type or this options value according with you envirovment.

WBR Timur

Offline elzazz

  • Newbie
  • *
  • Posts: 2
  • Karma: 0
Thank you for your responses. I had to bring both the Cisco T Servers and URS's down at once (needed to bring both primary and backup down at the same time) so that everything re-registered and all config changes to refresh...

I know config changes are supposed to propagate realtime but sometimes i guess you have to force apps to get the latest config data. Now everything works.

Offline cavagnaro

  • Administrator
  • Hero Member
  • *****
  • Posts: 7641
  • Karma: 56330
It may also be case that if license failure the error has just moved to another objects...be careful