Nicholas,
In the UK, I had the same quality issue until I put the compand-type under the voice port -- it may or not work for you, try it with a-law then u-law. Also have you stuck the correct cptone as well? You may have to shut/no shut the voice-port XX/XX to activate, anytime you alter voice-port settings.
voice-port 2/0
compand-type a-law
cptone GB
!
voice-port 2/1
compand-type a-law
cptone GB
!
Paul
________________________________
From: cisco-voip-bounces@puck.nether.net on behalf of cisco-voip-request@puck.nether.net
Sent: Sun 25/04/2004 17:01
To: cisco-voip@puck.nether.net
Subject: cisco-voip Digest, Vol 14, Issue 31
Send cisco-voip mailing list submissions to
cisco-voip@puck.nether.net
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
cisco-voip-request@puck.nether.net
You can reach the person managing the list at
cisco-voip-owner@puck.nether.net
When replying, please edit your Subject line so it is more specific
than "Re: Contents of cisco-voip digest..."
Today's Topics:
1. Cisco voip linked huntgroups (Peter)
2. Re: VOIP, CME and ISDN BRI problem (Nicolas Goy)
----------------------------------------------------------------------
Message: 1
Date: Sun, 25 Apr 2004 14:14:39 +0200
From: "Peter" <peterderegt@wanadoo.nl>
Subject: [cisco-voip] Cisco voip linked huntgroups
To: <cisco-voip@puck.nether.net>
Message-ID: <00bc01c42abe$e210c840$9600000a@wshenk>
Content-Type: text/plain; charset="iso-8859-1"
Hello,
Does anyone know the procedure to create linked huntgroups in a Cisco Call
manager 3.3(4) envirement?
My procedure:
-Create pilot point
-Create members in huntgroup
-Create in huntgroup at the a huntgroup member as route member
-Toggle TCD service
-Create AC user-huntgroup
The huntgroup are working independent fine, but I when I create a huntgroup
in a huntgroup, the attached huntgroup will not work.
So, I have huntgroup 4444 with members 4565, 5678 and huntgroup number 6754,
the call will only switch to 4565 and 5678 and not the attached huntgroup
6754.
In the huntgroup I attached member with a directory number and not with a user, that's not necessary? And can I attached all the huntgroups under the same AC user?
Can anyone help me with problem?
Thanks in advance!
Regards,
Peter
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20040425/7bf57be7/attachment-0001.html
------------------------------
Message: 2
Date: Sun, 25 Apr 2004 17:27:55 +0200
From: Nicolas Goy <goyman@goyman.com>
Subject: Re: [cisco-voip] VOIP, CME and ISDN BRI problem
To: cisco-voip@puck.nether.net
Message-ID: <1FCABABC-96CD-11D8-AB98-000393481E96@goyman.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Hello,
Now incoming call are correctly routed to phone 1 ( I added
voice-port 1/0/0
translate called 1
)
But when I answer the call, the song quality is absolutly horrible with
a buzzing noise in the background.
Intern calls have very good quality, but ISDN-IP are completly
garbled...
If you have any tips on the one.
I still can't make outgouing calls.
On Apr 22, 2004, at 11:28 PM, Nicolas Goy wrote:
> Hello,
>
> I try to setup voip at our office, I got the following configuration:
>
......
------------------------------
_______________________________________________
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
End of cisco-voip Digest, Vol 14, Issue 31
******************************************
DISCLAIMER:
This message is intended only for the use of the person(s) ('Intended Recipient') to whom it is addressed. It may contain information, which is privileged and confidential. Accordingly any dissemination, distribution, copying or other use of this message or any of its content by any person other than the Intended Recipient may constitute a breach of civil or criminal law and is strictly prohibited. If you are not the Intended Recipient, please contact the sender as soon as possible. Neither Lynx Technology Ltd or the sender accept any responsibility for viruses and its is your responsibility to scan the email and attachments. Any liability arising from any third party acting on any information contained in this email is hereby excluded. Lynx Technology Ltd will hold data provided by you for marketing and promotional purposes unless otherwise advised. If you no longer wish to receive communication from Lynx Technology, please see our Statement of Privacy at www.lynxtec.com.
In the UK, I had the same quality issue until I put the compand-type under the voice port -- it may or not work for you, try it with a-law then u-law. Also have you stuck the correct cptone as well? You may have to shut/no shut the voice-port XX/XX to activate, anytime you alter voice-port settings.
voice-port 2/0
compand-type a-law
cptone GB
!
voice-port 2/1
compand-type a-law
cptone GB
!
Paul
________________________________
From: cisco-voip-bounces@puck.nether.net on behalf of cisco-voip-request@puck.nether.net
Sent: Sun 25/04/2004 17:01
To: cisco-voip@puck.nether.net
Subject: cisco-voip Digest, Vol 14, Issue 31
Send cisco-voip mailing list submissions to
cisco-voip@puck.nether.net
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
cisco-voip-request@puck.nether.net
You can reach the person managing the list at
cisco-voip-owner@puck.nether.net
When replying, please edit your Subject line so it is more specific
than "Re: Contents of cisco-voip digest..."
Today's Topics:
1. Cisco voip linked huntgroups (Peter)
2. Re: VOIP, CME and ISDN BRI problem (Nicolas Goy)
----------------------------------------------------------------------
Message: 1
Date: Sun, 25 Apr 2004 14:14:39 +0200
From: "Peter" <peterderegt@wanadoo.nl>
Subject: [cisco-voip] Cisco voip linked huntgroups
To: <cisco-voip@puck.nether.net>
Message-ID: <00bc01c42abe$e210c840$9600000a@wshenk>
Content-Type: text/plain; charset="iso-8859-1"
Hello,
Does anyone know the procedure to create linked huntgroups in a Cisco Call
manager 3.3(4) envirement?
My procedure:
-Create pilot point
-Create members in huntgroup
-Create in huntgroup at the a huntgroup member as route member
-Toggle TCD service
-Create AC user-huntgroup
The huntgroup are working independent fine, but I when I create a huntgroup
in a huntgroup, the attached huntgroup will not work.
So, I have huntgroup 4444 with members 4565, 5678 and huntgroup number 6754,
the call will only switch to 4565 and 5678 and not the attached huntgroup
6754.
In the huntgroup I attached member with a directory number and not with a user, that's not necessary? And can I attached all the huntgroups under the same AC user?
Can anyone help me with problem?
Thanks in advance!
Regards,
Peter
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20040425/7bf57be7/attachment-0001.html
------------------------------
Message: 2
Date: Sun, 25 Apr 2004 17:27:55 +0200
From: Nicolas Goy <goyman@goyman.com>
Subject: Re: [cisco-voip] VOIP, CME and ISDN BRI problem
To: cisco-voip@puck.nether.net
Message-ID: <1FCABABC-96CD-11D8-AB98-000393481E96@goyman.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Hello,
Now incoming call are correctly routed to phone 1 ( I added
voice-port 1/0/0
translate called 1
)
But when I answer the call, the song quality is absolutly horrible with
a buzzing noise in the background.
Intern calls have very good quality, but ISDN-IP are completly
garbled...
If you have any tips on the one.
I still can't make outgouing calls.
On Apr 22, 2004, at 11:28 PM, Nicolas Goy wrote:
> Hello,
>
> I try to setup voip at our office, I got the following configuration:
>
......
------------------------------
_______________________________________________
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
End of cisco-voip Digest, Vol 14, Issue 31
******************************************
DISCLAIMER:
This message is intended only for the use of the person(s) ('Intended Recipient') to whom it is addressed. It may contain information, which is privileged and confidential. Accordingly any dissemination, distribution, copying or other use of this message or any of its content by any person other than the Intended Recipient may constitute a breach of civil or criminal law and is strictly prohibited. If you are not the Intended Recipient, please contact the sender as soon as possible. Neither Lynx Technology Ltd or the sender accept any responsibility for viruses and its is your responsibility to scan the email and attachments. Any liability arising from any third party acting on any information contained in this email is hereby excluded. Lynx Technology Ltd will hold data provided by you for marketing and promotional purposes unless otherwise advised. If you no longer wish to receive communication from Lynx Technology, please see our Statement of Privacy at www.lynxtec.com.