PINX_DN for QSIG Path Replacement
Bookmark this page:
 Yahoo!
 Google
 Windows Live
 del.icio.us
 digg
 Netscape
|
|
||||||||||||||||
|
Posted by John Neiberger on May 12, 2006, 3:01 pm
Please log in for more thread options and it mentions that a PINX_DN must be configured for certain QSIG features to work, specifically Path Replacement. The guide seems to indicate that this is a mandatory configuration. Nowhere does it indicate that it might be optional, nor does it describe how the PBX will behave if it is not configured. When we did some interoperability testing several months ago, we didn't configure this on any of our PBXs and path replacement worked most of the time. The only time it didn't work is when our 81C was at the end of the line. Path replacement always worked if an 11C was the final destination. That makes me think that perhaps this setting isn't quite as mandatory as the guide indicates. On the other hand, it might help explain why the 81C didn't handle path replacement correctly. Any thoughts? Do any of you have path replacement working correctly without configuring a PINX_DN on each PBX? Thanks! John | ||||||||||||||||
|
Posted by on May 16, 2006, 11:18 am
Please log in for more thread options of my engineers to help you out. Who is your service provider? james.stanford@xo.com | ||||||||||||||||
| Similar Threads | Posted |
| PINX_DN for QSIG Path Replacement | May 12, 2006, 3:01 pm |
| Meridian E1 QSIG to Meridain T1 Qsig | March 16, 2005, 10:37 am |
| QSIG Question | January 13, 2006, 12:53 am |
| MerAssistant MAC replacement for OTM/TM | June 11, 2008, 9:20 am |
| QSIG Bug on 81C running Succession 3.0 | May 7, 2006, 2:13 am |
| install PRI2 / Qsig | October 3, 2006, 1:01 pm |
| OTP 11c ITG Trunk to Toshiba Qsig/Stratanet | February 15, 2006, 8:50 am |
| Alteon Websystems Aceswitch 180 replacement | November 7, 2005, 11:57 am |