Table of Contents
Telstra TelePresence B2B Config
Dial Plan
Dial Pattern | Descriptions | FNN |
---|---|---|
912266591359 | TATA International - Mumbai Static | N2019334R |
18774418282 | TATA International - Meet-Me Service | N2019334R |
442031061789 | TATA International - Stratford Static | N2019334R |
16312095439 | TATA International - New York Static | N2019334R |
18774418282∗∗XXXXXX | TATA Exchange | N2019334R |
26269508[5-9] | NBN CO LIMITED | N2015708R |
38662829X | NBN CO LIMITED | N2015708R |
29927428X | NBN CO LIMITED | N2015708R |
e164 - Translation Pattern
Pattern | Descriptions |
---|---|
0.[2378]! | Dropping leading 0 for 02,03,07,08 |
0011.18666287435∗∗XXXXXXXX | Dropping 0011 prefix for Cisco 3.0 Meet-Me Service |
0011.18669863384∗∗XXXXXXXX | Dropping 0011 prefix for AT-T 3.0 Meet-Me Service |
0011.[1-9]! | Dropping 0011 prefix for all other international number |
1800011080∗∗.[56]XXXXXXX | Dropping 1800…∗∗ prefix for Hosted Multipoint Bridge Service |
61.[2378]! | Dropping Oz 61 prefix |
Config Detail
Customer Detail
Name: | Woolworth |
---|---|
VPN FNN: | N2012648R |
Publisher IP: | 10.56.124.70 |
Subscriber IP: | 10.56.124.71 |
Number Range: | 2888793XX |
SBC Detail
CSD001 | CSD002 | |
---|---|---|
Port FNN: | N2031212R | N2031208R |
CE01 IP: | 10.0.68.114/30 | 10.0.68.118/30 |
CE02 IP: | 10.0.68.113/30 | 10.0.68.117/30 |
VLAN: | 1100 | 1100 |
SBC to B2B-CUCM Signaling IP: | <192.168.1.X> | <192.168.2.X> |
SBC Configuration
VRF
vrf definition <VPN-FNN> description <Customer Name Name> rd <XXXXX:XX> ! address-family ipv4 exit-address-family !
Interface to IPMAN
interface GigabitEthernet1/0/0.<VLAN> description <Customer Name> vrf forwarding <VPN-FNN> encapsulation dot1Q <VLAN> ! *** On CSD-001 *** ip address <CE01-IP> 255.255.255.252 ! *** On CSD-002 *** ip address <CE02-IP> 255.255.255.252 ip access-group signalling_and_media_only in no ip unreachables no cdp enable no shut !
IP Routing
! *** On CSD-001 *** ip route vrf <VPN-FNN> 0.0.0.0 0.0.0.0 <PE01-IP> ! *** On CSD-002 *** ip route vrf <VPN-FNN> 0.0.0.0 0.0.0.0 <PE02-IP>
SBC Interface
interface SBC<FNN> description <Customer Name> vrf forwarding <VPN-FNN> ! *** On CSD-001 *** ip address <192.168.1.X> 255.255.255.255 secondary vrf b2bCore ip address 147.132.191.18 255.255.255.252 ! *** On CSD-002 *** ip address <192.168.2.X> 255.255.255.255 secondary vrf b2bCore ip address 147.132.191.22 255.255.255.252 !
Media Address
! *** On CSD-001 *** sbc csd-001 ! *** On CSD-002 *** sbc csd-002 ! *** On CSD-001 *** media-address ipv4 147.132.191.18 vrf <VPN-FNN> ! *** On CSD-002 *** media-address ipv4 147.132.191.22 vrf <VPN-FNN>
Adjacency
! *** On CSD-001 *** sbc csd-001 ! *** On CSD-002 *** sbc csd-002 sbe adjacency sip <VPN-FNN>_ccp vrf b2bCore account <VPN-FNN>_b2bCore ! *** On CSD-001 *** signaling-address ipv4 <192.168.1.X> ! *** On CSD-002 *** signaling-address ipv4 <192.168.2.X> signaling-port 5060 remote-address ipv4 10.126.180.68 255.255.255.255 signaling-peer 10.126.180.68 preferred-transport tcp ping-enable ping-interval 50 ping-fail-count 2 ping-lifetime 5 statistics method summary nat force-off attach ! adjacency sip <VPN-FNN>_ccs vrf b2bCore account <VPN-FNN>_b2bCore ! *** On CSD-001 *** signaling-address ipv4 <192.168.1.X> ! *** On CSD-002 *** signaling-address ipv4 <192.168.2.X> signaling-port 5060 remote-address ipv4 10.126.180.69 255.255.255.255 signaling-peer 10.126.180.69 preferred-transport tcp ping-enable ping-interval 50 ping-fail-count 2 ping-lifetime 5 statistics method summary nat force-off attach ! adjacency sip <VPN-FNN>_pub vrf <VPN-FNN> account <VPN-FNN>_cust ! *** On CSD-001 *** signaling-address ipv4 147.132.191.18 ! *** On CSD-002 *** signaling-address ipv4 147.132.191.22 signaling-port 5060 remote-address ipv4 <publisher-ip> 255.255.255.255 signaling-peer <publisher-ip> preferred-transport tcp ping-enable ping-interval 50 ping-fail-count 2 ping-lifetime 5 statistics method summary nat force-off attach ! adjacency sip <VPN-FNN>_sub vrf <VPN-FNN> account <VPN-FNN>_cust ! *** On CSD-001 *** signaling-address ipv4 147.132.191.18 ! *** On CSD-002 *** signaling-address ipv4 147.132.191.22 signaling-port 5060 remote-address ipv4 <subscriber-ip> 255.255.255.255 signaling-peer <subscriber-ip> preferred-transport tcp ping-enable ping-interval 50 ping-fail-count 2 ping-lifetime 5 statistics method summary nat force-off attach
Call Policy Routing
! *** On CSD-001 *** sbc csd-001 ! *** On CSD-002 *** sbc csd-002 sbe call-policy-set <1-2> ! *** Copy existing policy no complete rtg-src-account-table SOURCE-ACCT-TABLE entry <n> action next-table <VPN-FNN>_cust match-account <VPN-FNN>_b2bCore entry <n+1> action next-table <VPN-FNN>_b2bCore match-account <VPN-FNN>_cust rtg-least-cost-table <VPN-FNN>_b2bCore entry 1 action complete dst-adjacency <VPN-FNN>_ccs cost 10 entry 2 action complete dst-adjacency <VPN-FNN>_ccp cost 20 rtg-least-cost-table <VPN-FNN>_cust entry 1 action complete dst-adjacency <VPN-FNN>_sub cost 10 entry 2 action complete dst-adjacency <VPN-FNN>_pub cost 20 complete active-call-policy-set <1-2>
CUCM Configuration
- Create dedicated Partition for customer
- Add customer parition to “Incoming_b2b” Calling Search Space
- Create dedicate Location for each customer assign to SIP trunk
- SIP trunk to CSD-001 and CSD-002 for SIP adjacency to the SBC, assign it the Customer dedicated location
- Create a dedicate Route Group for each customer, add the two customer adjacency SIP trunks to the route group and make CSD-002 the primary
- Create a dedicate Route List for each customer, add the customer Route Group to the Route List
- Create Route Pattern to Customer Numbering Range, put that into the customer partition
Troubleshooting
- Show adjacency matching rule
cjtp-csd-002#show sbc csd-002 sbe call-policy-set active SBC Service "csd-002" Policy set 1 Active policy set : Yes First Number Analysis table : First call routing table : SOURCE-ACCT-TABLE First reg routing table : Table Name : N2031208R_b2bCore Class : Routing Table type : rtg-least-cost Total Call-policy Failures : 0 (0 *) Entry Match Value Destination Adjacency Action ----- ----------- --------------------- ------ 1 No match value N2031208R_ccs Routing complete 2 No match value N2031208R_ccp Routing complete Table Name : N2031208R_cust Class : Routing Table type : rtg-least-cost Total Call-policy Failures : 0 (0 *) Entry Match Value Destination Adjacency Action ----- ----------- --------------------- ------ 1 No match value N2031208R_sub Routing complete 2 No match value N2031208R_pub Routing complete Table Name : N2067088R_b2bCore Class : Routing Table type : rtg-least-cost Total Call-policy Failures : 0 (0 *) Entry Match Value Destination Adjacency Action ----- ----------- --------------------- ------ 1 No match value N2067088R_ccs Routing complete 2 No match value N2067088R_ccp Routing complete Table Name : N2067088R_cust Class : Routing Table type : rtg-least-cost Total Call-policy Failures : 0 (0 *) Entry Match Value Destination Adjacency Action ----- ----------- --------------------- ------ 1 No match value N2067088R_pub Routing complete Table Name : N2728701R_b2bCore Class : Routing Table type : rtg-least-cost Total Call-policy Failures : 0 (0 *) Entry Match Value Destination Adjacency Action ----- ----------- --------------------- ------ 1 No match value N2728701R_ccs Routing complete 2 No match value N2728701R_ccp Routing complete Table Name : N2728701R_cust Class : Routing Table type : rtg-least-cost Total Call-policy Failures : 0 (0 *) Entry Match Value Destination Adjacency Action ----- ----------- --------------------- ------ 1 No match value N2728701R_pub Routing complete Table Name : SOURCE-ACCT-TABLE Class : Routing Table type : rtg-src-acc Total Call-policy Failures : 0 (0 *) Entry Match Value Destination Adjacency Action ----- ----------- --------------------- ------ 1 N2728701R_b2bCore Next N2728701R_cust 2 N2728701R_cust Next N2728701R_b2bCo 3 N2067088R_b2bCore Next N2067088R_cust 4 N2067088R_cust Next N2067088R_b2bCo 5 telstraEDN_b2bCore Next telstraEDN_cust 6 telstraEDN_cust Next telstraEDN_b2bC 7 N2031208R_b2bCore Next N2031208R_cust 8 N2031208R_cust Next N2031208R_b2bCo Table Name : telstraEDN_b2bCore Class : Routing Table type : rtg-least-cost Total Call-policy Failures : 0 (0 *) Entry Match Value Destination Adjacency Action ----- ----------- --------------------- ------ 1 No match value telstraEDN_ccs Routing complete 2 No match value telstraEDN_ccp Routing complete Table Name : telstraEDN_cust Class : Routing Table type : rtg-least-cost Total Call-policy Failures : 0 (0 *) Entry Match Value Destination Adjacency Action ----- ----------- --------------------- ------ 1 No match value telstraEDN_sub Routing complete 2 No match value telstraEDN_pub Routing complete * Numbers in brackets refer to a call being rejected by a routing or number analysis table because there were no matching entries in the table. This is also included in the total figure. cjtp-csd-002#
- Check adjacency status
cjtp-csd-001#sh sbc csd-001 sbe adjacencies SBC Service "csd-001" Name Type State Description ----------------------------------------------------------- N2012648R_ccp SIP Attached N2012648R_ccs SIP Attached N2012648R_pub SIP Attached N2012648R_sub SIP Attached N2012734R_ccp SIP Attached N2012734R_ccs SIP Attached N2012734R_pub SIP Attached N2015708R_ccp SIP Attached N2015708R_ccs SIP Attached N2015708R_pub SIP Attached N2015708R_sub SIP Attached N2019334R_ccp SIP Attached N2019334R_ccs SIP Attached N2019334R_pub SIP Attached N2019334R_sub SIP Attached N2019633R_ccp SIP Detached N2019633R_ccs SIP Detached N2019633R_pub SIP Detached N2041337R_ccp SIP Attached N2041337R_ccs SIP Attached N2041337R_pub SIP Attached N2041337R_sub SIP Attached N2724990R_ccp SIP Attached N2724990R_ccs SIP Attached N2724990R_pub SIP Attached N3012699R_ccp SIP Attached N3012699R_ccs SIP Attached N3012699R_pub SIP Attached N3710999R_ccp SIP Attached N3710999R_ccs SIP Attached N3710999R_pub SIP Attached N3710999R_sub SIP Attached telstraEDN_ccp SIP Attached telstraEDN_ccs SIP Attached telstraEDN_pub SIP Attached telstraEDN_sub SIP Attached cjtp-csd-001#
- Check adjacency status detail
cjtp-csd-001#sh sbc csd-001 sbe adjacencies N2724990R_pub detail SBC Service "csd-001" Adjacency N2724990R_pub (SIP) Status: Attached Signaling address: 147.132.191.18:5060, VRF N2724990R Signaling-peer: 10.145.64.254:5060 (Default) Force next hop: No Account: N2724990R_cust Group: None In header profile: Default Out header profile: Default In method profile: Default Out method profile: Default In body profile: None Out body profile: None In UA option prof: Default Out UA option prof: Default In proxy opt prof: Default Out proxy opt prof: Default Priority set name: None Local-id: None Rewrite REGISTER: Off Register contact username: Rewrite Target address: None NAT Status: Force off Reg-min-expiry: 3000 seconds Fast-register: Enabled Fast-register-int: 30 seconds Register aggregate: Disabled Registration Required: Disabled Register Out Interval: 0 seconds Parse username params: Disabled Supported timer insert:Disabled Suppress Expires: Disabled p-asserted-id header-value: not defined p-assert-id assert: Disabled Authenticated mode: None Authenticated realm: None Auth. nonce life time: 300 seconds IMS visited NetID: None Inherit profile: Default Force next hop: No Home network Id: None UnEncrypt key data: None SIPI passthrough: No Passthrough headers: Media passthrough: No Preferred transport: TCP Incoming 100rel strip: No Incoming 100rel supp: No Out 100rel supp add: No Out 100rel req add: No Parse TGID parms: No IP-FQDN inbound: IP-FQDN outbound: FQDN-IP inbound: FQDN-IP outbound: Outbound Flood Rate: None Hunting Triggers: 408 500 503 Add transport=tls param: Disabled Redirect mode: Pass-through Security: Untrusted-Unencrypted TLS mutual authentication: No Ping: Enabled Ping Interval: 32 seconds Ping Life Time: 5 seconds Ping Peer Fail Count: 2 Ping Trap sending: Enabled Ping Peer Status: Online Rewrite Request-uri: Disabled Registration Monitor: Disabled DTMF SIP NOTIFY Relay: Enabled DTMF SIP NOTIFY Interval: 2000 DTMF SIP default duration: 200 DTMF Preferred Method: SIP NOTIFY Realm : None Statistics setting: Summary cjtp-csd-001#
- Show active call
cjtp-csd-001#show sbc csd-001 sbe calls SBC Service "csd-001" Call State Src Adjacency Dest Adjacency --------------------------------------------------------------- 2271 Active telstraEDN_sub telstraEDN_ccs 2272 Active N2012734R_ccs N2012734R_pub cjtp-csd-001#
- Clear problem call
clear sbc <sbc-name> sbe call <Call-ID>
- Check which addresses are being blacklist
cjtp-csd-001#sh sbc csd-001 sbe blacklist current-blacklisting SBC Service "csd-001" SBE dynamic blacklist current members No configured blacklist information found. cjtp-csd-001#
- Show black list limit
cjtp-csd-001#sh sbc csd-001 sbe blacklist configured-limits SBC Service "csd-001" No configured blacklist information found. Blacklist Defaults ==================== Reason Trigger Trigger Blacklisting Size Period Period Authentication (4) (100 ms) (10 mins) Bad-Address (4) (100 ms) (10 mins) Routing (4) (100 ms) (10 mins) Registration (4) (100 ms) (10 mins) Policy (4) (100 ms) (10 mins) Corruption (4) (100 ms) (10 mins) Spam (30) (100 ms) (10 mins) -------------------------------------------------------------- cjtp-csd-001#
* Clear blacklist
clear sbc <sbc-name> sbe blacklist ipv4 <ip>
- Other Debug Commands
debug sbc csd-001 filter adjacency telstraEDN_ccp sip debug sbc csd-001 filter adjacency telstraEDN_ccp call debug sbc csd-001 filter adjacency telstraEDN_ccp media debug sbc csd-001 filter adjacency telstraEDN_ccs sip debug sbc csd-001 filter adjacency telstraEDN_ccs call debug sbc csd-001 filter adjacency telstraEDN_ccs media
Cisco Troubleshooting
B2B - Basic troubleshooting for TelePresence B2B Calls
TelePresence endpoints are single and three-screen endpoints that are SIP standardsbased. Most of the B2B calls are routed through the Cisco SBC ASR platforms.
When there are problems placing B2B calls, there are a number of steps that you can take to isolate the cause of the problem.
To troubleshoot a B2B call, do the following procedure:
Troubleshooting within your network
- All rooms are failing to place B2B calls or only 1?
- Verify CTS version is compatible with remote equipment
- Is this room enabled to place B2B calls?
- Do you have security enabled in the CTS/Tandberg endpoint?
- Do you have a valid route pattern and Calling Search Space access from your room to the remote B2B number?
- Is routing properly setup between your Company and the remote SBC for Company B or TelePresence Exchange?
- Is there a Firewall, CUBE, ASA or any other device in the middle which may be preventing communication between your Company and the remote SBC?
- Have you collected CTS, CUCM and SBC logs?
If you need to troubleshoot video and/or audio quality issues for any call for which the call passes through the SBC, it is easy to get some good information/statistics vlia CLI. Note that there is no easy way to programmatically identify dbe media-flows correlating to the sbe call leg based on calling/called numbers since the sbe/dbe do not use the same keys/contexts. Still, you can usually identify the media-flow of interest if you know the media-address on the Customer’s side. Some basic commands are below.
For dialout calls placed on enterprise endpoints, check the status of the call on the session border controller (SBC).
If you need to troubleshoot video and/or audio quality issues for any call for which the call passes through the SBC, it is easy to get some good information/statistics vlia CLI. Note that there is no easy way to programmatically identify dbe media-flows correlating to the sbe call leg based on calling/called numbers since the sbe/dbe do not use the same keys/contexts. Still, you can usually identify the media-flow of interest if you know the media-address on the Customer’s side. Some basic commands are below.
Commands and debugs (ASR platform)
The following commands can give you valuable information to verify call information.
show sbc <your sbc name> sbe adjacencies
show sbc <your sbc name> dbe media-flow-stats summary
show sbc <your sbc name> dbe media-flow-stats detail
show sbc <your sbc name> sbe calls
show platform hardware qfp active feature sbc pfilter global
show ip socket detail
show sbc <your sbc name> sbe sip statistics
show sbc <your sbc name> dbe forwarder-stat
To collect logs in SBC ASR:
- sbc dump-diagnostics harddisk: (issue once to clear the log)
debug sbc <sbc-name> log-level console 0 debug sbc <sbc-name> log-level buffer 0
- Place the call
sbc dump-diagnostics harddisk: (dump the log for this new call) Collect ipstrc and pdtrc file from harddisk.
- After test is complete, you can optionally reset the debug levels:
debug sbc <sbc_name> log-level console 63 debug sbc <sbc_name> log-level buffer 63
Cisco GSR log collection
RP/0/9/CPU0:ciscotxbu-mysbc-1#show services red Service type Name Pref. Active Pref. Standby -------------------------------------------------------------------------------- SBC mycompanysbc 0/7/CPU0 Active 0/6/CPU0 Standby RP/0/9/CPU0:ciscotxbu-mysbc-1#run attach 0/7/CPU0 attach: Starting session 0 to nodeid 0/7/CPU0 attach: Type "exit" to quit. ksh-LC>en ksh-LC>cd /tmp ksh-LC>ls pdtrc* pdtrc.201007191624.log pdtrc.201007191936.log ksh-LC>tail -f pdtrc.201007191936.log
Example 1: Audio only call ( IVR)
1) sjc01-ops-asr-1#show sbc ops-sbc dbe media-flow-stats detail | inc Stream|Side|Address|RTCP|Port|SDP|Packets|Reserved
Stream ID: 49153 Side A: Reserved Bandwidth: 10920 (bytes/second) Local Address: 10.22.134.131 Local Port: 16408 Remote Address: 10.35.204.91 <-- This is typically the peer’s IP (usually extracted from SDP) // Note that this need not match the signaling remote-address configured in the adjacency (remember that this is a dbe command, not an sbe command) Remote Port: 30836 Port Range Tag: <None> Packets Received: 777 Packets received on side A should match packets sent side B, if not, DBE may be dropping packets Packets Sent: 328 Packets Discarded: 0 Packets discarded by DBE, typically if input packet rate exceeds Reserved Bandwidth GM Discarded Packets: 0 RTCP Packets Sent: 0 RTCP Packets Received: 0 RTCP Packets Lost: 0 Unexpected SrcAddr Packets: No SDP string: m=audio 0 RTP/SAVP 0 101 Side B: Reserved Bandwidth: 10920 (bytes/second) Local Address: 10.22.134.131 Local Port: 16410 Remote Address: 10.35.195.51 Remote Port: 17592 Port Range Tag: <None> Packets Received: 328 Packets Sent: 777 <-- Note that this value matches packets received on side A (see above) Packets Discarded: 0 GM Discarded Packets: 0 RTCP Packets Sent: 0 RTCP Packets Received: 0 RTCP Packets Lost: 0 Unexpected SrcAddr Packets: No SDP string: m=audio 0 RTP/SAVP 0 101 <-- This is a audio stream, and the RTP payload_type of the associated RTP packets is 0
2) Command to see recent/generic call stats/failure-codes:
sjc01-ops-asr-1#sh sbc ops-sbc sbe call-stats all previous5mins
statistics for the previous 5 mins for source adjacency TXBUALPHA-CUCM Call count totals: Total call attempts = 1 Total active calls = 0 Total active IPv6 calls = 0 Total activating calls = 0 Total de-activating calls = 0 Total active emergency calls = 0 Total active e2 emergency calls = 0 Total IMS rx active calls = 0 Total IMS rx call renegotiation attempts = 0 Total SRTP-RTP interworked calls = 0 Total active calls not using SRTP = 0 Total active transcoded calls = 0 Total active transrated calls = 0 General call failure counters: Total call setup failures = 0 Total active call failures = 0 Total failed call attempts = 0 Total failed calls due to update failure = 0 Total failed calls due to resource failure = 0 Total failed calls due to congestion = 0 Total failed calls due to media failure = 0 Total failed calls due to signaling failure = 0 Total failed calls due to IMS rx setup failure = 0 Total failed calls due to IMS rx renegotiation failure = 0 Total failed calls due to RTP disallowed on call leg = 0 Total failed calls due to SRTP disallowed on call leg = 0 Policy control failures: Call setups failed due to NA = 0 Call setups failed due to RTG = 0 Call setups failed due to CAC = 0 CAC fails due to number of calls limit = 0 CAC fails due to call rate limit = 0 CAC fails due to bandwidth limit = 0 CAC fails due to number of media channels limit = 0 CAC fails due to number of media update limit = 0 CAC message drops due to mid call message rate limit = 0 CAC message drops due to out of call message rate limit = 0
3) Command to see if the QFP (QuantamFlow Processors).
→ See if the numbers are incrementing to determine if counter is interesting.
sjc01-ops-asr-1#show platform hardware qfp active statistics drop
------------------------------------------------------------------------- Global Drop Stats Packets Octets ------------------------------------------------------------------------- IpTtlExceeded 190 14060
Packet drops can happen for a number of different reasons (layer 1 – 7, osi). Item 1 & item 2 allow you to track drops at the sbc software level (Layer 5+). To track lower layer problems (for example, drops caused by rtp packets that have udp checksum errors), use command 3 from below (only an example to give you an idea of the commands used, you can use different options to suit your needs).
Example 2: TelePresence Video call
sjc01-ops-asr-1#sh sbc ops-sbc sbe calls
SBC Service "ops-sbc" Call State Src Adjacency Dest Adjacency ----------------------------------------------------------------------- 8 Active TXBUALPHA-CUCM ACE 9 Active TXBUALPHA-CUCM ACE
From the show sbc <your sbc> sbe calls, you can verify calling number using the following command:
sjc01-ops-asr-1#sh sbc ops-sbc sbe call 8 branches
SBC Service "ops-sbc" Call: 8 State: Active Type: Audio Transrating: No Caller Port Range Tag: (None) Callee Port Range Tag: (None) Branch Calling Number Called Number Billing ID DTMF Capabilities 1 14082323488 4DA8C848202020203835313500000000000000000000000F None 2 14082323769**8 4DA8C8482020202038353135000000000000000000000010 Media(RFC2833)
sjc01-ops-asr-1#sh sbc ops-sbc sbe call 9 branches
SBC Service "ops-sbc" Call: 9 State: Active Type: Audio Transrating: No Caller Port Range Tag: (None) Callee Port Range Tag: (None) Branch Calling Number Called Number Billing ID DTMF Capabilities 1 14082323487 4DA8C8602020202038353135000000000000000000000011 None 2 14082323769**8 4DA8C8602020202038353135000000000000000000000012 Media(RFC2833)
Verify Media flowing and remote IP addresses are correct.
When placing B2B and there is an ASA, CUBE or any device which is performing NAT, this command becomes really useful as provide information which can help you to verify if IP addresses negotiated are correct.
sjc01-ops-asr-1# show sbc ops-sbc dbe media-flow-stats summary
SBC Service "ops-sbc" Context ID 8 Stream ID 49153 Side A: Name Media Flowing: Yes Local Address/Port: 10.22.134.131/16416 Remote Address/Port: 10.35.204.91/22270 Status: InService Side B: Name Media Flowing: Yes Local Address/Port: 10.22.134.131/16418 Remote Address/Port: 10.22.133.231/16384 Status: InService Context ID 8 Stream ID 49154 Side A: Name Media Flowing: Yes Local Address/Port: 10.22.134.131/16420 Remote Address/Port: 10.35.204.91/20180 Status: InService Side B: Name Media Flowing: Yes Local Address/Port: 10.22.134.131/16422 Remote Address/Port: 10.22.133.231/16386 Status: InService Context ID 9 Stream ID 49153 Side A: Name Media Flowing: Yes Local Address/Port: 10.22.134.131/16424 Remote Address/Port: 10.22.73.71/23848 Status: InService Side B: Name Media Flowing: Yes Local Address/Port: 10.22.134.131/16426 Remote Address/Port: 10.22.133.231/16388 Status: InService Context ID 9 Stream ID 49154 Side A: Name Media Flowing: Yes Local Address/Port: 10.22.134.131/16428 Remote Address/Port: 10.22.73.71/24800 Status: InService Side B: Name Media Flowing: Yes Local Address/Port: 10.22.134.131/16430 Remote Address/Port: 10.22.133.231/16390 Status: InService
sjc01-ops-asr-1#show sbc ops-sbc dbe media-flow-stats detail | inc Stream|Side|Address|RTCP|Port|SDP|Packets|Reserved
Stream ID: 49153 Side A: Reserved Bandwidth: 61320 (bytes/second) Local Address: 10.22.134.131 Local Port: 16416 Remote Address: 10.35.204.91 Remote Port: 22270 Port Range Tag: <None> Packets Received: 34010 Packets Sent: 21679 Packets Discarded: 0 GM Discarded Packets: 0 RTCP Packets Sent: 0 RTCP Packets Received: 0 RTCP Packets Lost: 0 Unexpected SrcAddr Packets: No SDP string: m=audio 0 RTP/SAVP 96 101 <-- This is a audio stream, and the RTP payload_type of the associated RTP packets is 96 Side B: Reserved Bandwidth: 61320 (bytes/second) Local Address: 10.22.134.131 Local Port: 16418 Remote Address: 10.22.133.231 Remote Port: 16384 Port Range Tag: <None> Packets Received: 21679 Packets Sent: 34010 Packets Discarded: 0 GM Discarded Packets: 0 RTCP Packets Sent: 0 RTCP Packets Received: 0 RTCP Packets Lost: 0 Unexpected SrcAddr Packets: No SDP string: m=audio 0 RTP/SAVP 96 101 <-- This is a audio stream, and the RTP payload_type of the associated RTP packets is 96 Stream ID: 49154 Side A: Reserved Bandwidth: 2847373 (bytes/second) Local Address: 10.22.134.131 Local Port: 16420 Remote Address: 10.35.204.91 Remote Port: 20180 Port Range Tag: <None> Packets Received: 297289 Packets Sent: 337934 Packets Discarded: 0 GM Discarded Packets: 0 RTCP Packets Sent: 0 RTCP Packets Received: 0 RTCP Packets Lost: 0 Unexpected SrcAddr Packets: No SDP string: m=video 0 RTP/SAVP 112 <-- This is a video stream, and the RTP payload_type of the associated RTP packets is 112 Side B: Reserved Bandwidth: 2847373 (bytes/second) Local Address: 10.22.134.131 Local Port: 16422 Remote Address: 10.22.133.231 Remote Port: 16386 Port Range Tag: <None> Packets Received: 337934 Packets Sent: 297289 Packets Discarded: 0 GM Discarded Packets: 0 RTCP Packets Sent: 0 RTCP Packets Received: 0 RTCP Packets Lost: 0 Unexpected SrcAddr Packets: No SDP string: m=video 0 RTP/SAVP 112 <-- This is a video stream, and the RTP payload_type of the associated RTP packets is 112