[nsp] Trying to connect Nortel Meridian Option 11 to SL100 us ing Cisco voice modules

Burns, Keith Keith_Burns at icgcomm.com
Fri Dec 19 12:49:11 EST 2003


Is there anyway you can do PRI instead of CAS??

Depending on the loads in your Meridian, you should be able to.

PRI is simpler (IMHO) and allows passing of CALLING party information
without dual-step outpulsing on the CAS (quicker call setup times with
CALLING party passed).

Keith Burns
Principal Network Architect
ICG Telecommunications
IP Ph: 303-414-5385
Cell:   303-912-3777 

"The dogs may bark, but the caravan rolls on...."


> -----Original Message-----
> From: FILYURIN, YAN [mailto:YAN_FILYURIN at fleet.com]
> Sent: Friday, December 19, 2003 9:20 AM
> To: cisco-nsp at puck.nether.net
> Cc: isp-routing at isp-routing.com
> Subject: [nsp] Trying to connect Nortel Meridian Option 11 to SL100
> using Cisco voice modules
> 
> 
> I was wondering if anyone out there had experience doing 
> something similar.
> We have Nortel Meridian option 11 in Mexico City and Sl100 in 
> US.  What we
> are trying to do is connect both devices to voice ports on Cisco High
> Density Voice Network Modules on cisco 3600 routers and use 
> connection trunk
> to make voice calls.  It is T1 on the US end and E1 on Mexico 
> end and we are
> trying to use three channels.  We are using E&M wink start 
> signaling and we
> are migrating the connection from IDNX Nodes to the routers, 
> since we have
> to retire IDNX nodes.  According to our voice group they are 
> seeing and
> attempt on the Boston end to seize the channels and the 
> signaling is wrong
> so they channels become locked.  So I was wondering if I have to do
> something about ABCD signaling to make sure it matches, or there is
> something else that is important I am missing. Thanks in 
> advance for any
> assistance.
> 
> 
> 
> Yan Filyurin
> Fleet Services Group 
> Enterprise Network Planning and Design
> Phone: 617-533-4536
> Cell:      617-875-4862
> Pager:  617-339-8913
> yan_filyurin at fleet.com
> 
> 
> 
> 
> 


More information about the cisco-nsp mailing list