Strange Issue, dialing out on SIP trunks 6

[dgrizzard]

We are testing SIP trunks for voice from our Telco provider. The technicians that set this up on our switch created an AC2 for dialing out over these trunks. So far we have 1 extension on a phone in our data room that they setup for testing that works perfectly fine. You dial AC2+number and everything goes through correctly with the correct caller ID tied to that DN. My only issue is that I've not been able to successfully test this on a different phone. I've created even the same DN on my desk set with the same CLID entry the other phone is using, but I can not make a successful call.

I guess my main question is, what should I be looking for on the set or in our switch that allows this one DN to dial out on this one set, but does not work any where else?

TIA

 

[Reusser]

I still suspect your trace is not the active call when you heard the intercept message (complete the call preceded)I suspect call failed over to PSTN or you took the trace to early before call completed to far end

FAR-END SIP SIGNALLING IP: 0.0.0.0
FAR-END MEDIA ENDPOINT IP: 0.0.0.0 PORT: 0

Also interesting enough - these 2 phones do not appear to be at the same location -
Working phone - MEDIA ENDPOINT IP: 172.16.100.33
non-working phone = MEDIA ENDPOINT IP: 192.9.202.74

your problem could be this site is not registared to NRS or same NRS, or bars are not setup the same.

or, if this is a branch - maybe phone is registerd locally?

 

[dgrizzard]

For instance, after making the changes to my CLID per your previous post the call had a long pause probably at least 5 seconds and then went fast busy. Here is a trace right before it went fast busy...

ACTIVE  TN 004 0 08 01  IPMG 004 0

ORIG   TN 004 0 08 01  IPMG 004 0  KEY 2  SCR       CUST 0  DN 1737  TYPE 3904
  VGW TN 004 0 11 31
  MEDIA ENDPOINT IP: 172.16.100.33  PORT: 5454
TERM   VTN 252 0 00 08  IPTI  RMBR  40 9 OUTGOING VOIP GW CALL
  FAR-END SIP SIGNALLING IP: 0.0.0.0
  FAR-END MEDIA ENDPOINT IP: 0.0.0.0  PORT: 0
  FAR-END VendorID: Not available
MEDIA PROFILE: CODEC n/a NO-LAW  PAYLOAD 1 ms  VAD OFF
RFC2833:  RXPT  101   TXPT  N/A  DIAL DN 2674588
MAIN_PM  DIAL    AUX_PM  COMPLETE
TALKSLOT  ORIG  15   TERM  15    JUNCTOR  ORIG0   TERM0
EES_DATA:
NONE
QUEU  NONE
CALL ID 0 12930


AUX  NARS



----  ISDN ISL CALL (TERM) ----
CALL REF # =  393
BEARER CAP =  VOICE
HLC =
CALL STATE =  3     OUTGOING
CALLING NO =  2621737  NUM_PLAN:E164    TON:SUBSCRIBER  ESN:NXX
CALLED NO  =  2674588  NUM_PLAN:E164    TON:SUBSCRIBER  ESN:NXX

NON ACTIVE  VTN 100 0 02 17

NON ACTIVE  VTN 100 0 02 21

NON ACTIVE  TN 004 0 09 13   MARP

Previously this phone was working perfectly fine, and here is the trace after I change it back to basically just DIDN being YES and everything else defaulted.

ACTIVE  TN 004 0 08 01  IPMG 004 0

ORIG   TN 004 0 08 01  IPMG 004 0  KEY 2  SCR       CUST 0  DN 1737  TYPE 3904
  VGW TN 004 0 11 06
  MEDIA ENDPOINT IP: 172.16.100.33  PORT: 5404
TERM   VTN 252 0 00 08  IPTI  RMBR  40 9 OUTGOING VOIP GW CALL
  FAR-END SIP SIGNALLING IP: 172.30.209.57
  FAR-END MEDIA ENDPOINT IP: 172.30.209.164  PORT: 12640
  FAR-END VendorID: Not available
MEDIA PROFILE: CODEC G.711 MU-LAW  PAYLOAD 20 ms  VAD OFF
RFC2833:  RXPT  101   TXPT  101   DIAL DN 32674588
MAIN_PM  DIAL    AUX_PM  COMPLETE
TALKSLOT  ORIG  8   TERM  8    JUNCTOR  ORIG0   TERM0
EES_DATA:
NONE
QUEU  NONE
CALL ID 0 13790


----  ISDN ISL CALL (TERM) ----
CALL REF # =  393
BEARER CAP =  VOICE
HLC =
CALL STATE =  3     OUTGOING
CALLING NO =  1737  NUM_PLAN:E164    TON:SUBSCRIBER  ESN:NXX
CALLED NO  =  2674588  NUM_PLAN:E164    TON:SUBSCRIBER  ESN:NXX

NON ACTIVE  VTN 100 0 02 17

NON ACTIVE  VTN 100 0 02 21

NON ACTIVE  TN 004 0 09 13   MARP

Got immediate ring back on that call and number on my cell phone was the correct CLID. The only thing I change between that non-working call and a working call was the CLID. I also just tested putting in the NPA only and leaving the prefix blank, that worked on a TDM phone, but not on an IP phone (still telco message).

Also, to answer your question, the previous IP phone used in my posts was registering to an SMG and then redirecting to my main CS (where the SIP trunk is). Now I am using an IP phone just registered locally to my main CS with the same result though. Also, the IP addresses are different , but that's because they are on different subnets from my ELAN/TLAN. I am also able to dial fine from all phones/DNs using my AC1.

I'm starting to think a part of it deals with what the telco is expecting as a CLID before it will pass the call. I'm just not sure why my IP phones are not passing the same CLID as my TDM.

 

[dgrizzard]

Also interesting enough - these 2 phones do not appear to be at the same location -
Working phone - MEDIA ENDPOINT IP: 172.16.100.33
non-working phone = MEDIA ENDPOINT IP: 192.9.202.74

Just to clear up this part too, the working phone is a 3904 so the first media endpoint of 172.16.100.33 is an MGC card(DSP channel). The non-working is directly to an IP phone.

 

[dgrizzard]

HAHA *KICKS THE CS1000*

*clears his throat*

Well..when you have SIP trunking on a separate signaling server the voice payload must match your signaling server for your IP phones. It is working now. Thank you everyone and stars all around.


*bows*