H.323 Transferring and Conferencing

[clindberg]

I'm having an issue using H.323 trunks for off switch transferring and confereincing. Are there limitiation I am unaware of. I can conference, but the two parties cannot hear each other. I also am having trouble tranferring and inbound call back out. I am assuing this is related to my confereincing issue.

 

[amriddle01]

Make sure Direct Media path is off in the trunk settings

ACSS (SME)
APSS (SME)

http://www.ipoffice.tel

 

[clindberg]

Tricky, because if I'm not mistaken that would consume a VCM, something I was trying to avoid. I don't mind consuming a VCM for conferencing purposes. But if it's an all or none situation I've negated the whole purpose for using the H.323 gateway in teh first place.

 

[clindberg]

I suppose I coulud create multiple H323 trunks to the same gateway, one with direct media and one without. Then create some kind of short code that directs all conferences and transfers out the "no direct media path" trunk. Any ideas how I can accomplish this????

 

[amriddle01]

It will work with Direct media path enabled for transfers if you have your routing setup correctly, if once transferred the devices can't hear each other it's not the IP office at fault as it has dropped itself out the equation and the two devices are trying to talk direct. But for conferencing the conference chip is on the IP offices TDM bus and so requires a VCM for use

ACSS (SME)
APSS (SME)

http://www.ipoffice.tel

 

[clindberg]

Thanks for your time AMRiddle

The h323 gateway is betwen an IP office and a Cisco VG200 H323 gateway. When transfering with Direct media path on, doesn't that mean that the Cisco gateway needs to pass the call between itself? Maybe it's a Cisco configuration at that point?

 

[amriddle01]

Indeed it is, Direct media path is just what it says, send the traffic direct between the two endpoints not via the IP Office, if the most direct/default route for the two devices is the Cisco then that is what needs to be configured to route the traffic

ACSS (SME)
APSS (SME)

http://www.ipoffice.tel

 

[amriddle01]

Also clindberg, if the endpoints all use the same codec even if you turn DMP off it will not use a VCM channel as the system will just use RTP relay to route the traffic for you (IP Office needs to be 4.0+ )

ACSS (SME)
APSS (SME)

http://www.ipoffice.tel

 

[clindberg]

Oh, so that means I can turn off direct media path and still save the VCM. I guess I'll do that if it works.

 

[amriddle01]

It will work as long as they use the same codec, watch the call in System Status and it will say RTP relay in the call details

ACSS (SME)
APSS (SME)

http://www.ipoffice.tel

 

[clindberg]

Tried this and still used 2 VCM channels. Note that originator and receiver codec are same. I assume that "RTP Connection Type" was supposed to say "RELAY"

XXX have been added to content to protect the innocent


------------------------------------------------------------

Call Details

Call Ref: 81 Call length: 00:13:10

Originator
Current State: Connected Time in State: 00:12:59
Currently at: Extn 1199, XXXXX XXXXXXX
Button Number: 1
Button Type: Call Appearance (CA)
Round Trip Delay: 97ms
Receive Jitter: 0.6ms
Receive Packet Loss Fraction: 0%
Transmit Jitter: 2.5ms
Transmit Packet Loss Fraction: 0%
Dialed Digits: 81XXXXXXXXXX
Codec: G711 Mu

Destination
Current State: Connected Time in State: 00:12:59
Trunk Used: Line: 10 H.323 192.168.XX.X Channel: 1
Digits sent to Central Office: 91XXXXXXXXXX
Caller ID sent from Central Office: 81XXXXXXXXXX
Codec: G711 Mu

Round Trip Delay: 1ms
Receive Jitter: 0.8ms
Receive Packet Loss Fraction: 0%
Transmit Jitter: 64ms
Transmit Packet Loss Fraction: 0%

Call target / Routing information
Short Code matched: 8XXXXXXXXXXX, Dial, System
RTP Connection Type: VCM
Call Recording: No
Redirected to Twin: No
Routed across SCN trunk: No
Retargeting Count: 0

Trace Output: