Help with CME 4.1 and SIP trunks 1

[wreed333]

Hey guys I have my SIP trunks fully functional with inbound and outbound calling, the problems is, my public line is only going to be on 1 phone. If I do not put that line on every phone the other users cannot place outgoing calls. The debug logs try to talk to my ISPs server as (internalextension)@206.xxx.xxx.xxx instead of the (SIP line)@206.xxx.xxx.xxx.

How do I get around this so my intenal extensions can place outgoing calls?

 

[whykap]

Mask your caller ID at the Route Pattern level with the SIP line number. You must not be masking it so it passes the DN info.

 

[wreed333]

Hi, Thanks for the response. Could you point me in the right direction with some config or commands to issue?

 

[whykap]

Never mind you got a cme 4.1 and not ccm 4.1.
Here is what you need to do:
On your outgoing dial-peers add this command:
clid network-number xxxxxxxxxx

where xxxxxxxxxx is your SIP line number (what your provider needs to see.

If you need more details please post your dial-peer config first.

 

[wreed333]

I am setting up a new system. Is the best way to make my incoming line ring on a select few phones it to create a ephone-dn for it and assign it to the 2 phones i want to ring, correct? Then the other phones will just have the internal extensions masked with the clid command you gave me.

I want to do this correct the first time.

Thanks

 

[whykap]

WNich phones the main line rings is a customer preference and not a best way to do it. Ask your customer/users how they want to handle incoming calls and how they want to route it.
Incoming has nothing to do with outgoing CLID mask.
Did you get you outbound working with the CLI command I suggested?

 

[wreed333]

Yes it worked beautifully, thank you!

 

[wreed333]

We need to be able to dial #.. to call forward our main line. I have dial-peers for 0, the * key but the dial-peer for the #.. does not work. Any ideas?

 

[wreed333]

Also,
We cannot call-forward to numbers on the outside, inside extensions work fine, but it does not do anything when trying to call forward to a outside number. Any ideas?

 

[whykap]

Is your SIP provider blocking that call from going back out after you forward it? You need to look at your ccsip debugs and see what happens.

 

[whykap]

So what is the inbound calling number and what is the number you are forwarding it to?
What happens? fast busy? dead air?
Can you post you router config?
Exactly what debug is the one posted?
ccsip all?

What is your SIP provider saying about your problem? They can also debug the call and might have some suggestions.

I'd rather keep the discussions within the forum. I do not like to exchange email addresses. Most of us on this forum have jobs, and use the forum to learn and help others out on our spare time. Also by keeping the discussions within the forum you will get more feedback from other members that might have something to add or suggest.

 

[wreed333]

OK i got call-forwaring to work using the NO SUPPLEMENTARY-SERVICE SIP REFER and MOVED TEMP commands but either end cannot hear or talk to one another.

Any ideas?

 

[wreed333]

call transfers to the outside work fine, call forwards work but you each party cannot hear to talk to one another.

 

[whykap]

Your config looks good.
Try this under clobal config:
voice rtp send-recv

Also did you try binding the interface you are using for SIP under voice services?
So under global:
voice service voip
bind control source-interface interface FastEthernet0/0
bind media source-interface FastEthernet0/0

I am not saying this is your problem (probably not) but it's worth a shot.

 

[wreed333]

The voice rtp send-rec is already enabled.

I will try the bind commands. What do they do?

 

[wreed333]

call transfers to the outside work fine, call forwards work but you each party cannot hear to talk to one another.

 

[wreed333]

Anyone else??? I am still fighting this.

 

[whykap]

try this under voice service voip:
redirect ip2ip

The purpose of this command:
Redirects SIP phone calls to SIP phone calls globally on a gateway using the Cisco IOS Voice Gateway.

Unfortunately I do not have a SIP trunk on a CME that I can easily access and try this.
You might want to see if CISCO TAC has anything to add to this.

Let me know.

 

[wreed333]

OK I have signed up for the Broadvoice bring your own device progam to test call forwarding. Guess what same problem.

I am thinking this has to be something on the CME side now.

Any other ideas?