cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1117
Views
0
Helpful
2
Replies
Highlighted
Beginner

sip-only endpoints calling h323-only external systems (through VCS)

Hi all,

We've got a clustered VCS-C and VCS-E and a number of Cisco/Tandberg codecs. Most of my codecs are h323 or sip but since getting Jabber video, have noticed that sip-only systems (Jabber included) can't call external h323-only devices (systems not registered). Is there any way to make a transform/search rule to interwork calls from sip-only internal systems to h323-only external systems? It'd be really nice if VCS tried both h323 and sip before giving up, but worse case a rule that says anything to uri x needs to be interworked to h323.

(vcs v7.1)

Thanks!

Ken

Everyone's tags (7)
2 REPLIES 2
Highlighted
Beginner

sip-only endpoints calling h323-only external systems (through V

Got it working... Had to change "H.323 <-> SIP interworking mode" from "Registered only" (which I would have though would work) to "On".

Highlighted
Engager

sip-only endpoints calling h323-only external systems (through V

Just out of curiosity. Could you tell us a bit more of the call flow of your failed calls?

Like endpoint (sip) -> vcs-c -> vcs-e -> endpoint (h323)

and how your interworking settings were and are now on both vcs.

Also, what does the search history for the failed calls say on both vcs and how about the state of the traversal zone for sip and h323?

Please remember to rate helpful responses and identify

CreatePlease to create content