CUBE - send SIP signaling down a different path

[dshumake]

Hello All,

First this is what I am trying to do.

int: 0/0/0   inbound from ATT

int: 0/0/1   outbound to avaya

int: 0/0/2   outbound to proxy server

incoming call 

   signaling path:   att --> cube --> proxy server --> cube -->  avaya (agent)

    media path:       att --> cube -->  avaya (agent)

Does any have an example on how to build the voice dialpeers for this going to proxy servers and avaya?

[Steven L]

sip bind commands is what you need.

bind control source-interface int 0/0/2

bind media source-interface int 0/0/1

that being said, i dont follow the cube>proxy>cube>avaya flow.

Are these 2 different cube routers?

[dshumake]

forgot to add,  this is one router

[Steven L]

ok...i believe i answered your original question. so unless it is not working, i am not sure i NEED to understand what you are doing with the bounce off the proxy back to the CUBE.

Are you still having an issue?

[dshumake]

avaya flow mean connecting to Avaya ASM

[Roger Kallberg]

I think what Steve meant is that you have 2 SBCs (Cubes) mentioned in your outline of the call path.

“signaling path: att --> cube --> proxy server --> cube -->  avaya (agent)”

[Steven L]

yes. that is correct.

[Nithin Eluvathingal]

@Roger Kallberg  What I understood is , he is asking if he can bind the media through one port and signalling through another port which go through a  proxy.

@dshumake Not sure why you need to do this. But  I think   this will make things more complicated. 

[Roger Kallberg]

I understood the path @Nithin Eluvathingal, it was @Steven L that asked about the second SBC in the described path.

[dshumake]

this is one cube...

with be routing the signaling traffic to a proxy (3rd party device/ application) then flow back to cube on the call center agent on Avaya.

with is a special app to monitor calls  if that make sense.