Hi Mark, Your understand is spot on. A4.11. One PRI to a Lucent 5ESS CO. It's a lab setup so there is next to no traffic. Not that it's related to this case but the 908e does handle REFERs correctly from sipX when necessary. That got crossed off the list yesterday.
Back to the sipX box. Capturing traffic on localhost 5060 I found the INVITE that represented the outbound leg of the call. It gets shot down with a "403 Requires" by "Server: sipXecs/4.6.0 sipXecs/sipXproxy (Linux)", never making it to the gateway. - Jeff On Wed, Sep 19, 2012 at 5:02 PM, Mark A. Smith <[email protected]> wrote: > > > Hi Jeff, > Just to ensure I understand the scenario: > • Calling party originates via PRI > • Calling party is routed to called party. > • Called party is unavailable, rule is set to forward to > 10 digit destination number via PRI > • Calling party actually arrives at Free Switch VM box for > called party. > • The ISDN-PRI gateway is an ADTRAN 908e > First, could you please share what version of AOS your TA is > running? > Second, how many PRIs are actually terminating on the 908e? > > Best, > Mark > > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/ >
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
