RE: VOIP Sessions - Source Interface

From: Scott Morris (swm@emanon.com)
Date: Thu Jun 26 2003 - 11:04:57 GMT-3


Must be a problem in your mailer.... *shrug*

The header on mine looks normal:

-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
sadame@unitel.co.kr
Sent: Thursday, June 26, 2003 9:25 AM
To: ccielab@groupstudy.com; danielcgs@imc.net.au
Subject: Re: VOIP Sessions - Source Interface

 hi there & daniel
<<<snipped>>>

-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Ronald Fugate
Sent: Thursday, June 26, 2003 9:49 AM
To: ''; ccielab@groupstudy.com; danielcgs@imc.net.au
Subject: RE: VOIP Sessions - Source Interface

Whats going on here.

This email says it was sent from me.

I did not send this.

Anyone have any ideas.

-----Original Message-----
From: Ronald Fugate [mailto:sadame@unitel.co.kr]
Sent: Thursday, June 26, 2003 8:39 AM
To: ccielab@groupstudy.com; danielcgs@imc.net.au
Subject: Re: VOIP Sessions - Source Interface

 hi there & daniel

 your concern was solved at groupstudy mailing-list by someone,, I
cann't remember who.. the key command is "h323-gateway voip bind
srcaddr <ip_address>" that is interface command

 for example

 lo0 172.16.2.1 R1 e1(10.1.1.1) -------------------- e2(10.1.1.2) R2 lo0
172.16.1.1

  the configure on R1 is as following
 !
 R1
  !
  interface loopback 0
   ip address 172.16.2.1 255.255.255.0
   h323-gateway voip bind srcaddr 172.16.2.1 -> interface command
  !
  dial-peer voice 11 pots
   destination-pattern 1111...
   port 1/0/0
  !
  dial-peer voice 22 voip
   destination-pattern 2222...
   session target ipv4:172.16.1.1
   ip preference 5
  !

you can find the way to solve your concern...

R2> show call active voice 8m7I=C
 onnectionId[0x65B8E25C 0x14F211CC 0x8024B9BB 0xB6B4DD0A]
IncomingConnectionId[0x65B8E25C 0x14F211CC 0x8024B9BB 0xB6B4DD0A]
RemoteIPAddress=172.16.2.1 --> this ip address is the loopback of R1
RemoteUDPPort=17272 RemoteSignallingIPAddress=137.12.22.2 --> this ip
address is the loopback of R1 RemoteSignallingPort=1720
RemoteMediaIPAddress=137.12.22.2 --> this ip address is the loopback of
R1 RemoteMediaPort=17272 RoundTripDelay=0 ms SelectedQoS=best-effort
tx_DtmfRelay=inband-voice FastConnect=TRUE ..

search the document on the CD-ROM or WEB for more detail of this
command..

you know this way is very effective for VOIPsession sustenance even if
the link-fail occurs.. but you must have redundancy-path



This archive was generated by hypermail 2.1.4 : Fri Jul 04 2003 - 11:11:10 GMT-3