SIP Trunk to Carrier Issue

Unanswered Question
Jan 25th, 2010

The incoming call hits the NAT'd IP of the Pub, unfortunately the cluster does not recognize that IP and rejects the call. Is there any way I can make this work? Thanks.
01/22/2010 11:43:06.923  CCM|//SIP/SIPUdp/wait_UdpDataInd: Incoming SIP UDP message size 1037 from  208..x.x.x:[5060]:
INVITE sip:6024667xxx;[email protected] (My Nat'd IP):5060  SIP/2.0
Via: SIP/2.0/UDP  208.x.x.x:5060;branch=z9hG4bK07B7a045e321f57a5a2
From:  <sip:[email protected]>;tag=gK077f12b8
To:  <sip:[email protected]>
[email protected]
01/22/2010 11:43:06.934  CCM|//SIP/SIPUdp/wait_SdlSPISignal: Outgoing SIP UDP message to  208.x.x.x:[5060]:
SIP/2.0 100 Trying
As we are unware of  ip.addr 12.X.X.X, we send a NOT found.
01/22/2010 11:43:06.936 CCM|Digit  Analysis: Host Address=12.X.X.X DOES NOT MATCH any address for this  cluster.|<CLID::StandAloneCluster><NID::10.23.X.X><CT::1,100,185,1.94><IP::208.x.x.x><DEV::><LVL::Arbitrary><MASK::0800>

01/22/2010 11:43:06.942 CCM|//SIP/SIPUdp/wait_SdlSPISignal: Outgoing SIP  UDP message to 208.x.x.x:[5060]:
SIP/2.0 404 Not  Found
Reason: Q.850;cause=1
Date: Fri, 22 Jan 2010 16:43:06  GMT
From:  <sip:[email protected]>;tag=gK077f12b8
Allow-Events:  presence
Content-Length: 0
To:  <sip:[email protected]>;tag=1bf2e1f4-b033-4236-a158-4348f90067ba-22034938
[email protected]Via: SIP/2.0/UDP  208.x.x.x:5060;branch=z9hG4bK07B7a045e321f57a5a2
CSeq: 3780  INVITE

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
wrickk_2 Tue, 01/26/2010 - 07:24

Anyone?  Is there a way to setup a FQDN for that trunk and have them point to that? I looked but couldn't find anything.




This Discussion