Yelp!

We are ripping out the PBX and its currently providing ISDN connectivity
to our RightFax server.
Calls come into a PRI and get delivered to the Brooktrout TR1034+P4-2B
from a card in the PBX.

We've ordered a BRI card for a 3845. At this point we get no connection
between the server and router.

Has anyone done this before?


As an added twist, we are setting this up in Germany.

Any input greatly appreciated. We are cutting over on Friday.

-Erik



 ****************************************
*******************************

This communication is not intended to be used, and cannot be used,
by the recipient or any other person for the purpose of avoiding United
States federal tax penalties that may be imposed on the recipient or
such other person. In addition, if any United States federal tax
advice contained in this communication is used or referred to in
promoting, marketing or recommending any corporation, partnership
or other entity, investment plan, concept, structure or arrangement
(which should be assumed to be the case by a recipient or other
person who is not our client with respect to the subject matter of the
communication), then (i) such tax advice should be construed as written
to support the promotion or marketing of the transactions or matters
addressed by the advice and (ii) the recipient or other person should
seek advice based on the recipient or other person's particular
circumstances from an independent tax advisor. For further information,
please go to http://www.shearman.com/disclaimer/tax_disclosure.html

 ****************************************
*******************************

This transmittal and/or attachments may be a confidential
attorney-client communication or may otherwise be privileged or
confidential. If you are not the intended recipient, you are hereby
notified that you have received this transmittal in error; any review,
dissemination, distribution or copying of this transmittal is strictly
prohibited. If you have received this transmittal and/or attachments in
error, please notify us immediately by reply or by telephone (call us
collect at +1 212-848-8400) and immediately delete this message and
all its attachments.

Shearman & Sterling LLP is a limited liability partnership organized in
the United States under the laws of the State of Delaware, which laws
limit the personal liability of partners.

[ Post a follow-up to this message ]

I tried a couple of years ago to connect a BRI type brooktrout card to
a cisco voice gateway using BRI interfaces without success. I tried to
get tac to help and they simply said it will not work. Not sure what
the model number was of the card anymore.

With the pri versions of brooktrout it is apparently easy and might
also be easier now with the newer ISDN BRI cards from Cisco



Erik Erasmus

-----Original Message-----
From: cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Erik Stillman
Sent: Wednesday, September 26, 2007 11:04 AM
To: cisco-voip@puck.nether.net
Subject: [cisco-voip] RightFax

Yelp!

We are ripping out the PBX and its currently providing ISDN
connectivity
to our RightFax server.
Calls come into a PRI and get delivered to the Brooktrout TR1034+P4-2B
from a card in the PBX.

We've ordered a BRI card for a 3845. At this point we get no
connection
between the server and router.

Has anyone done this before?


As an added twist, we are setting this up in Germany.

Any input greatly appreciated. We are cutting over on Friday.

-Erik



 ****************************************
******************************
*

This communication is not intended to be used, and cannot be used,
by the recipient or any other person for the purpose of avoiding
United
States federal tax penalties that may be imposed on the recipient or
such other person. In addition, if any United States federal tax
advice contained in this communication is used or referred to in
promoting, marketing or recommending any corporation, partnership
or other entity, investment plan, concept, structure or arrangement
(which should be assumed to be the case by a recipient or other
person who is not our client with respect to the subject matter of the
communication), then (i) such tax advice should be construed as
written
to support the promotion or marketing of the transactions or matters
addressed by the advice and (ii) the recipient or other person should
seek advice based on the recipient or other person's particular
circumstances from an independent tax advisor. For further
information,
please go to http://www.shearman.com/disclaimer/tax_disclosure.html

 ****************************************
******************************
*

This transmittal and/or attachments may be a confidential
attorney-client communication or may otherwise be privileged or
confidential. If you are not the intended recipient, you are hereby
notified that you have received this transmittal in error; any review,
dissemination, distribution or copying of this transmittal is strictly
prohibited. If you have received this transmittal and/or attachments
in
error, please notify us immediately by reply or by telephone (call us
collect at +1 212-848-8400) and immediately delete this message and
all its attachments.

Shearman & Sterling LLP is a limited liability partnership organized
in
the United States under the laws of the State of Delaware, which laws
limit the personal liability of partners.
 ________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~
This e-mail is subject to the Telkom SA electronic communication legal notic
e, available at :
http://www.telkom.co.za/TelkomEMailLegalNotice.PDF
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~

[ Post a follow-up to this message ]

I think you'd need to configure the cisco router to bet BRI network
side, which is not a 'supported' feature.  I believe there are hidden
commands to force it, but there is no testing or support for that mode
of operation.

router doing network side PRI is supported.

/Wes

Erik Stillman wrote:
> Yelp!
>
> We are ripping out the PBX and its currently providing ISDN connectivity
> to our RightFax server.
> Calls come into a PRI and get delivered to the Brooktrout TR1034+P4-2B
> from a card in the PBX.
>
> We've ordered a BRI card for a 3845. At this point we get no connection
> between the server and router.
>
> Has anyone done this before?
>
>
> As an added twist, we are setting this up in Germany.
>
> Any input greatly appreciated. We are cutting over on Friday.
>
> -Erik
>
>
>
>  ****************************************
*******************************
>
> This communication is not intended to be used, and cannot be used,
> by the recipient or any other person for the purpose of avoiding United
> States federal tax penalties that may be imposed on the recipient or
> such other person. In addition, if any United States federal tax
> advice contained in this communication is used or referred to in
> promoting, marketing or recommending any corporation, partnership
> or other entity, investment plan, concept, structure or arrangement
> (which should be assumed to be the case by a recipient or other
> person who is not our client with respect to the subject matter of the
> communication), then (i) such tax advice should be construed as written
> to support the promotion or marketing of the transactions or matters
> addressed by the advice and (ii) the recipient or other person should
> seek advice based on the recipient or other person's particular
> circumstances from an independent tax advisor. For further information,
> please go to http://www.shearman.com/disclaimer/tax_disclosure.html
>
>  ****************************************
*******************************
>
> This transmittal and/or attachments may be a confidential
> attorney-client communication or may otherwise be privileged or
> confidential. If you are not the intended recipient, you are hereby
> notified that you have received this transmittal in error; any review,
> dissemination, distribution or copying of this transmittal is strictly
> prohibited. If you have received this transmittal and/or attachments in
> error, please notify us immediately by reply or by telephone (call us
> collect at +1 212-848-8400) and immediately delete this message and
> all its attachments.
>
> Shearman & Sterling LLP is a limited liability partnership organized in
> the United States under the laws of the State of Delaware, which laws
> limit the personal liability of partners.
>  ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>

[ Post a follow-up to this message ]

I've noticed with MGCP/PRI/VWIC2-1MFTT1/2811 IOS 12.4.11T3 in CCMAdmin
(5.1.2) there is drop down for "Network Side" but it never shows up in
the router show run. I manually put it there it works.  Is this by
design or a caveat?

-----Original Message-----
From: cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Wes Sisk
Sent: Wednesday, September 26, 2007 11:10 AM
To: Erik Stillman
Cc: cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] RightFax

I think you'd need to configure the cisco router to bet BRI network
side, which is not a 'supported' feature.  I believe there are hidden
commands to force it, but there is no testing or support for that mode
of operation.

router doing network side PRI is supported.

/Wes

Erik Stillman wrote:
> Yelp!
>
> We are ripping out the PBX and its currently providing ISDN
connectivity
> to our RightFax server.
> Calls come into a PRI and get delivered to the Brooktrout TR1034+P4-2B
> from a card in the PBX.
>
> We've ordered a BRI card for a 3845. At this point we get no
connection
> between the server and router.
>
> Has anyone done this before?
>
>
> As an added twist, we are setting this up in Germany.
>
> Any input greatly appreciated. We are cutting over on Friday.
>
> -Erik
>
>
>
>
 ****************************************
 *******************************
>
> This communication is not intended to be used, and cannot be used,
> by the recipient or any other person for the purpose of avoiding
United
> States federal tax penalties that may be imposed on the recipient or
> such other person. In addition, if any United States federal tax
> advice contained in this communication is used or referred to in
> promoting, marketing or recommending any corporation, partnership
> or other entity, investment plan, concept, structure or arrangement
> (which should be assumed to be the case by a recipient or other
> person who is not our client with respect to the subject matter of the
> communication), then (i) such tax advice should be construed as
written
> to support the promotion or marketing of the transactions or matters
> addressed by the advice and (ii) the recipient or other person should
> seek advice based on the recipient or other person's particular
> circumstances from an independent tax advisor. For further
information,
> please go to http://www.shearman.com/disclaimer/tax_disclosure.html
>
>
 ****************************************
 *******************************
>
> This transmittal and/or attachments may be a confidential
> attorney-client communication or may otherwise be privileged or
> confidential. If you are not the intended recipient, you are hereby
> notified that you have received this transmittal in error; any review,
> dissemination, distribution or copying of this transmittal is strictly
> prohibited. If you have received this transmittal and/or attachments
in
> error, please notify us immediately by reply or by telephone (call us
> collect at +1 212-848-8400) and immediately delete this message and
> all its attachments.
>
> Shearman & Sterling LLP is a limited liability partnership organized
in
> the United States under the laws of the State of Delaware, which laws
> limit the personal liability of partners.
>  ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
 ________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

-----------------------------------------
Disclaimer:

This e-mail communication and any attachments may contain
confidential and privileged information and is for use by the
designated addressee(s) named above only.  If you are not the
intended addressee, you are hereby notified that you have received
this communication in error and that any use or reproduction of
this email or its contents is strictly prohibited and may be
unlawful.  If you have received this communication in error, please
notify us immediately by replying to this message and deleting it
from your computer. Thank you.

[ Post a follow-up to this message ]

i imagine this is because L3 is backhauled and so CCM is handling the
q931 and acting as network side.

Justin

On 9/26/07, Jason Aarons (US) <jason.aarons@us.didata.com> wrote:
> I've noticed with MGCP/PRI/VWIC2-1MFTT1/2811 IOS 12.4.11T3 in CCMAdmin
> (5.1.2) there is drop down for "Network Side" but it never shows up in
> the router show run. I manually put it there it works.  Is this by
> design or a caveat?
>
> -----Original Message-----
> From: cisco-voip-bounces@puck.nether.net
> [mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Wes Sisk
> Sent: Wednesday, September 26, 2007 11:10 AM
> To: Erik Stillman
> Cc: cisco-voip@puck.nether.net
> Subject: Re: [cisco-voip] RightFax
>
> I think you'd need to configure the cisco router to bet BRI network
> side, which is not a 'supported' feature.  I believe there are hidden
> commands to force it, but there is no testing or support for that mode
> of operation.
>
> router doing network side PRI is supported.
>
> /Wes
>
> Erik Stillman wrote: 
> connectivity 
> connection 
>  ****************************************
******************************* 
> United 
> written 
> information, 
>  ****************************************
******************************* 
> in 
> in 
>  ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
> -----------------------------------------
> Disclaimer:
>
> This e-mail communication and any attachments may contain
> confidential and privileged information and is for use by the
> designated addressee(s) named above only.  If you are not the
> intended addressee, you are hereby notified that you have received
> this communication in error and that any use or reproduction of
> this email or its contents is strictly prohibited and may be
> unlawful.  If you have received this communication in error, please
> notify us immediately by replying to this message and deleting it
> from your computer. Thank you.
>  ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>

[ Post a follow-up to this message ]

That worked!

Now we are having transmission errors and the baud rate is only 9600.

Erik

-----Original Message-----
From: Wes Sisk [mailto:wsisk@cisco.com]
Sent: Wednesday, September 26, 2007 5:10 PM
To: Erik Stillman
Cc: cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] RightFax

I think you'd need to configure the cisco router to bet BRI network
side, which is not a 'supported' feature.  I believe there are hidden
commands to force it, but there is no testing or support for that mode
of operation.

router doing network side PRI is supported.

/Wes

Erik Stillman wrote:
> Yelp!
>
> We are ripping out the PBX and its currently providing ISDN
> connectivity to our RightFax server.
> Calls come into a PRI and get delivered to the Brooktrout TR1034+P4-2B

> from a card in the PBX.
>
> We've ordered a BRI card for a 3845. At this point we get no
> connection between the server and router.
>
> Has anyone done this before?
>
>
> As an added twist, we are setting this up in Germany.
>
> Any input greatly appreciated. We are cutting over on Friday.
>
> -Erik
>
>
>
>  ****************************************
******************************
> *
>
> This communication is not intended to be used, and cannot be used, by
> the recipient or any other person for the purpose of avoiding United
> States federal tax penalties that may be imposed on the recipient or
> such other person. In addition, if any United States federal tax
> advice contained in this communication is used or referred to in
> promoting, marketing or recommending any corporation, partnership or
> other entity, investment plan, concept, structure or arrangement
> (which should be assumed to be the case by a recipient or other person

> who is not our client with respect to the subject matter of the
> communication), then (i) such tax advice should be construed as
> written to support the promotion or marketing of the transactions or
> matters addressed by the advice and (ii) the recipient or other person

> should seek advice based on the recipient or other person's particular

> circumstances from an independent tax advisor. For further
> information, please go to
> http://www.shearman.com/disclaimer/tax_disclosure.html
>
>  ****************************************
******************************
> *
>
> This transmittal and/or attachments may be a confidential
> attorney-client communication or may otherwise be privileged or
> confidential. If you are not the intended recipient, you are hereby
> notified that you have received this transmittal in error; any review,

> dissemination, distribution or copying of this transmittal is strictly

> prohibited. If you have received this transmittal and/or attachments
> in error, please notify us immediately by reply or by telephone (call
> us collect at +1 212-848-8400) and immediately delete this message and

> all its attachments.
>
> Shearman & Sterling LLP is a limited liability partnership organized
> in the United States under the laws of the State of Delaware, which
> laws limit the personal liability of partners.
>  ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>

[ Post a follow-up to this message ]