[cisco-voip] Outbound Dial with Carrier SIP Trunk
Wilusz, Mike
mikewilusz at pricechopper.com
Thu Oct 2 16:10:32 EDT 2008
Matt,
Tried that and I still get the same result. The voice config from the
CUBE is this:
voice service voip
address-hiding
allow-connections h323 to h323
allow-connections h323 to sip
allow-connections sip to h323
allow-connections sip to sip
!
dial-peer voice 2 voip
destination-pattern 1..........
session protocol sipv2
session target ipv4:64.206.114.6 (Carrier Gateway)
dtmf-relay rtp-nte
codec g711ulaw
!
dial-peer voice 3 voip
destination-pattern 3474179896
session protocol sipv2
session target ipv4:10.50.120.33 (Our CUCM)
dtmf-relay rtp-nte
codec g711ulaw
!
!
sip-ua
registrar ipv4:64.206.114.6 expires 3600
Mike Wilusz, CCNA
Networking Systems Programmer
Price Chopper Supermarkets / The Golub Corporation
From: Matt Slaga (US) [mailto:Matt.Slaga at us.didata.com]
Sent: Thursday, October 02, 2008 4:06 PM
To: Wilusz, Mike; cisco-voip at puck.nether.net
Subject: RE: [cisco-voip] Outbound Dial with Carrier SIP Trunk
Try adding this to your config:
voice class codec 1
codec preference 1 g711ulaw
codec preference 2 g729br8
codec preference 3 g729r8
And to your voip dial peers:
voice-class codec 1
From: Wilusz, Mike [mailto:mikewilusz at pricechopper.com]
Sent: Thursday, October 02, 2008 3:42 PM
To: Matt Slaga (US); cisco-voip at puck.nether.net
Subject: RE: [cisco-voip] Outbound Dial with Carrier SIP Trunk
Yup... set here in this dial-peer. Which is matched properly according
to the debug.
dial-peer voice 2 voip
destination-pattern 1..........
session protocol sipv2
session target ipv4:64.206.114.6
dtmf-relay rtp-nte
codec g711ulaw
Mike Wilusz, CCNA
Networking Systems Programmer
Price Chopper Supermarkets / The Golub Corporation
From: Matt Slaga (US) [mailto:Matt.Slaga at us.didata.com]
Sent: Thursday, October 02, 2008 3:40 PM
To: Wilusz, Mike; cisco-voip at puck.nether.net
Subject: RE: [cisco-voip] Outbound Dial with Carrier SIP Trunk
Where are you setting the codec? The line below says you are not using
VCC, are your dial peers specifying a codec?
Oct 2 10:21:18: //10/36ECCAF0801A/SIP/Info/sipSPIGetCallConfig: Not
using Voice Class Codec
From: Wilusz, Mike [mailto:mikewilusz at pricechopper.com]
Sent: Thursday, October 02, 2008 3:35 PM
To: Matt Slaga (US); cisco-voip at puck.nether.net
Subject: RE: [cisco-voip] Outbound Dial with Carrier SIP Trunk
Matt,
Not sure what means. I see g726r32 is selected as a codec...but why? I
don't have the set as my codec on the dial-peer and the carrier is set
(or supposed to be) to the same as me. I guess I'm not really sure what
that line is telling me.
Mike Wilusz, CCNA
Networking Systems Programmer
Price Chopper Supermarkets / The Golub Corporation
From: Matt Slaga (US) [mailto:Matt.Slaga at us.didata.com]
Sent: Thursday, October 02, 2008 3:14 PM
To: Wilusz, Mike; cisco-voip at puck.nether.net
Subject: RE: [cisco-voip] Outbound Dial with Carrier SIP Trunk
Probably this:
Oct 2 10:21:18: //9/36ECCAF0801A/SIP/Info/sipSPISelectDynamicPayload:
Selecting Dynamic Payload : 96 for Codec: g726r32
From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Wilusz, Mike
Sent: Thursday, October 02, 2008 10:31 AM
To: cisco-voip at puck.nether.net
Subject: [cisco-voip] Outbound Dial with Carrier SIP Trunk
Hey All,
We're in the process of trialing a SIP trunk solution from our provider,
PAETEC. I followed the Cisco docs for configuring a CUBE, but we can
only receive calls and not place them. The setup is CUCM 6.1(2) -> SIP
Trunk -> CUBE (2811) -> SIP Trunk -> PAETEC SIP Gateway. I'm very new
to SIP and am trying to analyze the output from debug ccsip all.
Nothing is jumping out at me as the exact reason why the calls outbound
from our CUCM aren't working. Anybody have any ideas?
________________________________
Disclaimer: This e-mail communication and any attachments may contain
confidential and privileged information and is for use by the designated
addressee(s) named above only. If you are not the intended addressee,
you are hereby notified that you have received this communication in
error and that any use or reproduction of this email or its contents is
strictly prohibited and may be unlawful. If you have received this
communication in error, please notify us immediately by replying to this
message and deleting it from your computer. Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20081002/919f5b68/attachment.html>
More information about the cisco-voip
mailing list