From: pbubienczyk@szczesliwice.pl
Date: Thu Jun 24 2004 - 06:14:48 GMT-3
Hi Bhavin
Your solution is working fine. Thank you very much.
Funny thing is that I implemented this command on 2651 (site B) yesterday
and tested voip connection from site A to site B - and the connection failed.
After reading your advice I reintroduced the command today morning and the
connection also failed. Fortunately few minutes later colegue from site B
colled me at site A and connection was working fine.
So I have to implement this command on both sides (IOS upgarde in site A
was neccesary as this command was introduced in 12.2(11)T )
Thx once again - Peter
---- Original Message -----
From: "Bhavin Patel" <BPatel@ibasis.net>
To: <pbubienczyk@szczesliwice.pl>; <mmaslo@optonline.net>
Cc: <ccielab@groupstudy.com>
Sent: Wednesday, June 23, 2004 7:43 PM
Subject: RE: ISDN trunk and VOIP
> Hi Peter,
>
> Dont know if your 2651 supports this command, but you can try this under
> global configuration.
>
> voice service voip
> signaling forward none
>
> Bhavin
>
>
> -----Original Message-----
> From: pbubienczyk@szczesliwice.pl [mailto:pbubienczyk@szczesliwice.pl]
> Sent: Wednesday, June 23, 2004 10:38 AM
> To: mmaslo@optonline.net
> Cc: ccielab@groupstudy.com
> Subject: Re: ISDN trunk and VOIP
>
>
> My gateway is configured in standard way (user side). config from 2651
> below:
>
> interface BRI1/1
> no ip address
> isdn switch-type basic-net3
> isdn incoming-voice voice
> isdn static-tei 0
>
> voice-port 1/0/0
> compand-type a-law
> cptone PL
>
> dial-peer voice 2 pots
> huntstop
> destination-pattern 618588...
> progress_ind alert enable 8
> direct-inward-dial
> port 1/0/0
> !
> dial-peer voice 10 voip
> destination-pattern 22.......
> session target ipv4:x.x.x.x
>
> The configuration DOESN'T change comparing to the running instalation with
> 3640
> (IOS ver 12.2(5))
>
> I think the problem is that in ios ver 12.2(11)T6 the ISDN SETUP message
is
> extended comparing to the 12.2(5) main line. And particulary I don't like
> this
> long Facility string in ISDN SETUP message. In fact PBX doesn't see
anything
>
> after it in the SETUP message (no calling, no called number).
>
> rgds - Peter
>
>
>
> Quoting mmaslo@optonline.net:
>
> > Peter,
> >
> > How is your gateway configured from the ISDN prospective ? Are you
> emulating
> > the network side or user side (default) ?
> >
> > If you have the config handy it would help too.
> >
> > Matt
> >
> > ----- Original Message -----
> > From: pbubienczyk@szczesliwice.pl
> > Date: Wednesday, June 23, 2004 7:03 am
> > Subject: ISDN trunk and VOIP
> >
> > > I've got the problem with my VOIP network
> > >
> > > I've two gateways (2651 with 12.2(11)T6 and 2621XM with
> > > 12.2(8)T5), they are
> > > connected with two PBX Alcatel 4400 by ISDN BRI(2651) and
> > > PRI(2621XM) trunks.
> > >
> > > I've problem with the facility message in ISDN SETUP message.
> > > Seems like PBX
> > > don't like it and not accepting the connection.
> > >
> > > Previously BRI trunk (now on 2561) ran on 3640(with 12.2(5)) and
> > > my VOIP was
> > > working fine, and I think that there was no facility messages in
> > > ISDN SETUP.
> > >
> > > Somebody knows how to get this facility out of ISDN SETUP message,
> > > or how to
> > > fix the problem???
> > >
> > > Log from 2651:
> > >
> > > Jun 23 09:33:13: ISDN BR1/0 Q931: TX -> SETUP pd = 8 callref = 0x24
> > > Bearer Capability i = 0x8090A3
> > > Standard = CCITT
> > > Transer Capability = Speech
> > > Transfer Mode = Circuit
> > > Transfer Rate = 64 kbit/s
> > > Channel ID i = 0x83
> > > Facility i =
> > >
> >
>
0x9E0100036774640000002E49414D2C0D0A4743492C36626638663133346334316531316438
> 3933
> > > 31636164386532346238646132310D0A0D0A
> > > - Unknown Service Discriminator
> > > Calling Party Number i = 0x0181, '225852536'
> > > Plan:ISDN, Type:Unknown
> > > Called Party Number i = 0xA1, '817'
> > > Plan:ISDN, Type:National
> > > High Layer Compat i = 0x9181
> > > Jun 23 09:33:13: ISDN BR1/0 Q931: RX <- STATUS pd = 8 callref = 0xA4
> > > Cause i = 0x81E41C - Invalid information element contents
> > > Call State i = 0x06
> > > Jun 23 09:33:13: ISDN BR1/0 Q931: TX -> RELEASE pd = 8 callref = 0x24
> > > Cause i = 0x80E5 - Message not compatible with call state
> > >
> > >
> > > thx - Peter
> > >
> > >
This archive was generated by hypermail 2.1.4 : Sat Jul 03 2004 - 19:40:49 GMT-3