Erik Anderson wrote: > On 8/6/07, Anthony Francis <[EMAIL PROTECTED]> wrote: > >> also in asterisk do: >> pri intense debug span 1 >> Then you should see UA's and SABME's, If you don't, your not talking to >> them. >> > > I see plenty of SABMEs, but nothing else: > > >> [ 02 01 7f ] >> > > >> Unnumbered frame: >> SAPI: 00 C/R: 1 EA: 0 >> TEI: 000 EA: 1 >> M3: 3 P/F: 1 M2: 3 11: 3 [ SABME (set asynchronous balanced mode >> extended) ] >> 0 bytes of data >> > Sending Set Asynchronous Balanced Mode Extended > > >> [ 02 01 7f ] >> > > >> Unnumbered frame: >> SAPI: 00 C/R: 1 EA: 0 >> TEI: 000 EA: 1 >> M3: 3 P/F: 1 M2: 3 11: 3 [ SABME (set asynchronous balanced mode >> extended) ] >> 0 bytes of data >> > Sending Set Asynchronous Balanced Mode Extended > lpdlnx04*CLI> pri > >> [ 02 01 7f ] >> > lpdlnx04*CLI> pri > >> Unnumbered frame: >> SAPI: 00 C/R: 1 EA: 0 >> TEI: 000 EA: 1 >> M3: 3 P/F: 1 M2: 3 11: 3 [ SABME (set asynchronous balanced mode >> extended) ] >> 0 bytes of data >> > Sending Set Asynchronous Balanced Mode Extended > > _______________________________________________ > --Bandwidth and Colocation Provided by http://www.api-digital.com-- > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users > Yeah you are sending the SABME's because you think you are the master, they are not replaying with a UA because they think they are the master, you should def be pri_cpe.
There is one other potential cause here, you may not have had the sangoma install patch and rebuild zaptel. Not doing that can cause a D channel lockout on your end, but the provider should be able to see the the D is in lockout. Anthony _______________________________________________ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
