Send cisco-voip mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://puck.nether.net/mailman/listinfo/cisco-voip
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of cisco-voip digest..."
Today's Topics:
1. 60 channel SIP trunk to H323 trunk (Hefin James [ahj])
2. Re: 60 channel SIP trunk to H323 trunk (Wes Sisk)
3. Re: 60 channel SIP trunk to H323 trunk (Hefin James [ahj])
4. bogen tamb pop when user hangs up - vg224 (Erick Wellnitz)
5. Re: bogen tamb pop when user hangs up - vg224 (Jason Faraone)
----------------------------------------------------------------------
Message: 1
Date: Wed, 7 Aug 2013 06:06:38 +0000
From: "Hefin James [ahj]" <[email protected]>
To: "[email protected]" <[email protected]>
Subject: [cisco-voip] 60 channel SIP trunk to H323 trunk
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"
All,
We have a SIP trunk connected to a IP-IP gateway, and connected to CM via H323.
It's working fine, but we have just flexed the link up to 60 channels in
readiness of high demand later in the month.
I suddenly thought, can H323 handle 60 channels?
Or do I need to configure proper SIP to SIP?
Thanks,
Hefin
------------------------------
Message: 2
Date: Wed, 7 Aug 2013 10:59:50 -0400
From: Wes Sisk <[email protected]>
To: "Hefin James [ahj]" <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [cisco-voip] 60 channel SIP trunk to H323 trunk
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii
H.323 can easily handle 60 channels. The only limitations might be around
locations bandwidth provisioned for the trunk.
Otherwise, an h.323 trunk will start throttling above 24cps. Usually that call
rate only occurs with a call routing loop.
Regards,
Wes
On Aug 7, 2013, at 2:06 AM, Hefin James [ahj] <[email protected]> wrote:
All,
We have a SIP trunk connected to a IP-IP gateway, and connected to CM via H323.
It's working fine, but we have just flexed the link up to 60 channels in
readiness of high demand later in the month.
I suddenly thought, can H323 handle 60 channels?
Or do I need to configure proper SIP to SIP?
Thanks,
Hefin
_______________________________________________
cisco-voip mailing list
[email protected]
https://puck.nether.net/mailman/listinfo/cisco-voip
------------------------------
Message: 3
Date: Wed, 7 Aug 2013 15:34:38 +0000
From: "Hefin James [ahj]" <[email protected]>
To: Wes Sisk <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [cisco-voip] 60 channel SIP trunk to H323 trunk
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"
Thanks Wes.
Real bandwidth between the gateway, and CM is 1Gbps, and the location bandwidth
for audio in unlimited.
I don't think we'll see 24cps, but thanks for letting me know.
Thanks,
Hefin
-----Original Message-----
From: Wes Sisk [mailto:[email protected]]
Sent: 07 August 2013 16:00
To: Hefin James [ahj]
Cc: [email protected]
Subject: Re: [cisco-voip] 60 channel SIP trunk to H323 trunk
H.323 can easily handle 60 channels. The only limitations might be around
locations bandwidth provisioned for the trunk.
Otherwise, an h.323 trunk will start throttling above 24cps. Usually that call
rate only occurs with a call routing loop.
Regards,
Wes
On Aug 7, 2013, at 2:06 AM, Hefin James [ahj] <[email protected]> wrote:
All,
We have a SIP trunk connected to a IP-IP gateway, and connected to CM via H323.
It's working fine, but we have just flexed the link up to 60 channels in
readiness of high demand later in the month.
I suddenly thought, can H323 handle 60 channels?
Or do I need to configure proper SIP to SIP?
Thanks,
Hefin
_______________________________________________
cisco-voip mailing list
[email protected]
https://puck.nether.net/mailman/listinfo/cisco-voip
------------------------------
Message: 4
Date: Wed, 7 Aug 2013 15:15:17 -0500
From: Erick Wellnitz <[email protected]>
To: cisco-voip <[email protected]>
Subject: [cisco-voip] bogen tamb pop when user hangs up - vg224
Message-ID:
<CAK0wOsCGm=9mhg1mn9guqjncnfswqr3mdpmaj3zetrqpndt...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
Anyone ever had an issue where there is a 'pop' after the user hangs up to
a Bogen tamb? We have it connected via a VG224.
The strangest part is that we have another one that is perfect without
tweaking anything.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130807/30e939dd/attachment-0001.html>
------------------------------
Message: 5
Date: Wed, 7 Aug 2013 20:26:16 +0000
From: Jason Faraone <[email protected]>
To: "'Erick Wellnitz'" <[email protected]>, cisco-voip
<[email protected]>
Subject: Re: [cisco-voip] bogen tamb pop when user hangs up - vg224
Message-ID:
<fb0beb07ca11e54a83b331ad1c263ed665d9d...@chq-mdf-mbx-01.paulo.com>
Content-Type: text/plain; charset="us-ascii"
I have a few locations with the same setup (VG224 => Tam B) and I don't think I
have seen this issue. My dipswitch configuration is (1,2,4,5 = OFF; 3 = ON).
From: cisco-voip [mailto:[email protected]] On Behalf Of Erick
Wellnitz
Sent: Wednesday, August 07, 2013 3:15 PM
To: cisco-voip
Subject: [cisco-voip] bogen tamb pop when user hangs up - vg224
Anyone ever had an issue where there is a 'pop' after the user hangs up to a
Bogen tamb? We have it connected via a VG224.
The strangest part is that we have another one that is perfect without tweaking
anything.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130807/032ed638/attachment-0001.html>
------------------------------
Subject: Digest Footer
_______________________________________________
cisco-voip mailing list
[email protected]
https://puck.nether.net/mailman/listinfo/cisco-voip
------------------------------
End of cisco-voip Digest, Vol 118, Issue 6
******************************************
