Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

SBC Redundant Adjacencies and remote address

Hello all.

I have an SBC (ace20) deployed in unified model.

I have a costumer with 2 Call managers. This costumer is behind NAT and one call manager has an IP address of 10.245.3.1 and the othet one is 10.245.3.2; I tried the following config to acheive redundancy (the ideia is to config routing in order to always choose A and if routing fails then choose B, with all costumer network behind 10.245.3.0/28):

adjacency sip A

  nat force-on

  signalling-address ipv4 10.245.2.1

  signalling-port 5060

  remote-address ipv4 10.245.3.0 255.255.255.240

  signalling-peer 10.245.3.1

  signalling-peer-port 5060

  media-bypass-forbid

adjacency sip B

  nat force-on

  signalling-address ipv4 10.245.2.1

  signalling-port 5060

  remote-address ipv4 10.245.3.0 255.255.255.240

  signalling-peer 10.245.3.2

  signalling-peer-port 5060

  media-bypass-forbid

The thing is that SBC doesn´t allow adjacency " an attempt was made to configure an adjacency that has the same local and remote addresses as an existing adjacency".

Why can´t this be done? I believe that the remote-address command is used to specified the ip addresses for the phones allowed to communicate with SBC, so it should work just fine.

Can anyone give a hand on this?

Thanks in advance.

Best regards,

Joao Ribau.

1 REPLY
New Member

SBC Redundant Adjacencies and remote address

Hello.

I have being talking to a friend and he told me that the remote-address is not for phones but for other signaling devices (for instance other call managers), so I change the config to:

adjacency sip A

  nat force-on

  signalling-address ipv4 10.245.2.1

  signalling-port 5060

  remote-address ipv4 10.245.3.1 255.255.255.255

  signalling-peer 10.245.3.1

  signalling-peer-port 5060

  media-bypass-forbid

adjacency sip B

  nat force-on

  signalling-address ipv4 10.245.2.1

  signalling-port 5060

  remote-address ipv4 10.245.3.2 255.255.255.255

  signalling-peer 10.245.3.2

  signalling-peer-port 5060

  media-bypass-forbid

This way I think it should work.

Any feedback would be appreciated.

Regards,

Joao

236
Views
0
Helpful
1
Replies
CreatePlease to create content