[asterisk-users] Re: Nortel Option 11C and SIP gateway integration

Joe Dennick joe at dennick.net
Fri Nov 3 07:44:51 MST 2006


I'm not a Nortel expert, but if I remember correctly, you have to create 
a dial plan for every trunk on the Nortel.  I'm sure the Option 11C sees 
that SIP Gateway as a trunk, and as such it has to have a dialplan so 
that it knows what to do with calls coming in on that trunk. 

By the way, you can get creative with your numbering scheme and just 
assign a block of numbers to the SIP Gateway (like 4100 to 4199) so that 
you don't have to precede all those calls with an 8 (or 9).  We did this 
using a T-1 tie between an Option 61C and Asterisk where we assigned 
3000 to 3999 to the Asterisk system.  Using that method, four-digit 
dialing between the systems worked flawlessly....

Good luck!

Heison Chak wrote:

>Here's the Option 11 trace... I was not able to send as attachment.
>
>DCH 20 UIPE_IMSG CC_SETUP_IND  REF 00000004 CH 4 23 TOD  14:32:12 CK
>E4EA1E52
>CALLED  #:1500 NUM PLAN: UNKNOWN   TON: UNKNOWN
>CALLING #:1567 NUM PLAN: UNKNOWN   TON: UNKNOWN
>
>DCH 20 UIPE_OMSG CC_REJECT_REQ   REF 00008004 CH 4 23 TOD  14:32:12 CK
>E4EA1E6E
>
>CAUSE: #21 - CALL REJECTED
>
>DCH 20 UIPE_IMSG CC_SETUP_IND  REF 00000005 CH 4 23 TOD  14:32:16 CK
>E4EA39B2
>CALLED  #:1500 NUM PLAN: UNKNOWN   TON: UNKNOWN
>CALLING #:1567 NUM PLAN: UNKNOWN   TON: UNKNOWN
>
>DCH 20 UIPE_OMSG CC_REJECT_REQ   REF 00008005 CH 4 23 TOD  14:32:16 CK
>E4EA39CF
>
>CAUSE: #21 - CALL REJECTED
>
>DCH 20 UIPE_IMSG CC_SETUP_IND  REF 00000006 CH 4 23 TOD  14:32:20 CK
>E4EA540A
>CALLED  #:1500 NUM PLAN: UNKNOWN   TON: UNKNOWN
>CALLING #:1567 NUM PLAN: UNKNOWN   TON: UNKNOWN
>
>DCH 20 UIPE_OMSG CC_REJECT_REQ   REF 00008006 CH 4 23 TOD  14:32:20 CK
>E4EA5427
>
>CAUSE: #21 - CALL REJECTED
>
>DCH 20 UIPE_OMSG CC_SETUP_REQ  REF 0000002C CH 4 23 TOD  14:32:36 CK
>E4EAD197
>PROGRESS: ORIGINATING END IS NOT ISDN
>CALLING #:4169771414 NUM PLAN: E164  TON: NATL
>CALLED  #:1695 NUM PLAN: E164  TON: NATL
>
>DCH 20 UIPE_IMSG CC_PROCEED_IND  REF 0000002C CH 4 23 TOD  14:32:36 CK
>E4EAD254
>
>
>DCH 20 UIPE_IMSG CC_SETUP_CONF   REF 0000002C CH 4 23 TOD  14:32:36 CK
>E4EAD280
>
>
>DCH 20 UIPE_OMSG CC_DISC_REQ   REF 0000002C CH 4 23 TOD  14:32:38 CK
>E4EAEC5C
>CAUSE: #16 - NORMAL CALL CLEARING
>
>DCH 20 UIPE_IMSG CC_RELEASE_IND  REF 0000002C CH 4 23 TOD  14:32:38 CK
>E4EAECF7
>
>
>DCH 20 UIPE_OMSG CC_RELEASE_RESP   REF 0000002C CH 4 23 TOD  14:32:38 CK
>E4EAECF
>F
>
>
>
>
>
>
>
>
>
>
>
>Heison Chak wrote:
>  
>
>>Hi,
>>
>>     We have a Nortel Option 11C (with Succession 3.0), with 3 PRI cards
>>connected to:
>>1. PSTN
>>2. ITG network to our other 2 offices on a 4-digit dialplan
>>3. SIP media gateway (for Asterisk)
>>
>>     We normally dial access code "9" for outside PSTN calls, and when
>>the SIP media gateway was introduced, a new access code "8" was created.
>>Inbound calls from Nortel (originating from the PSTN, from any office
>>handset) are being delivered to the PRI trunk on the SIP media gatway
>>then onwards to Asterisk. However, any outgoing calls made from
>>Asterisk, into Nortel via SIP gateway is being rejected.
>>
>>     To narrow down the possibility, we have tried 2 different SIP
>>gateways - AudioCodes Mediant 1000 and Cisco AS5300, and they both
>>exhibit the same behavior (incoming works fine, ALL outgoing calls are
>>being rejected). Attached is the capture of the console message on the
>>Nortel side while an outbound call was made.
>>
>>Calls from x1567 (Cisco 7960 registered to Asterisk) to x1500 (digital
>>extension on Option 11C) is being reject with CAUSE #21.
>>
>>     The capture also shows a successful inbound call while 4169771414
>>(digital handset on Opt 11C) called x1695 (Meetme on Asterisk) via the
>>same PRI card (Ch. 4 23) was completed with release cause #16.
>>
>>     We suspect there is some authorization code or ACL that needs to be
>>put in place, so that calls made to the Opt 11C can be routed. We have
>>tired talking to 3 local Nortel vendors, AudioCodes and none has been
>>able to help us rectify this issue. We are looking for someone who can
>>help us identify what the problem is so that we can get this working.
>>
>>
>>Thanks
>>-Heison
>>
>>  
>>    
>>
>
>  
>
>------------------------------------------------------------------------
>
>_______________________________________________
>--Bandwidth and Colocation provided by Easynews.com --
>
>asterisk-users mailing list
>To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-users
>  
>


More information about the asterisk-users mailing list