Adtran
Help
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Anonymous
Not applicable
‎05-13-2014 06:26 PM

Connecting 2 NV7100s via the WAN port (0/0)

Jump to solution

Whats the best way to set up calls between 2 NV7100 using the WAN interface?  Phones ring but disconnects once off-hook.

VLDZ_NV7100#deb voice ver

VLDZ_NV7100#

15:11:00.007 TM.T03 01 SipTM_Idle           rcvd SIP call-leg request: INVITE

15:11:00.008 TM.T03 01 SipTM_Idle           call-leg -> Offering

15:11:00.008 TM.T03 01 SipTM_Idle           State change      >> SipTM_Idle->SipTM_Trying

15:11:00.008 TM.T03 01 SipTM_Trying         SDP offer is not loopback request

15:11:00.009 TM.T03 01 SipTM_Trying         Processing From for Caller-ID.

15:11:00.009 TM.T03 01 SipTM_Trying         Caller ID Name   = "Glennallen Central Office"

15:11:00.009 TM.T03 01 SipTM_Trying         Caller ID Number = "9075551101"

15:11:00.010 TM.T03 01 SipTM_Trying         info: unable to set redirect number(s) from INVITE

15:11:00.010 TM.T03 01 SipTM_Trying         sent: TA->InboundCall

15:11:00.010 TM.T03 01 Looking up source address for destination 10.10.10.2

15:11:00.011 TM.T03 01 call-leg (0x57dff30) -> src: 10.10.10.3 : 5060  dst: 10.10.10.2 : 5060

15:11:00.012 TM.T03 01 SipTM_Trying         sent: 100 Trying

15:11:00.012 TA.T03 01 TAIdle               rcvd: inboundCall from TM

15:11:00.013 TA.T03 01 State change      >> TAIdle->TAInboundCall (TAS_Calling)

15:11:00.013 TA.T03 01 Failed - DID translation: no match for 7710, using 7710

15:11:00.013 TA.T03 01 TAIdle               sent: call to SB

15:11:00.014 TM.T03 01 SipTM_Trying         tachg -> TAInboundCall

15:11:00.014 TM.T03 01 SipTM_Trying         State change      >> SipTM_Trying->SipTM_Pending

15:11:00.014 SB.CALL 22 Idle                 Called the call routine with 7710

15:11:00.014 SB.CCM isMappable:

15:11:00.014 SB.CCM  :  Call Struct 0x3f46c10 :   Call-ID = 22

15:11:00.015 SB.CCM  :  Org Acct = T03    Dst Acct = 7710

15:11:00.015 SB.CCM  :  Org Port ID = SipTrunk 0/0.256   Dst Port ID = unknown 0/0

15:11:00.015 SB.CCM  :  SDP Transaction = CallID: 22

15:11:00.015 SB.CCM  :  SDP Offer = 0x03ef1c10, (192.168.11.42:50032)

15:11:00.016 SB.CCM isMappable: Call Connection Type is RTP_TO_RTP

15:11:00.016 SB.CCM handleRtpToRtp: Modifying SDP Offer

15:11:00.017 SB.CCM translateOffer: offer codec list: PCMU G729

15:11:00.017 SB.CCM translateOffer: revised offer codec list: PCMU G729

15:11:00.017 SB.CCM translateOffer: codec list after answerer: PCMU G729

15:11:00.018 SB.CCM translateOffer: DTMF signaling: answerer has no restrictions configured, passing offer(NTE 101) through

15:11:00.018 SB.CCM translateOffer: success

15:11:00.019 MEDIA.MANAGER Allocating media port.

15:11:00.019 MEDIA.MANAGER getSubstitutePort: No matching callIdMap entry found for call 22

15:11:00.019 MEDIA.MANAGER Call ID map : Added new entry : call ID 22 : session -1400022659INIP4192.168.11.42 : version 1400022659 : index 82

15:11:00.019 MEDIA.MANAGER New media entry : type(0), callID(22), sessionID(-1400022659INIP4192.168.11.42), original IP(192.168.11.42) ports(50032-50033), substitute IP(::) ports(10082-10083), RtpChannel(NULL), connection(0x3eb8b10), sdpOverride(0), me(0x3ee5310). No RtpChannel

15:11:00.020 SB.CALL 22 Idle                 Call sent from T03 to 7710 (7710)

15:11:00.020 SB.CALL 22 State change      >> Idle->Delivering

15:11:00.020 TA.T03 01 TAInboundCall        CallResp event accepted

15:11:00.021 TA.T03 01 State change      >> TAInboundCall->TAConnectWaitIn (TAS_Calling)

15:11:00.021 SA.7710 rcvd: deliver from SB

15:11:00.021 SA.7710 Ca:0 Idle                 sent: deliverResponse(accept) to SB

15:11:00.021 SA.7710 Ca:0 Idle                 Set my destination sessionCookie to my call Appearance

15:11:00.021 SA.7710 Ca:0 Idle                 State change      >> Idle->Ringing (CAS_Ringing)

15:11:00.022 SA.7710 Ca:0 Ringing              sent: AcctPhoneMgr_cachg(CAS_Ringing) to PM

15:11:00.022 PM.7710 Ca:0 SipPM_Idle           rcvd: CAS_Ringing

15:11:00.022 PM.7710 Ca:0 State change      >> SipPM_Idle->SipPM_Ringing

15:11:00.022 PM.7710 Ca:0 Looking up source address for destination 10.10.29.2

15:11:00.023 PM.7710 Ca:0 call-leg (0x57e0158) -> src: 10.10.29.1 : 5060  dst: 10.10.29.2 : 5060

15:11:00.023 PM.7710 Ca:0 SDP DPI call ID 22 : No media bin.

15:11:00.024 PM.7710 Ca:0 Processing new SDP entries.

15:11:00.024 PM.7710 Ca:0 Checking for internal Media Gateway IP Address

15:11:00.024 PM.7710 Ca:0 RTP Channel is NULL, Media Gateway must not be involved in call

15:11:00.024 PM.7710 Ca:0 Undo of previous operation not required (RTP NAT Entry for 192.168.11.42:50032 not found)

15:11:00.024 PM.7710 Ca:0 Checking for internal Media Gateway IP Address

15:11:00.025 PM.7710 Ca:0 Given RTP Channel is null, checking for hairpinned RTP Channel

15:11:00.025 PM.7710 Ca:0 RTP Channel is NULL, Media Gateway must not be involved in call

15:11:00.025 PM.7710 Ca:0 Checking need for firewall traversal

15:11:00.025 PM.7710 Ca:0 Testing firewall policies

15:11:00.025 PM.7710 Ca:0 Source NAT is needed

15:11:00.026 PM.7710 Ca:0 Requesting new NAT port pair from firewall

15:11:00.026 PM.7710 Ca:0 Requesting ref counting for  NAT port pair 50062 and 50063

15:11:00.026 PM.7710 Ca:0 Reserving NAT ports 50062 & 50063 for interface 10.10.10.3

15:11:00.026 PM.7710 Ca:0 Source NAT - replacing 192.168.11.42:50032 with 10.10.10.3:50062

15:11:00.027 PM.7710 Ca:0 Adding RTP NAT Entry: 192.168.11.42:50032 -> 10.10.10.3:50062

15:11:00.030 PM.7710 Ca:0 SipPM_Ringing        call-leg (P:0x57e0158 S:0x0) -> Inviting (Local Inviting)

15:11:00.030 PM.7710 Ca:0 SipPM_Ringing        Default: CallLegStateChanged to Inviting ignored

15:11:00.030 PM.7710 Ca:0 SipPM_Ringing        sent: INVITE

15:11:00.031 SB.CALL 22 Delivering           Called the deliverResponse routine from Delivering

15:11:00.031 SB.CALL 22 Delivering           DeliverResponse(accept) sent from 7710 to T03

15:11:00.031 TA.T03 01 TAConnectWaitIn      deliverResponse event accepted

15:11:00.031 TA.T03 01 TAConnectWaitIn      ERROR! deliverResponse ignored

15:11:00 SB.CallStructObserver 22 Created

15:11:00 SB.CallStructObserver 22 <-> 599c760-a0a1f01-13c4-46df-59d9e1cd-46df@10.10.10.3

15:11:00.043 PM.7710 Ca:0 SipPM_Ringing        rcvd SIP call-leg response: 100 Trying

15:11:00.044 PM.7710 Ca:0 SipPM_Ringing        call-leg (P:0x57e0158 S:0x0) -> Proceeding (Remote Provisional Response)

15:11:00.095 PM.7710 Ca:0 SipPM_Ringing        rcvd SIP call-leg response: 180 Ringing

15:11:00.096 PM.7710 Ca:0 SipPM_Ringing        sent: SA->Alert

15:11:00.096 PM.7710 Ca:0 call-leg prack -> Rel Prov Response Rcvd / Undefined : -1

15:11:00.096 PM.7710 Ca:0 100rel prov resp rcvd, sent PRACK

15:11:00.098 PM.7710 Ca:0 call-leg prack -> Prack Sent / Undefined : -1

15:11:00.098 SA.7710 Ca:0 Ringing              rcvd: AcctPhoneMgr_alert from PM

15:11:00.098 SA.7710 Ca:0 Ringing              sent: deliverResponse(alert) to SB

15:11:00.099 SB.CALL 22 Delivering           Called the deliverResponse routine from Delivering

15:11:00.099 SB.CALL 22 Delivering           Alert sent from 7710 to T03

15:11:00.099 SB.CALL 22 State change      >> Delivering->Alerting

15:11:00.099 TA.T03 01 TAConnectWaitIn      alert event accepted

15:11:00.100 TM.T03 01 SipTM_Pending        tachg -> TAConnectWaitIn

15:11:00.100 TM.T03 01 SipTM_Pending        State change      >> SipTM_Pending->SipTM_Alerting

15:11:00.101 TM.T03 01 SipTM_Alerting       Sent 180 Ringing

15:11:00.113 PM.7710 Ca:0 SipPM_Ringing        rcvd SIP call-leg response: 200 OK

15:11:00.113 PM.7710 Ca:0 call-leg prack -> Prack Final Response Rcvd / Undefined : 200

15:11:06.698 PM.7710 Ca:0 SipPM_Ringing        rcvd SIP call-leg response: 200 OK

15:11:06.698 PM.7710 Ca:0 SipPM_Ringing        call-leg (P:0x57e0158 S:0x0) -> RemoteAccepted (Remote Accepted)

15:11:06.698 PM.7710 Ca:0 State change      >> SipPM_Ringing->SipPM_Answering

15:11:06.699 PM.7710 Ca:0 SipPM_Answering      sent: SA->Connect

15:11:06.699 SA.7710 Ca:0 Ringing              rcvd: AcctPhoneMgr_connect from PM

15:11:06.700 SA.7710 Ca:0 Ringing              sent: connect to SB

15:11:06.700 SA.7710 Ca:0 Ringing              State change      >> Ringing->Connecting (CAS_Active)

15:11:06.700 SB.CALL 22 Alerting             Called the connect routine

15:11:06.700 SB.CCM isResponseMappable:

15:11:06.700 SB.CCM  :  Call Struct 0x3f46c10 :   Call-ID = 22

15:11:06.701 SB.CCM  :  Org Acct = T03    Dst Acct = 7710

15:11:06.701 SB.CCM  :  Org Port ID = SipTrunk 0/0.256   Dst Port ID = SipPhone 0/0

15:11:06.701 SB.CCM  :  SDP Transaction = CallID: 22

15:11:06.701 SB.CCM  :  SDP Offer = 0x03ef1c10, (192.168.11.42:50032)

15:11:06.702 SB.CCM  :  SDP Answer = 0x03ed5810, (10.10.29.2:2228)

15:11:06.702 SB.CCM isResponseMappable: reversing call connection type to compensate for event originator direction

15:11:06.702 SB.CCM isResponseMappable: Call Connection Type is RTP_TO_RTP

15:11:06.702 SB.CCM handleRtpToRtp: Modifying SDP Answer

15:11:06.703 SB.CCM translateAnswer: offer  codec list: PCMU G729

15:11:06.703 SB.CCM                : answer codec list: PCMU

15:11:06.703 SB.CCM translateAnswer: CODEC transcoding is not required

15:11:06.704 SB.CCM translateAnswer: skipping DTMF answer translation for (NTE 101->NTE 101) due to invalid resource(0x0) or unsupported CODEC, using (NTE 101)

15:11:06.704 SB.CCM translateAnswer: success

15:11:06.705 MEDIA.MANAGER Allocating media port.

15:11:06.705 MEDIA.MANAGER getSubstitutePort: Matching callIdMap entry found for call 22 sessionId -1400022665INIP410.10.29.2 remote port 2228

15:11:06.705 MEDIA.MANAGER Call ID map : Added new session ID : call ID 22 : session -1400022665INIP410.10.29.2 : version 1400022665 : index 84

15:11:06.705 MEDIA.MANAGER New media entry : type(0), callID(22), sessionID(-1400022665INIP410.10.29.2), original IP(10.10.29.2) ports(2228-2229), substitute IP(::) ports(10084-10085), RtpChannel(NULL), connection(0x3f11b10), sdpOverride(0), me(0x3ed4310). No RtpChannel

15:11:06.706 SB.CALL 22 Alerting             Connect sent from 7710 to T03

15:11:06.706 SB.CALL 22 State change      >> Alerting->Connecting

15:11:06.706 TA.T03 01 TAConnectWaitIn      connect event accepted

15:11:06.706 TA.T03 01 State change      >> TAConnectWaitIn->TAConnectPending (TAS_Connected)

15:11:06.707 TM.T03 01 SipTM_Alerting       tachg -> TAConnectPending

15:11:06.707 TM.T03 01 SipTM_Alerting       State change      >> SipTM_Alerting->SipTM_Accept

15:11:06.707 TM.T03 01 SDP DPI call ID 22 : No media bin.

15:11:06.708 TM.T03 01 Processing new SDP entries.

15:11:06.708 TM.T03 01 Checking for internal Media Gateway IP Address

15:11:06.708 TM.T03 01 RTP Channel is NULL, Media Gateway must not be involved in call

15:11:06.708 TM.T03 01 Undo of previous operation not required (RTP NAT Entry for 10.10.29.2:2228 not found)

15:11:06.708 TM.T03 01 Checking for internal Media Gateway IP Address

15:11:06.709 TM.T03 01 Given RTP Channel is null, checking for hairpinned RTP Channel

15:11:06.709 TM.T03 01 RTP Channel is NULL, Media Gateway must not be involved in call

15:11:06.709 TM.T03 01 Checking need for firewall traversal

15:11:06.709 TM.T03 01 Testing firewall policies

15:11:06.709 TM.T03 01 Source NAT is needed

15:11:06.710 TM.T03 01 Requesting new NAT port pair from firewall

15:11:06.710 TM.T03 01 Requesting ref counting for  NAT port pair 50064 and 50065

15:11:06.710 TM.T03 01 Reserving NAT ports 50064 & 50065 for interface 10.10.10.3

15:11:06.710 TM.T03 01 Source NAT - replacing 10.10.29.2:2228 with 10.10.10.3:50064

15:11:06.711 TM.T03 01 Adding RTP NAT Entry: 10.10.29.2:2228 -> 10.10.10.3:50064

15:11:06.713 TM.T03 01 SipTM_Accept         call-leg -> Accepted

15:11:06.714 TM.T03 01 SipTM_Accept         sent: 200 with SDP

15:11:06 SB.CallStructObserver 22 <-> 57e0158-7f000001-13c4-1a527-7b3c0f29-1a527@10.10.29.1

15:11:06.754 TM.T03 01 SipTM_Accept         rcvd SIP call-leg request: ACK

15:11:06.754 TM.T03 01 SipTM_Accept         call-leg -> Connected

15:11:06.754 TM.T03 01 SipTM_Accept         No body in message when trying to get SDP

15:11:06.754 TM.T03 01 SipTM_Accept         info: unable to save SDP

15:11:06.755 TM.T03 01 SipTM_Accept         sent: TA->Connect

15:11:06.755 TM.T03 01 SipTM_Accept         State change      >> SipTM_Accept->SipTM_Connected

15:11:06.755 TM.T03 01 SipTM_Connected      call-leg-mod -> Modify Idle

15:11:06.755 TA.T03 01 TAConnectPending     rcvd: connect from TM

15:11:06.756 TA.T03 01 State change      >> TAConnectPending->TAConnected (TAS_Connected)

15:11:06.756 SB.CALL 22 Connecting           Called the connectResponse routine

15:11:06.756 SB.CCM connect:

15:11:06.756 SB.CCM  :  Call Struct 0x3f46c10 :   Call-ID = 22

15:11:06.757 SB.CCM  :  Org Acct = T03    Dst Acct = 7710

15:11:06.757 SB.CCM  :  Org Port ID = SipTrunk 0/0.256   Dst Port ID = SipPhone 0/0

15:11:06.757 SB.CCM  :  SDP Transaction = CallID: 22

15:11:06.757 SB.CCM  :  SDP Offer = 0x03ef1c10, (192.168.11.42:50032)

15:11:06.758 SB.CCM  :  SDP Answer = 0x03ed5810, (10.10.29.2:2228)

15:11:06.758 MOH.APP printCSHoldStates, connect_: towOrig 0, towDest 0 origHold 0 destHold 0 isHold 0

15:11:06.758 SB.CCM connect: Call Connection Type is RTP_TO_RTP

15:11:06.758 MEDIA.MANAGER Trying to connect call ID 22 : SDP sessions -1400022659INIP4192.168.11.42 and -1400022665INIP410.10.29.2

15:11:06.758 MEDIA.MANAGER Found 1 ports for session -1400022659INIP4192.168.11.42

15:11:06.759 MEDIA.MANAGER Found 1 ports for session -1400022665INIP410.10.29.2

15:11:06.759 MEDIA.MANAGER Connecting Disconnected Local [::]:10082 : Remote 192.168.11.42:50032

15:11:06.759 MEDIA.MANAGER    and     Disconnected Local [::]:10084 : Remote 10.10.29.2:2228

15:11:06.759 SB.CCM firewallConnectCall: Set up firewall using SDP

15:11:06.759 SB.CCM sdpFirewall: invoked with offer - 192.168.11.42:50032, answer - 10.10.29.2:2228

15:11:06.760 SB.CCM sdpFirewallV4: Testing firewall policies

15:11:06.760 SB.CCM sdpFirewallV4: Creating firewall associations to connect 192.168.11.42:50032 to 10.10.29.2:2228

15:11:06.760 SB.CCM sdpFirewallV4: Found Offer 1 times in NAT Table, using: 192.168.11.42:50032 -> 10.10.10.3:50062

15:11:06.761 SB.CCM sdpFirewallV4: Found Answer 1 times in NAT Table, using: 10.10.29.2:2228 -> 10.10.10.3:50064

15:11:06.761 SB.CCM sdpFirewallV4: ERROR - Cannot source NAT in both directions

15:11:06.761 SB.CALL 22 Connecting           ERROR! connect failed

15:11:06.761 SB.CALL 22 State change      >> Connecting->DoubleClearing

15:11:06.762 SB.CALL 22 DoubleClearing       ConnectResponse sent from T03 to 7710

15:11:06.762 SA.7710 Ca:0 Connecting           rcvd: connectResponse from SB

15:11:06.762 SA.7710 Ca:0 Connecting           State change      >> Connecting->Connected (CAS_Connected)

15:11:06.762 SA.7710 Ca:0 Connected            sent: AcctPhoneMgr_cachg(CAS_Connected) to PM

15:11:06.762 PM.7710 Ca:0 State change      >> SipPM_Answering->SipPM_Acking

15:11:06.763 PM.7710 Ca:0 SipPM_Acking         sent: finalizeConnect to SA

15:11:06.764 PM.7710 Ca:0 SipPM_Acking         call-leg (P:0x57e0158 S:0x0) -> Connected (Ack Sent)

15:11:06.764 PM.7710 Ca:0 State change      >> SipPM_Acking->SipPM_Connected

15:11:06.765 PM.7710 Ca:0 SipPM_Connected      call-leg-mod (P:0x57e0158 S:0x0) -> Modify Idle

15:11:06.765 PM.7710 Ca:0 SipPM_Connected      Default: SipCallLegModifyStateChanged to Idle ignored

15:11:06.765 PM.7710 Ca:0 SipPM_Acking         sent: ACK

15:11:06.765 SA.7710 Ca:0 Connected            sent: AcctPhoneMgr_info to PM

15:11:06.765 TA.T03 01 TAConnected          ClearCall event accepted

15:11:06.766 TA.T03 01 State change      >> TAConnected->TAClearingComplete (TAS_Clearing)

15:11:06.766 TM.T03 01 SipTM_Connected      tachg -> TAClearingComplete

15:11:06.766 TM.T03 01 SipTM_Connected      tachgClearing caused transition to byeing state.

15:11:06.766 TM.T03 01 SipTM_Connected      State change      >> SipTM_Connected->SipTM_Byeing

15:11:06.768 TM.T03 01 SipTM_Byeing         call-leg -> Disconnecting

15:11:06.768 TM.T03 01 SipTM_Byeing         sent: BYE

15:11:06.769 SA.7710 Ca:0 Connected            rcvd: clearCall from SB

15:11:06.769 SA.7710 Ca:0 Connected            sent: clearResponse(pass) to SB

15:11:06.769 SA.7710 Ca:0 Connected            State change      >> Connected->Idle (CAS_Idle)

15:11:06.769 SA.7710 Ca:0 Idle                 sent: AcctPhoneMgr_cachg(CAS_Idle) to PM

15:11:06.770 PM.7710 Ca:0 State change      >> SipPM_Connected->SipPM_Byeing

15:11:06.771 PM.7710 Ca:0 SipPM_Byeing         call-leg (P:0x57e0158 S:0x0) -> Disconnecting (Local Disconnecting)

15:11:06.772 PM.7710 Ca:0 SipPM_Byeing         sent: BYE

15:11:06.772 PM.7710 Ca:0 State change      >> SipPM_Byeing->SipPM_Terminated

15:11:06.772 PM.7710 Ca:0 State change      >> SipPM_Terminated->SipPM_Idle

15:11:06.772 SA.7710 Ca:0 Idle                 rcvd: AcctPhoneMgr_finalizeConnect from PM

15:11:06.773 SA.7710 Ca:0 Idle                 Default! ignoring finalizeConnect from PM

15:11:06.773 SB.CALL 22 DoubleClearing       Called the clearResponse routine

15:11:06.773 SB.CALL 22 DoubleClearing       Cleared org in DDC from T03 to 7710

15:11:06.773 SB.CCM disconnect:

15:11:06.773 SB.CCM  :  Call Struct 0x3f46c10 :   Call-ID = 22

15:11:06.774 SB.CCM  :  Org Acct = T03    Dst Acct = 7710

15:11:06.774 SB.CCM  :  Org Port ID = SipTrunk 0/0.256   Dst Port ID = SipPhone 0/0

15:11:06.774 MOH.APP printCSHoldStates, disconnect: towOrig 0, towDest 0 origHold 0 destHold 0 isHold 0

15:11:06.774 SB.CCM disconnect: Call Connection Type is RTP_TO_RTP

15:11:06.774 SB.CCM disconnect, music on hold

15:11:06.775 SB.CCM release:

15:11:06.775 SB.CCM  :  Call Struct 0x3f46c10 :   Call-ID = 22

15:11:06.775 SB.CCM  :  Org Acct = T03    Dst Acct = 7710

15:11:06.775 SB.CCM  :  Org Port ID = SipTrunk 0/0.256   Dst Port ID = SipPhone 0/0

15:11:06.775 SB.CCM release: Call Connection Type is RTP_TO_RTP

15:11:06.776 SB.CALL 22 DoubleClearing       Called the clearResponse routine

15:11:06.776 SB.CALL 22 DoubleClearing       Cleared dest in DDC from 7710 to T03

15:11:06.776 SB.CALL 22 State change      >> DoubleClearing->CallIdlePending

15:11:06.776 SB.CCM release:

15:11:06.776 SB.CCM  :  Call Struct 0x3f46c10 :   Call-ID = 22

15:11:06.777 SB.CCM  :  Org Acct = T03    Dst Acct = 7710

15:11:06.777 SB.CCM  :  Org Port ID = SipTrunk 0/0.256   Dst Port ID = SipPhone 0/0

15:11:06.777 SB.CCM release: Call Connection Type is RTP_TO_RTP

15:11:06 SB.CallStructObserver 22 Finalized

15:11:06.789 TM.T03 01 SipTM_Byeing         rcvd SIP call-leg response: 200 OK

15:11:06.789 TM.T03 01 SipTM_Byeing         call-leg -> Disconnected

15:11:06.789 TM.T03 01 SipTM_Byeing         State change      >> SipTM_Byeing->SipTM_Terminated

15:11:06.790 TM.T03 01 SipTM_Terminated     sent: TA->AppearanceOff

15:11:06.790 TM.T03 01 SipTM_Terminated     State change      >> SipTM_Terminated->SipTM_Idle

15:11:06.791 TA.T03 01 TAClearingComplete   rcvd: appearance off from TM

15:11:06.791 TA.T03 01 TAClearingComplete   Clear Local Variables

15:11:06.793 TA.T03 01 State change      >> TAClearingComplete->TAIdle (TAS_Idle)

15:11:06.794 TM.T03 01 SipTM_Idle           tachg -> TAIdle

2014.05.13 15:11:07 SMDR 22         05/13/2014 15:11:00      0.1 0    E  00/00 Glennallen Cent 9075551101      00/00 Valdez Central  7710            0 N

VLDZ_NV7100#

Message was edited by: matt - removed sensitive information

Labels (3)
Tags (3)
0 Kudos
Reply
1 Solution

Accepted Solutions
Anonymous
Not applicable
‎05-14-2014 01:34 PM

Re: Connecting 2 NV7100s via the WAN port (0/0)

Jump to solution

Had to set an explicit IP route. Thanks TAC!

View solution in original post

0 Kudos
Reply
3 Replies
jayh
Honored Contributor
Honored Contributor
‎05-13-2014 07:29 PM

Re: Connecting 2 NV7100s via the WAN port (0/0)

Jump to solution

Do you have "media-gateway ip primary" configured on the WAN interfaces of both 7100s as well as the interfaces facing the SIP phones?  If not, please do so and try it again.

0 Kudos
Accept as Solution Reply
Anonymous
Not applicable
‎05-14-2014 12:34 PM

Re: Connecting 2 NV7100s via the WAN port (0/0)

Jump to solution

Yes, I do.

0 Kudos
Accept as Solution Reply
Anonymous
Not applicable
‎05-14-2014 01:34 PM

Re: Connecting 2 NV7100s via the WAN port (0/0)

Jump to solution

Had to set an explicit IP route. Thanks TAC!

0 Kudos
Reply