[cisco-voip] Outbound Dial with Carrier SIP Trunk

Matt Slaga (US) Matt.Slaga at us.didata.com
Thu Oct 2 16:03:35 EDT 2008


It should go 

 

SIP 100 - Invite

SIP 183 - Session Progress

SIP 180 - Ringing

 

Yours appears to be 

SIP 100 - Invite

SIP 183 - Session Progress

SIP 183 - Session Progress

SIP 183 - Session Progress

 

What is the codec on the internal side?  I'm seeing RTPMAPs on your 10
network for 8 codecs, and incoming from your provider 3 supported codecs
(G711ulaw, G711alaw and G729).

 

It appears that your provider is attempting G729 to connect and
continues to send you SIP 183s.

 

Can you send a sanitized config?

 

Also, I removed the debug from below so the list moderator won't have to
keep approving these for size.

 

 

 

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?

 

=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2008.10.02 10:21:09
=~=~=~=~=~=~=~=~=~=~=~=

 

our computer. Thank you. 




-----------------------------------------
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/20622be8/attachment.html>


More information about the cisco-voip mailing list