denial event 1166: Unassigned number 1

[simreal]

I need a little help here.

I'm setting up a QSIG trunk from Avaya to Cisco Call manager. This is for Unity Integrations.

The number I'm using to get calls to Unity is 4444 (currently for testing).

When I dial I immediately get wave off.

I google'd and I searched previous posts here. I found some folks with the same issue but no resolutions were posted.

My "list trace station":

12:25:11     active station    81018 cid 0x227c
12:25:11     G729A ss:off ps:20 rn:32/2 10.35.41.108:2946 10.35.252.14:4968
12:25:11     xoip: fax:PT modem:PT tty:US 10.35.252.14:4968 uid:0x8a5b
12:25:12     dial 4444 route:UDP|AAR
12:25:12     term trunk-group 45    cid 0x227c
12:25:12     dial 4444 route:UDP|AAR
12:25:12     route-pattern  45 preference 1  cid 0x227c
12:25:12     seize trunk-group 45 member 1  cid 0x227c
12:25:12     Calling Number & Name NO-CPNumber Miguel Hidalg
12:25:12     G729A ss:off ps:20 rn:32/31 10.35.41.108:2946 10.35.0.12:2580
12:25:12     xoip: fax:PT modem:PT tty:US 10.35.0.12:2580 uid:0x8a5b
12:25:12     denial event 1166: Unassigned number D1=0x8a5b D2=0x860f01
12:25:12     idle trunk-group 45 member 1  cid 0x227c
12:25:13     idle station    81018 cid 0x227c

My "change uniform-dialplan 4":

  Matching         Insert          Node   Matching         Insert          Node 
  Pattern  Len Del Digits Net Conv Num    Pattern  Len Del Digits Net Conv Num  
  4444      4   0         aar  n          6105      4   0         ext  n

My "change aar analysis 4":

          Dialed           Total     Route    Call   Node  ANI                  
          String          Min  Max  Pattern   Type   Num   Reqd                 
    4444                  4    4     45       aar          y

My "display route-pattern 45"

                             SCCAN? n     Secure SIP? n                         
    Grp FRL NPA Pfx Hop Toll No.  Inserted                             DCS/ IXC 
    No          Mrk Lmt List Del  Digits                               QSIG     
                             Dgts                                      Intw     
 1: 45   0                                                              n   user
 2:                                                                     n   user
 3:                                                                     n   user
 4:                                                                     n   user
 5:                                                                     n   user
 6:                                                                     n   user
                                                                                
     BCC VALUE  TSC CA-TSC    ITC BCIE Service/Feature PARM  No. Numbering LAR  
    0 1 2 3 4 W     Request                                 Dgts Format         
                                                         Subaddress             
 1: y y y y y n  y  as-needed rest                               pub-unk   none 
 2: y y y y y n  n            rest                                         none 
 3: y y y y y n  n            rest                                         none 
 4: y y y y y n  n            rest                                         none 
 5: y y y y y n  n            rest                                         none 
 6: y y y y y n  n            rest                                         none 
                                                                                
                            Pattern Number: 45

What am I doing wrong here? Any help would be greatly appreciated.

 

[simreal]

I should also mention we are able to get calls from the Cisco to the Avay with info just fine.

 

[Mitch672]

Looks like the CISCO is waving you off, e.g. it is not accepting the call to 4444

Looks like its an H323 trunk group, you should check your Qsig tranlations, and status the signalling group and trunk group, mkae sure they are inservice.

Mitch

 

[mikeydidit]

simreal

Here is something I think will help you that i found while looking for you.

http://www.cisco.com/pcgi-bin/searc...&accessLevel=Guest&siteToSearch=cisco.com#TSD

Hell, there are no rules here - we're trying to accomplish something.
Thomas A. Edison

For the best response to a question, read faq690-6594

 

[simreal]

Thanks for the links mikeydidit. I have been through the cisco documents forward and backwards.

Ciscos interoperability portal has a document that specifies this particular integration method and details the config but I'm still having issues.

I'll keep looking though.

Mitch672, It's not a H323 trunk. It's an ISDN-PRI. The document I used to configure the trunk is here:

http://www.cisco.com/en/US/tech/tk1077/technologies_tech_note09186a00803d22cd.shtml

Thanks for the input folks. I'm still searhcing.

 

[mikeydidit]

Lets try it from the other side then.

http://www.avaya.com/gcm/master-usa...Type:Application Notes;CollectionSearch:cisco

Hopefully you can find what you need here.

Hell, there are no rules here - we're trying to accomplish something.
Thomas A. Edison

For the best response to a question, read faq690-6594

 

[simreal]

Thanks for taking the time to search for those Mikey. I'll give you a star for the effort.

I have already searched both sites and read everything i could find for the past 4 days. I have searched google which usually leads me back here, as well as calling upon my personal contacts at avaya (I worked at the TSO for 7 years) and at Cisco. I have a Cisco Engineer onsite every weds and thrusday for half the day working on application developement.

I even have running configs for a Company I used to work for that succesfully integrate Avaya and Call manager via QSIG. That integration was accomplished using the same documentation.

I'm missing something thats not standard in my config or I would have found it by now.

Thanks again for all the help. I will post a resolution once I have found it.

 

[mikeydidit]

I did a search at the top of the page for you and found this. He has it working but with no ANI. This might help.

thread690-1214380

Let me know and I'll keep digging for you.

Hell, there are no rules here - we're trying to accomplish something.
Thomas A. Edison

For the best response to a question, read faq690-6594

 

[simreal]

Yeah I saw that post. I would reply to his thread to help him. he needs to make an entry in the public unknown numbering table to solve his problem.


I have done that in my case and I can verify my call is hitting the trunk, and that I'm sending name and number (number only with the pub-unk info) and the call is being rejected by the cisco.

I believe its being rejected anyway. I just don't know why or how to fix it.

The one thing that causes me a little concern is when I do a "list trace tac #46/Q" which should give me the gqis info for the trace only I get nothing.


The hunt continues.

 

[kwing112000]

I just posted in your other thread. Why dont you post on the cisco side and see if they have found anything. there is a CM forum here.

 

[simreal]

Alright, I have it working now. We can get calls accross both ways and I even have coverage to Unity on the avaya.

What I'm working on now is the MWI. They don't light as of right now. The documentation doesn't detail the configuration of MWI.

So ... google is my friend.

I'll post the configs when I get it all working.

 

[mikeydidit]

Thanks simreal. It may save someone a lot of time somewhere down the road. Glad you got them talking.

Hell, there are no rules here - we're trying to accomplish something.
Thomas A. Edison

For the best response to a question, read faq690-6594

 

[Gielo]

Try changing the AAR setting in the cha aar analysis to pubu and try again

 

[simreal]

Thanks Gielo but we got it working. As it turns out the document details the configs comepletly. We had missed a calling search space setting in the cisco.


Everything is working now. The one thing the docs dont tell you is how to get the call to the cisco. The way I chose to do it was using AAR and a remote coverage point in a cover path. The remote coverage point is the lead extension to Unity in call manager.

As fas as the MWI goes all we had to do was configure routes in the call manager to the extension in the avaya. QSIG took care of the rest.