[cisco-voip] IPCC Express - JTAPI Triggers
Martin Fischer
mfischer at avodaq.com
Tue Jul 27 11:04:09 EDT 2004
Just a suggestion.
Try to build a Translation Pattern in the Callmanager
to translate that new number into the existing DN of the Route Point.
Best Regards
Martin
________________________
Martin Fischer
IT- Consultant
avodaq AG
professional network solutions
Moostr. 16
82319 Starnberg
Tel.: +49 8151 36858371
Mobil.: +49163 7788271
Fax.: +49 8151 918382
<mailto:mfischer at avodaq.com>
http://www.avodaq.com
-----Ursprüngliche Nachricht-----
Von: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] Im Auftrag von cisco-voip-request at puck.nether.net
Gesendet: Dienstag, 27. Juli 2004 16:17
An: cisco-voip at puck.nether.net
Betreff: cisco-voip Digest, Vol 17, Issue 39
Send cisco-voip mailing list submissions to
cisco-voip at 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 at puck.nether.net
You can reach the person managing the list at
cisco-voip-owner at 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. Re: MGCP, SIP and H.323 (Oleg Shevtsov)
2. Connecting H.323 clients to CCM-4.0
(Yehavi Bourvine +972-8-9489444)
3. Connection SIP phones to CCM-4.0 (Yehavi Bourvine +972-8-9489444)
4. Re: Connecting H.323 clients to CCM-4.0 (Oleg Shevtsov)
5. Qsig (Voll, Scott)
6. RE: IPCC Express - JTAPI Triggers (Voll, Scott)
7. Re: IPCC Express - JTAPI Triggers (Anthony Mendoza)
8. Re: IPCC Express - JTAPI Triggers (Anthony Mendoza)
----------------------------------------------------------------------
Message: 1
Date: Tue, 27 Jul 2004 11:21:23 +0300
From: Oleg Shevtsov <sat at orion.interexc.com>
Subject: [cisco-voip] Re: MGCP, SIP and H.323
To: ?smail CAN <ismailcan_net at yahoo.com>
Cc: cisco-voip at puck.nether.net
Message-ID: <20040727082123.GA47054 at interexc.com>
Content-Type: text/plain; charset=koi8-r
Hello Ismail,
On Tue, Jul 27, 2004 at 12:04:02AM -0700, Ýsmail CAN wrote:
>Hello,
>
>We have Cisco AS5350 Universal Gateways.
>I want to learn whether gw supports at the same time two or three protocols.( MGCP, SIP and H.323) or not.
We have Cisco 5300 and it works with SIP and h323 configured, and it
answers to MGCP.
Our major protocols are H323 and SIP, so I can tell you about these two
protocols first. In dial-peer configuration for outbound voip calls they
differs only by "session protocol" command.
The default protocol is h323, but you can force dial-peer to SIP using
"session protocol sipv2".
Major IOSes allows to receive calls by SIP using the same dial-peers as
for h323 calls.
About the MGCP. I know that you can use it with another protocols like
SIP ans H323. But as I know, for MGCP you will need PRI with MGCP
signalling. In out lab we made such signalling using pair 5300-5300.
controller E1 3
framing NO-CRC4
pri-group timeslots 1-31 service mgcp
gw-accounting aaa
But I'm not sure that in this schema we can receive calls on second
gateway and send them using H323 or SIP.
If you know much more better how to set up MGCP on c53xx -- give me to know.
>For example, if gw communicates with softswitch with MGCP and can it communicate with gk or another gw with H323 or SIP.
>
>Can I configure in order to use two or three protocols at the same time on gw?
I need more details about what are you going to configure.
--
Oleg Shevtsov
Chief of NOC InterExchange Carrier
phone +380442399740
mobile +380672341642
fax +380442468910
http://www.ixcaccounting.com
------------------------------
Message: 2
Date: Tue, 27 Jul 2004 13:39 +0200
From: Yehavi Bourvine +972-8-9489444 <YEHAVI at vms.HUJI.AC.IL>
Subject: [cisco-voip] Connecting H.323 clients to CCM-4.0
To: cisco-voip at puck.nether.net
Message-ID: <27072004133926 at HUJIVMS>
Content-Type: Text/plain; charset=US-ASCII
Hello,
I have a few H.323 clients which I want to connect to CCM-4.0; I've started
with ATA-186 in H.323 mode (I know it can run Skinny as well, but it is easier
for me to try H.323 with it).
I've defined the CCM address as the gatekeeper on the ATA-186, and I see it
tries to register on port 1719 while the CCM does not listen on that port. Any
idea what can be done?
Thanks, __Yehavi:
------------------------------
Message: 3
Date: Tue, 27 Jul 2004 13:41 +0200
From: Yehavi Bourvine +972-8-9489444 <YEHAVI at vms.HUJI.AC.IL>
Subject: [cisco-voip] Connection SIP phones to CCM-4.0
To: cisco-voip at puck.nether.net
Message-ID: <27072004134138 at HUJIVMS>
Content-Type: Text/plain; charset=US-ASCII
Hello,
I have CCM-4.0 and SIPproxy-4.0 installed; the local dealer told me in
advance that they have no idea how to config the SIPproxy, so I am alone...
I tired first directing the SIP phone to the CCM as its registrar. It fails
to register (Method not allowed) but can generate outgoing calls. When I
direct it to the SIPproxy it can communicate with the other phones on the
proxy. Where can I find the definitions on the CCM and the proxy in order to
connect them (probably via a trunk)?
Thanks, __Yehavi:
------------------------------
Message: 4
Date: Tue, 27 Jul 2004 13:44:56 +0300
From: Oleg Shevtsov <sat at interexc.com>
Subject: [cisco-voip] Re: Connecting H.323 clients to CCM-4.0
To: Yehavi Bourvine +972-8-9489444 <YEHAVI at vms.HUJI.AC.IL>
Cc: cisco-voip at puck.nether.net
Message-ID: <20040727104456.GC47054 at interexc.com>
Content-Type: text/plain; charset=us-ascii
Hello
On Tue, Jul 27, 2004 at 01:39:00PM +0200, Yehavi Bourvine +972-8-9489444 wrote:
>
>Hello,
>
> I have a few H.323 clients which I want to connect to CCM-4.0; I've started
>with ATA-186 in H.323 mode (I know it can run Skinny as well, but it is easier
>for me to try H.323 with it).
>
> I've defined the CCM address as the gatekeeper on the ATA-186, and I see it
>tries to register on port 1719 while the CCM does not listen on that port. Any
>idea what can be done?
> Thanks, __Yehavi:
CM is not a GK and it doesn't support GK functions
GK: 0.0.0.0
GW1: CM's IP
GW2: CM's IP
--
Oleg Shevtsov
Chief of NOC InterExchange Carrier
phone +380442399740
mobile +380672341642
fax +380442468910
http://www.ixcaccounting.com
------------------------------
Message: 5
Date: Tue, 27 Jul 2004 06:57:40 -0700
From: "Voll, Scott" <Scott.Voll at wesd.org>
Subject: [cisco-voip] Qsig
To: <cisco-voip at puck.nether.net>
Message-ID: <407055A92CECCB499C922A2D35FC19A6013F32D8 at apollo.wesd.org>
Content-Type: text/plain; charset="us-ascii"
I'm directing this more toward a Cisco person:
bug ID CSCec33755
http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCec33755+
&Submit=Search
I have a PBX connected to a cisco 2600 and originally tried to get it
working with MGCP. The Tac engineer said:
*************************
"After talking with our software developers I found we do not support
ECMA qsig. We only support ISO qsig. And for the basic call feature we
comply with the 3rd edition (2000) . Make sure your PBX qsig software
is not using the 1995 version if when using ISO qsig you still get same
problem.
Also apparently there are two versions of ECMA qsig one is kind of
similar to ISO qsig so that would be why your local calls work but
external calls do not."
**********************
So Based on this bug ID, do I understand that I should now be able to
use MGCP? I would really like to get away from having to use H323. How
do I find out; open a TAC case?
How do I find out which call signing MGCP supports with Qsig?
Thanks
Scott
------------------------------
Message: 6
Date: Tue, 27 Jul 2004 07:06:26 -0700
From: "Voll, Scott" <Scott.Voll at wesd.org>
Subject: RE: [cisco-voip] IPCC Express - JTAPI Triggers
To: "Voll, Scott" <Scott.Voll at wesd.org>, "Anthony Mendoza"
<amendoza at Niku.com>, <cisco-voip at puck.nether.net>
Message-ID: <407055A92CECCB499C922A2D35FC19A6013F32D9 at apollo.wesd.org>
Content-Type: text/plain; charset="us-ascii"
Sorry Anthony-
I wasn't able to get on my CRS server when I replied.
I'm actually using the same script and making two different applications
in order to do the same thing for two different TAC numbers.
Have you made the second DN a CTI Route Point in CM?
Scott
_____
From: Voll, Scott
Sent: Monday, July 26, 2004 8:28 PM
To: Anthony Mendoza; cisco-voip at puck.nether.net
Subject: RE: [cisco-voip] IPCC Express - JTAPI Triggers
so it's associated to both the jtapi and RM users?
-----Original Message-----
From: Anthony Mendoza [mailto:amendoza at Niku.com]
Sent: Mon 7/26/2004 7:02 PM
To: Voll, Scott; cisco-voip at puck.nether.net
Cc:
Subject: RE: [cisco-voip] IPCC Express - JTAPI Triggers
First thing I checked...my current number isn't associated to
the rmjtapi user so I didn't think of adding the 2nd one to it..However
both ports/extensions are associated with the jtapi user (used to create
the triggers).
_____
From: Voll, Scott [mailto:Scott.Voll at wesd.org]
Sent: Monday, July 26, 2004 6:58 PM
To: Anthony Mendoza; cisco-voip at puck.nether.net
Subject: RE: [cisco-voip] IPCC Express - JTAPI Triggers
have you checked your rmuser?
-----Original Message-----
From: Anthony Mendoza [mailto:amendoza at Niku.com]
Sent: Mon 7/26/2004 5:52 PM
To: cisco-voip at puck.nether.net
Cc:
Subject: [cisco-voip] IPCC Express - JTAPI Triggers
CONFIDENTIALITY NOTICE: The information contained in this message and
or attachments is intended only for the person or entity to which it
is addressed and may contain confidential and/or privileged material.
Any review, retransmission, dissemination, copying, or other use of
this information by persons or entities other than the intended
recipient is prohibited. If you received this e-mail or its
attachments in error, please contact the sender and delete the
material from any system and destroy any copies.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20040727/58bad38e/attachment-0001.html
------------------------------
Message: 7
Date: Tue, 27 Jul 2004 07:13:14 -0700
From: Anthony Mendoza <amendoza at Niku.com>
Subject: Re: [cisco-voip] IPCC Express - JTAPI Triggers
To: "Voll, Scott" <Scott.Voll at wesd.org>
Cc: cisco-voip at puck.nether.net
Message-ID: <410662FA.8050203 at niku.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
No, just to the jtapi user...
--
Anthony Mendoza
Senior Infrastructure Manager
t: 650-298-5955
c: 510-579-1909
f: 650-701-2730
e: amendoza at niku.com
On 7/26/2004 8:28 PM, Voll, Scott wrote:
> so it's associated to both the jtapi and RM users?
>
> -----Original Message-----
> *From:* Anthony Mendoza [mailto:amendoza at Niku.com]
> *Sent:* Mon 7/26/2004 7:02 PM
> *To:* Voll, Scott; cisco-voip at puck.nether.net
> *Cc:*
> *Subject:* RE: [cisco-voip] IPCC Express - JTAPI Triggers
>
> First thing I checked...my current number isn't associated to the
> rmjtapi user so I didn't think of adding the 2nd one to it..However
> both ports/extensions are associated with the jtapi user (used to
> create the triggers).
>
> ------------------------------------------------------------------------
> *From:* Voll, Scott [mailto:Scott.Voll at wesd.org]
> *Sent:* Monday, July 26, 2004 6:58 PM
> *To:* Anthony Mendoza; cisco-voip at puck.nether.net
> *Subject:* RE: [cisco-voip] IPCC Express - JTAPI Triggers
>
> have you checked your rmuser?
>
> -----Original Message-----
> *From:* Anthony Mendoza [mailto:amendoza at Niku.com]
> *Sent:* Mon 7/26/2004 5:52 PM
> *To:* cisco-voip at puck.nether.net
> *Cc:*
> *Subject:* [cisco-voip] IPCC Express - JTAPI Triggers
>
>
>
> CONFIDENTIALITY NOTICE: The information contained in this message and
> or attachments is intended only for the person or entity to which it
> is addressed and may contain confidential and/or privileged material.
> Any review, retransmission, dissemination, copying, or other use of
> this information by persons or entities other than the intended
> recipient is prohibited. If you received this e-mail or its
> attachments in error, please contact the sender and delete the
> material from any system and destroy any copies.
>
CONFIDENTIALITY NOTICE: The information contained in this message and
or attachments is intended only for the person or entity to which it
is addressed and may contain confidential and/or privileged material.
Any review, retransmission, dissemination, copying, or other use of
this information by persons or entities other than the intended
recipient is prohibited. If you received this e-mail or its
attachments in error, please contact the sender and delete the
material from any system and destroy any copies.
------------------------------
Message: 8
Date: Tue, 27 Jul 2004 07:14:55 -0700
From: Anthony Mendoza <amendoza at Niku.com>
Subject: Re: [cisco-voip] IPCC Express - JTAPI Triggers
To: "Voll, Scott" <Scott.Voll at wesd.org>
Cc: cisco-voip at puck.nether.net
Message-ID: <4106635F.8070602 at niku.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Yes, the 2nd DN is a CTI route point in CM..... Prior to that I tested
it by making it an extension on my phone and it rings through fine (so I
know the config for the DID is working)... Something I was wondering is
what is the association between apps and scripts..I was assuming 1 to 1,
but when would you not have a 1 to 1 (like in your case)?
--
Anthony Mendoza
On 7/27/2004 7:06 AM, Voll, Scott wrote:
> Sorry Anthony-
>
>
>
> I wasn't able to get on my CRS server when I replied.
>
>
>
> I'm actually using the same script and making two different applications
> in order to do the same thing for two different TAC numbers.
>
>
>
> Have you made the second DN a CTI Route Point in CM?
>
>
>
> Scott
>
>
>
> ------------------------------------------------------------------------
>
> *From:* Voll, Scott
> *Sent:* Monday, July 26, 2004 8:28 PM
> *To:* Anthony Mendoza; cisco-voip at puck.nether.net
> *Subject:* RE: [cisco-voip] IPCC Express - JTAPI Triggers
>
>
>
> so it's associated to both the jtapi and RM users?
>
> -----Original Message-----
> *From:* Anthony Mendoza [mailto:amendoza at Niku.com]
> *Sent:* Mon 7/26/2004 7:02 PM
> *To:* Voll, Scott; cisco-voip at puck.nether.net
> *Cc:*
> *Subject:* RE: [cisco-voip] IPCC Express - JTAPI Triggers
>
> First thing I checked...my current number isn't associated to the
> rmjtapi user so I didn't think of adding the 2nd one to it..However
> both ports/extensions are associated with the jtapi user (used to
> create the triggers).
>
>
>
> ------------------------------------------------------------------------
>
> *From:* Voll, Scott [mailto:Scott.Voll at wesd.org]
> *Sent:* Monday, July 26, 2004 6:58 PM
> *To:* Anthony Mendoza; cisco-voip at puck.nether.net
> *Subject:* RE: [cisco-voip] IPCC Express - JTAPI Triggers
>
> have you checked your rmuser?
>
> -----Original Message-----
> *From:* Anthony Mendoza [mailto:amendoza at Niku.com]
> *Sent:* Mon 7/26/2004 5:52 PM
> *To:* cisco-voip at puck.nether.net
> *Cc:*
> *Subject:* [cisco-voip] IPCC Express - JTAPI Triggers
>
>
>
> CONFIDENTIALITY NOTICE: The information contained in this message and
> or attachments is intended only for the person or entity to which it
> is addressed and may contain confidential and/or privileged material.
> Any review, retransmission, dissemination, copying, or other use of
> this information by persons or entities other than the intended
> recipient is prohibited. If you received this e-mail or its
> attachments in error, please contact the sender and delete the
> material from any system and destroy any copies.
>
CONFIDENTIALITY NOTICE: The information contained in this message and
or attachments is intended only for the person or entity to which it
is addressed and may contain confidential and/or privileged material.
Any review, retransmission, dissemination, copying, or other use of
this information by persons or entities other than the intended
recipient is prohibited. If you received this e-mail or its
attachments in error, please contact the sender and delete the
material from any system and destroy any copies.
------------------------------
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
End of cisco-voip Digest, Vol 17, Issue 39
******************************************
More information about the cisco-voip
mailing list