cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
97944
Views
16
Helpful
18
Replies
Beginner

Message SIP with 488 Not Acceptable Here

        Hello,I'm having this issue. I read documentation and I search in this forum for similar issues.
Seems is a Codec issue. Service Provider is asking for a g711alaw. However I already change all the codec, configured transcoder which is register with call manager and everything seems fine. But outgoing calls still give this error. Can anyone help me?

Here is part of my configuration:

voice call send-alert

voice call convert-discpi-to-prog

voice rtp send-recv

voice service voip

ip address trusted list

  ipv4 10.20.1.0 255.255.255.0

allow-connections h323 to h323

allow-connections h323 to sip

allow-connections sip to h323

allow-connections sip to sip

supplementary-service h450.12

fax protocol t38 version 0 ls-redundancy 0 hs-redundancy 0 fallback none

h323

  no h225 timeout keepalive

sip

  midcall-signaling passthru

         

sccp local GigabitEthernet0/1

sccp ccm 10.20.1.5 identifier 2 priority 2 version 7.0

sccp ccm 10.20.1.6 identifier 1 priority 1 version 7.0

sccp

!

sccp ccm group 1

associate ccm 1 priority 1

associate profile 1 register COMPcode

associate profile 2 register COMP01-mtp

!

dspfarm profile 1 transcode

codec g711ulaw

codec g711alaw

codec g729ar8

codec g729abr8

codec g729r8

codec g729br8

maximum sessions 14

associate application SCCP

!

dspfarm profile 2 mtp

codec g711ulaw

maximum sessions software 120

associate application SCCP

!

dial-peer voice 50 voip

description ### Calls from CUCM to VG ###

incoming called-number 9.T

dtmf-relay h245-alphanumeric

codec g711alaw

no vad

!

dial-peer voice 11 voip

description **Outgoing Call to SIP Trunk**

translation-profile outgoing SIP-CALLS-OUT

preference 1

destination-pattern 9T

progress_ind setup enable 3

progress_ind progress enable 8

progress_ind connect enable 8

redirect ip2ip

session protocol sipv2

session target ipv4:88.XXX.XX.XXX

dtmf-relay rtp-nte cisco-rtp

codec g711alaw

no vad

The Sip Trunk on call manager is using a MRGL with both MTP and XCODE.

SCCP Admin State: UP
Gateway Local Interface: GigabitEthernet0/1
        IPv4 Address: 10.20.1.11
        Port Number: 2000
IP Precedence: 5
User Masked Codec list: None
Call Manager: 10.20.1.5, Port Number: 2000
                Priority: 2, Version: 7.0, Identifier: 2
Call Manager: 10.20.1.6, Port Number: 2000
                Priority: 1, Version: 7.0, Identifier: 1

Transcoding Oper State: ACTIVE - Cause Code: NONE

Here is the both debugs:

*Dec  3 12:08:32.859: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:907718005555@10.20.1.11:5060 SIP/2.0
Via: SIP/2.0/TCP 10.20.1.6:5060;branch=z9hG4bK148c5e3b74ba77
From: <sip:02036666666@10.20.1.6>;tag=1130165~6e3f6e1b-b59e-4604-be6a-d6295dc18cf6-45522220
To: <sip:907718005555@10.20.1.11>
Date: Mon, 03 Dec 2012 12:02:40 GMT
Call-ID: 54cef580-bc194e0-5fb62-601140a@10.20.1.6
Supported: timer,resource-priority,replaces
Min-SE:  1800
User-Agent: Cisco-CUCM8.6
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
CSeq: 101 INVITE
Expires: 180
Allow-Events: presence, kpml
Supported: X-cisco-srtp-fallback
Supported: Geolocation
Call-Info: <sip:10.20.1.6:5060>;method="NOTIFY;Event=telephone-event;Duration=500"
Cisco-Guid: 1422849408-0000065536-0000391810-0100733962
Session-Expires:  1800
P-Asserted-Identity: <sip:02036666666@10.20.1.6>
Remote-Party-ID: <sip:02036666666@10.20.1.6>;party=calling;screen=yes;privacy=off
Contact: <sip:02036666666@10.20.1.6:5060;transport=tcp>
Max-Forwards: 70
Content-Length: 0


*Dec  3 12:08:32.863: //-1/54CEF5800005/CCAPI/cc_api_display_ie_subfields:
  cc_api_call_setup_ind_common:
  cisco-username=02036666666
  ----- ccCallInfo IE subfields -----
  cisco-ani=02036666666
  cisco-anitype=0
  cisco-aniplan=0
  cisco-anipi=0
  cisco-anisi=1
  dest=907718005555
  cisco-desttype=0
  cisco-destplan=0
  cisco-rdie=FFFFFFFF
  cisco-rdn=
  cisco-rdntype=0
  cisco-rdnplan=0
  cisco-rdnpi=-1
  cisco-rdnsi=-1
  cisco-redirectreason=-1  fwd_final_type =0
  final_redirectNumber =
  hunt_group_timeout =0

*Dec  3 12:08:32.863: //-1/54CEF5800005/CCAPI/cc_api_call_setup_ind_common:
  Interface=0x31196458, Call Info(
  Calling Number=02036666666,(Calling Name=)(TON=Unknown, NPI=Unknown, Screening=User, Passed, Presentation=Allowed),
  Called Number=907718005555(TON=Unknown, NPI=Unknown),
  Calling Translated=FALSE, Subscriber Type Str=Unknown, FinalDestinationFlag=TRUE,
  Incoming Dial-peer=50, Progress Indication=NULL(0), Calling IE Present=TRUE,
  Source Trkgrp Route Label=, Target Trkgrp Route Label=, CLID Transparent=FALSE), Call Id=21355
*Dec  3 12:08:32.863: //-1/54CEF5800005/CCAPI/ccCheckClipClir:
  In: Calling Number=02036666666(TON=Unknown, NPI=Unknown, Screening=User, Passed, Presentation=Allowed)
*Dec  3 12:08:32.863: //-1/54CEF5800005/CCAPI/ccCheckClipClir:
  Out: Calling Number=02036666666(TON=Unknown, NPI=Unknown, Screening=User, Passed, Presentation=Allowed)
*Dec  3 12:08:32.863: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:

*Dec  3 12:08:32.863: :cc_get_feature_vsa malloc success
*Dec  3 12:08:32.863: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:

*Dec  3 12:08:32.863:  cc_get_feature_vsa count is 1
*Dec  3 12:08:32.863: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:

*Dec  3 12:08:32.863: :FEATURE_VSA attributes are: feature_name:0,feature_time:832856160,feature_id:21306
*Dec  3 12:08:32.863: //21355/54CEF5800005/CCAPI/cc_api_call_setup_ind_common:
  Set Up Event Sent;
  Call Info(Calling Number=02036666666(TON=Unknown, NPI=Unknown, Screening=User, Passed, Presentation=Allowed),
  Called Number=907718005555(TON=Unknown, NPI=Unknown))
*Dec  3 12:08:32.863: //21355/54CEF5800005/CCAPI/cc_process_call_setup_ind:
  Event=0x2AFCEB88
*Dec  3 12:08:32.863: //-1/xxxxxxxxxxxx/CCAPI/cc_setupind_match_search:
  Try with the demoted called number 907718005555
*Dec  3 12:08:32.863: //21355/54CEF5800005/CCAPI/ccCallSetContext:
  Context=0x32D52B8C
*Dec  3 12:08:32.863: //21355/54CEF5800005/CCAPI/cc_process_call_setup_ind:
  >>>>CCAPI handed cid 21355 with tag 50 to app "_ManagedAppProcess_Default"
*Dec  3 12:08:32.867: //21355/54CEF5800005/CCAPI/ccCallProceeding:
  Progress Indication=NULL(0)
*Dec  3 12:08:32.867: //21355/54CEF5800005/CCAPI/ccCallSetupRequest:
  Destination=, Calling IE Present=TRUE, Mode=0,
  Outgoing Dial-peer=11, Params=0x2B62716C, Progress Indication=ORIGINATING SIDE IS NON ISDN(3)
*Dec  3 12:08:32.867: //21355/54CEF5800005/CCAPI/ccCheckClipClir:
  In: Calling Number=02036666666(TON=Unknown, NPI=Unknown, Screening=User, Passed, Presentation=Allowed)
*Dec  3 12:08:32.867: //21355/54CEF5800005/CCAPI/ccCheckClipClir:
  Out: Calling Number=02036666666(TON=Unknown, NPI=Unknown, Screening=User, Passed, Presentation=Allowed)
*Dec  3 12:08:32.867: //21355/54CEF5800005/CCAPI/ccCallSetupRequest:
  Destination Pattern=9T, Called Number=07718009863, Digit Strip=FALSE
*Dec  3 12:08:32.867: //21355/54CEF5800005/CCAPI/ccCallSetupRequest:
  Calling Number=02036666666(TON=Unknown, NPI=Unknown, Screening=User, Passed, Presentation=Allowed),
  Called Number=07718009863(TON=Unknown, NPI=Unknown),
  Redirect Number=, Display Info=
  Account Number=02036666666, Final Destination Flag=TRUE,
  Guid=54CEF580-0001-0000-0005-FA820601140A, Outgoing Dial-peer=11
*Dec  3 12:08:32.867: //21355/54CEF5800005/CCAPI/cc_api_display_ie_subfields:
  ccCallSetupRequest:
  cisco-username=02036666666
  ----- ccCallInfo IE subfields -----
  cisco-ani=02036666666
  cisco-anitype=0
  cisco-aniplan=0
  cisco-anipi=0
  cisco-anisi=1
  dest=07718009863
  cisco-desttype=0
  cisco-destplan=0
  cisco-rdie=FFFFFFFF
  cisco-rdn=
  cisco-rdntype=0
  cisco-rdnplan=0
  cisco-rdnpi=-1
  cisco-rdnsi=-1
  cisco-redirectreason=-1  fwd_final_type =0
  final_redirectNumber =
  hunt_group_timeout =0

*Dec  3 12:08:32.867: //21355/54CEF5800005/CCAPI/ccIFCallSetupRequestPrivate:
  Interface=0x31196458, Interface Type=3, Destination=, Mode=0x0,
  Call Params(Calling Number=02036666666,(Calling Name=)(TON=Unknown, NPI=Unknown, Screening=User, Passed, Presentation=Allowed),
  Called Number=07718009863(TON=Unknown, NPI=Unknown), Calling Translated=FALSE,
  Subscriber Type Str=Unknown, FinalDestinationFlag=TRUE, Outgoing Dial-peer=11, Call Count On=FALSE,
  Source Trkgrp Route Label=, Target Trkgrp Route Label=, tg_label_flag=0, Application Call Id=)
*Dec  3 12:08:32.867: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:

*Dec  3 12:08:32.867: :cc_get_feature_vsa malloc success
*Dec  3 12:08:32.867: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:

*Dec  3 12:08:32.867:  cc_get_feature_vsa count is 2
*Dec  3 12:08:32.867: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:

*Dec  3 12:08:32.867: :FEATURE_VSA attributes are: feature_name:0,feature_time:832857952,feature_id:21307
*Dec  3 12:08:32.867: //21356/54CEF5800005/CCAPI/ccIFCallSetupRequestPrivate:
  SPI Call Setup Request Is Success; Interface Type=3, FlowMode=1
*Dec  3 12:08:32.867: //21356/54CEF5800005/CCAPI/ccCallSetContext:
  Context=0x2B62711C
*Dec  3 12:08:32.867: //21355/54CEF5800005/CCAPI/ccSaveDialpeerTag:
  Outgoing Dial-peer=11
*Dec  3 12:08:32.867: //21356/54CEF5800005/CCAPI/cc_api_call_proceeding:
  Interface=0x31196458, Progress Indication=NULL(0)
*Dec  3 12:08:32.871: //21356/54CEF5800005/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:07718009863@88.XXX.XX.XXX:5060 SIP/2.0
Via: SIP/2.0/UDP 194.168.146.148:5060;branch=z9hG4bK4F1C77
Remote-Party-ID: <sip:02036666666@194.168.146.148>;party=calling;screen=yes;privacy=off
From: <sip:02036666666@194.168.146.148>;tag=E448A58-A24
To: <sip:07718009863@88.XXX.XX.XXX>
Date: Mon, 03 Dec 2012 12:08:32 GMT
Call-ID: FDF07C15-3C7811E2-94E3FEC8-F8813FD6@194.168.146.148
Supported: timer,resource-priority,replaces,sdp-anat
Min-SE:  1800
Cisco-Guid: 1422849408-0000065536-0000391810-0100733962
User-Agent: Cisco-SIPGateway/IOS-12.x
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Timestamp: 1354536512
Contact: <sip:02036666666@194.168.146.148:5060>
Expires: 180
Allow-Events: telephone-event
Max-Forwards: 69
Session-Expires:  1800
Content-Length: 0


*Dec  3 12:08:32.871: //21355/54CEF5800005/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 100 Trying
Via: SIP/2.0/TCP 10.20.1.6:5060;branch=z9hG4bK148c5e3b74ba77
From: <sip:02036666666@10.20.1.6>;tag=1130165~6e3f6e1b-b59e-4604-be6a-d6295dc18cf6-45522220
To: <sip:907718005555@10.20.1.11>
Date: Mon, 03 Dec 2012 12:08:32 GMT
Call-ID: 54cef580-bc194e0-5fb62-601140a@10.20.1.6
CSeq: 101 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-12.x
Content-Length: 0


*Dec  3 12:08:32.899: //21356/54CEF5800005/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 194.168.146.148:5060;received=194.168.146.148;branch=z9hG4bK4F1C77
From: <sip:02036666666@194.168.146.148>;tag=E488A58-A24
To: <sip:07718009863@88.XXX.XX.XXX>
Call-ID: FDF07C15-3C7811E2-94E3FEC8-F8813FD6@194.168.146.148
CSeq: 101 INVITE
Timestamp: 1354536512
Content-Length: 0


*Dec  3 12:08:32.995: //21356/54CEF5800005/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 488 Not Acceptable Here
Via: SIP/2.0/UDP 194.168.146.148:5060;received=194.168.146.148;branch=z9hG4bK4F1C77
To: <sip:07718009863@88.XXX.XX.XXX>;tag=3563525093-836070
From: <sip:02036666666@194.168.146.148>;tag=E488A58-A24
Call-ID: FDF07C15-3C7811E2-94E3FEC8-F8813FD6@194.168.146.148
CSeq: 101 INVITE
Allow: CANCEL, ACK, INVITE, BYE, OPTIONS, REGISTER, NOTIFY, INFO, REFER, SUBSCRIBE, PRACK, UPDATE, MESSAGE, PUBLISH
Contact: <sip:07718009863@88.XXX.XX.XXX:5060>
Reason: Q.850;cause=65
Content-Length: 0


*Dec  3 12:08:32.995: //21356/54CEF5800005/CCAPI/cc_api_call_disconnected:
  Cause Value=127, Interface=0x31196458, Call Id=21356
*Dec  3 12:08:32.995: //21356/54CEF5800005/CCAPI/cc_api_call_disconnected:
  Call Entry(Responsed=TRUE, Cause Value=127, Retry Count=0)
*Dec  3 12:08:32.995: //21355/54CEF5800005/CCAPI/ccCallReleaseResources:
  release reserved xcoding resource.
*Dec  3 12:08:32.995: //21356/54CEF5800005/CCAPI/ccCallSetAAA_Accounting:
  Accounting=0, Call Id=21356
*Dec  3 12:08:32.995: //21356/54CEF5800005/CCAPI/ccCallDisconnect:
  Cause Value=127, Tag=0x0, Call Entry(Previous Disconnect Cause=0, Disconnect Cause=127)
*Dec  3 12:08:32.995: //21356/54CEF5800005/CCAPI/ccCallDisconnect:
  Cause Value=127, Call Entry(Responsed=TRUE, Cause Value=127)
*Dec  3 12:08:32.999: //21356/54CEF5800005/CCAPI/cc_api_call_disconnect_done:
  Disposition=0, Interface=0x31196458, Tag=0x0, Call Id=21356,
  Call Entry(Disconnect Cause=127, Voice Class Cause Code=0, Retry Count=0)
*Dec  3 12:08:32.999: //21356/54CEF5800005/CCAPI/cc_api_call_disconnect_done:
  Call Disconnect Event Sent
*Dec  3 12:08:32.999: //-1/xxxxxxxxxxxx/CCAPI/cc_free_feature_vsa:

*Dec  3 12:08:32.999: :cc_free_feature_vsa freeing 31A46758
*Dec  3 12:08:32.999: //-1/xxxxxxxxxxxx/CCAPI/cc_free_feature_vsa:

*Dec  3 12:08:32.999:  vsacount in free is 1
*Dec  3 12:08:32.999: //21355/54CEF5800005/CCAPI/ccCallDisconnect:
  Cause Value=127, Tag=0x0, Call Entry(Previous Disconnect Cause=0, Disconnect Cause=0)
*Dec  3 12:08:32.999: //21355/54CEF5800005/CCAPI/ccCallDisconnect:
  Cause Value=127, Call Entry(Responsed=TRUE, Cause Value=127)
*Dec  3 12:08:32.999: //21355/54CEF5800005/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 500 Internal Server Error
Via: SIP/2.0/TCP 10.20.1.6:5060;branch=z9hG4bK148c5e3b74ba77
From: <sip:02036666666@10.20.1.6>;tag=1130165~6e3f6e1b-b59e-4604-be6a-d6295dc18cf6-45522220
To: <sip:907718005555@10.20.1.11>;tag=E488ADC-CEC
Date: Mon, 03 Dec 2012 12:08:32 GMT
Call-ID: 54cef580-bc194e0-5fb62-601140a@10.20.1.6
CSeq: 101 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-12.x
Reason: Q.850;cause=127
Content-Length: 0


*Dec  3 12:08:33.035: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
ACK sip:907718005555@10.20.1.11:5060 SIP/2.0
Via: SIP/2.0/TCP 10.20.1.6:5060;branch=z9hG4bK148c5e3b74ba77
From: <sip:02036666666@10.20.1.6>;tag=1130165~6e3f6e1b-b59e-4604-be6a-d6295dc18cf6-45522220
To: <sip:907718005555@10.20.1.11>;tag=E488ADC-CEC
Date: Mon, 03 Dec 2012 12:02:40 GMT
Call-ID: 54cef580-bc194e0-5fb62-601140a@10.20.1.6
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: presence, kpml
Content-Length: 0


*Dec  3 12:08:33.039: //21355/54CEF5800005/CCAPI/cc_api_call_disconnect_done:
  Disposition=0, Interface=0x31196458, Tag=0x0, Call Id=21355,
  Call Entry(Disconnect Cause=127, Voice Class Cause Code=0, Retry Count=0)
*Dec  3 12:08:33.039: //21355/54CEF5800005/CCAPI/cc_api_call_disconnect_done:
  Call Disconnect Event Sent
*Dec  3 12:08:33.039: //-1/xxxxxxxxxxxx/CCAPI/cc_free_feature_vsa:

*Dec  3 12:08:33.039: :cc_free_feature_vsa freeing 31A46058
*Dec  3 12:08:33.039: //-1/xxxxxxxxxxxx/CCAPI/cc_free_feature_vsa:

*Dec  3 12:08:33.039:  vsacount in free is 0
*Dec  3 12:08:33.039: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
ACK sip:07718009863@88.XXX.XX.XXX:5060 SIP/2.0
Via: SIP/2.0/UDP 194.168.146.148:5060;branch=z9hG4bK4F1C77
From: <sip:02036666666@194.168.146.148>;tag=E488A58-A24
To: <sip:07718009863@88.XXX.XX.XXX>;tag=3563525093-836070
Date: Mon, 03 Dec 2012 12:08:32 GMT
Call-ID: FDF07C15-3C7811E2-94E3FEC8-F8813FD6@194.168.146.148
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: telephone-event
Content-Length: 0

Many Thanks,

Chris

Everyone's tags (6)
1 ACCEPTED SOLUTION

Accepted Solutions
Cisco Employee

Re: Message SIP with 488 Not Acceptable Here

Hi Chris,

It looks like your CUBE config is correct. The CUCM is sending an Early Offer INVITE now. That means you have enabled MTP on the SIP trunk. The codec being sent in the INVITE is G711ulaw. In order to change this, go to the SIP trunk and look for "MTP Preferred Originating Codec" and change it from default G711ulaw to G711alaw. Hopefully that does the trick for you.

HTH.

Regards,

Harmit.

18 REPLIES
Cisco Employee

Message SIP with 488 Not Acceptable Here

Hi Chris,

Did you check with your ITSP why they are sending 488? Do they want you to send an EO INVITE or is it something else? You should ideally crosscheck with them since they are disconnecting the call.

HTH.

Regards,

Harmit.

Beginner

Re: Message SIP with 488 Not Acceptable Here

Hi checked with them,

Firslty they said I was seding the incorrect codec, so I changed to g711alaw to match their codec.

And now Im getting the debug messages that I posted.

by the way, this is my interfaces:

GigabitEthernet0/1         10.20.1.11      YES NVRAM  up                    up

GigabitEthernet0/2         194.XXX.XXX.XXX YES NVRAM  up                    up

Any clue about where can be the problem? I associated the MRGL_SIP to the trunk as well and confirmed all the codecs are correct but no joy.

Cisco Employee

Re: Message SIP with 488 Not Acceptable Here

Hi Chris,

How about them requiring an EO INVITE? Did you check with them about that? As of now, with the DO, you havent offered any codec in the outbound INVITE:

*Dec  3 12:08:32.871: //21356/54CEF5800005/SIP/Msg/ccsipDisplayMsg:

Sent:

INVITE sip:

07718009863@88.XXX.XX

.XXX:5060 SIP/2.0

Via: SIP/2.0/UDP 194.XXX.XXX.XXX:5060;branch=z9hG4bK4F1C77

Remote-Party-ID: <02036666666>;party=calling;screen=yes;privacy=off

From: <02036666666>;tag=E488A58-A24

To: <>

07718009863@88.XXX.XX

.XXX>

Date: Mon, 03 Dec 2012 12:08:32 GMT

Call-ID:

FDF07C15-3C7811E2-94E3FEC8-F8813FD6@194.168.166.158


Supported: timer,resource-priority,replaces,sdp-anat

Min-SE:  1800

Cisco-Guid: 1422849408-0000065536-0000391810-0100733962

User-Agent: Cisco-SIPGateway/IOS-12.x

Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER

CSeq: 101 INVITE

Timestamp: 1354536512

Contact: <02036666666>

Expires: 180

Allow-Events: telephone-event

Max-Forwards: 69

Session-Expires:  1800

Content-Length: 0

Most ITSPs require SIP Early Offer. I would suggest enabling the same and testing. At the same time, I would also refer you to the following doc to review the different interoperabilites such as DO to EO vs EO to EO vs DO to DO (which is what you currently have):

http://www.cisco.com/en/US/docs/ios/voice/cube/configuration/guide/vb-gw-sipsip.html#wp1443323

HTH.

Regards,
Harmit.

Beginner

Re: Message SIP with 488 Not Acceptable Here

Thanks Harmit for your reply. Let me have a look on that document and try with an EO Invite.
I will give you my feedback as soon as I test it.

Thanks,

Chris

Cisco Employee

Re: Message SIP with 488 Not Acceptable Here

Sure Chris, let me know how it goes.

Regards,
Harmit.

Beginner

Re: Message SIP with 488 Not Acceptable Here

I already contact ITSP about which type of INVITE they are expecting but still waiting for their answer. Meanwhile I tested forcing the EO and no joy, some output.

voice service voip

ip address trusted list

  ipv4 10.20.1.0 255.255.255.0

allow-connections h323 to h323

allow-connections h323 to sip

allow-connections sip to h323

allow-connections sip to sip

supplementary-service h450.12

fax protocol t38 version 0 ls-redundancy 0 hs-redundancy 0 fallback none

h323

  no h225 timeout keepalive

sip

  early-offer forced

  midcall-signaling passthru


Thanks,

Chris

Beginner

Re: Message SIP with 488 Not Acceptable Here

I just reset the trunk and tried again.

Im getting this output now, and it doesnt go to the ITSP.

*Dec  3 14:44:39.054: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:907718005060@10.20.1.11:5060 SIP/2.0
Via: SIP/2.0/TCP 10.20.1.6:5060;branch=z9hG4bK148edb6228bc9b
From: <02036666666>;tag=1130760~6e3f6e1b-b59e-4604-be6a-d6295dc18cf6-45530789
To: <907718005060>
Date: Mon, 03 Dec 2012 14:38:46 GMT
Call-ID: 23612480-bc1b976-5fbe4-601140a@10.20.1.6
Supported: timer,resource-priority,replaces
Min-SE:  1800
User-Agent: Cisco-CUCM8.6
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
CSeq: 101 INVITE
Expires: 180
Allow-Events: presence, kpml
Supported: X-cisco-srtp-fallback
Supported: Geolocation
Cisco-Guid: 0593568896-0000065536-0000391940-0100733962
Session-Expires:  1800
P-Asserted-Identity: <02036666666>
Remote-Party-ID: <02036666666>;party=calling;screen=yes;privacy=off
Contact: <02036666666>
Max-Forwards: 70
Content-Type: application/sdp
Content-Length: 210

v=0
o=CiscoSystemsCCM-SIP 1130760 1 IN IP4 10.20.1.6
s=SIP Call
c=IN IP4 10.20.1.11
t=0 0
m=audio 17330 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000
a=ptime:20
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15

*Dec  3 14:44:39.058: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 488 Not Acceptable Media
Via: SIP/2.0/TCP 10.20.1.6:5060;branch=z9hG4bK148edb6228bc9b
From: <02036666666>;tag=1130760~6e3f6e1b-b59e-4604-be6a-d6295dc18cf6-45530789
To: <907718005060>;tag=ED77508-11AB
Date: Mon, 03 Dec 2012 14:44:39 GMT
Call-ID: 23612480-bc1b976-5fbe4-601140a@10.20.1.6
CSeq: 101 INVITE
Allow-Events: telephone-event
Warning: 304 10.20.1.11 "Media Type(s) Unavailable"
Reason: Q.850;cause=65
Server: Cisco-SIPGateway/IOS-12.x
Content-Length: 0


*Dec  3 14:44:39.062: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
ACK sip:907718005060@10.20.1.11:5060 SIP/2.0
Via: SIP/2.0/TCP 10.20.1.6:5060;branch=z9hG4bK148edb6228bc9b
From: <02036666666>;tag=1130760~6e3f6e1b-b59e-4604-be6a-d6295dc18cf6-45530789
To: <907718005060>;tag=ED77508-11AB
Date: Mon, 03 Dec 2012 14:38:46 GMT
Call-ID: 23612480-bc1b976-5fbe4-601140a@10.20.1.6
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: presence, kpml
Content-Length: 0


Seems a codec issue no? but both dial-peers are force to use g711alaw...

Beginner

Re: Message SIP with 488 Not Acceptable Here

The ITSP reply was:

You are sending us a INVITE without SDP, you need to send an INVITE with SDP specifying the G711Alaw.

This refers to the early media? How to acchieve this?

Thanks!

Chris

Cisco Employee

Re: Message SIP with 488 Not Acceptable Here

Hi Chris,

Yes, thats exactly what I said, ITSPs want Early Offer INVITEs. They use this to always decide on which codec to offer for the calls. If you set up your CUBE to do Early Offer, it will send the SDP with the INVITE.

As for the configuration, the document I provided covers it nicely:

Configuring Delayed-Offer to Early-Offer for SIP Audio Calls at the Global Level

To configure Delayed-Offer to Early-Offer for SIP Audio Calls at the global level, perform the steps in this section.

SUMMARY STEPS

1. enable

2. configure terminal

3. voice service voip

4. allow-connections sip

5. early-offer forced

6. exit

Configuring Delayed-Offer to Early-Offer for SIP Audio Calls at the Global Level

To configure Delayed-Offer to Early-Offer for SIP Audio Calls at the global level, perform the steps in this section.

SUMMARY STEPS

1. enable

2. configure terminal

3. voice service voip

4. allow-connections sip

5. early-offer forced

6. exit

HTH.

Regards,

Harmit.

Beginner

Re: Message SIP with 488 Not Acceptable Here

So I spoke with them right now.
The situation is now i'm sending SDP with the INVITE but codec g711ulaw. My current config is:

voice class codec 1

codec preference 1 g711ulaw

codec preference 2 g711alaw

codec preference 3 g729r8

dial-peer voice 11 voip

description **Outgoing Call to SIP Trunk**

translation-profile outgoing SIP-CALLS-OUT

preference 1

destination-pattern 9T

progress_ind setup enable 3

progress_ind progress enable 8

progress_ind connect enable 8

redirect ip2ip

session protocol sipv2

session target ipv4:88.XXX.XX.XXX

voice-class codec 1

dtmf-relay rtp-nte cisco-rtp

no vad

!

dial-peer voice 70 voip

description *** Inbound from CUCM Publisher ***

redirect ip2ip

session protocol sipv2

session target ipv4:10.20.1.6

incoming called-number 9.T

voice-class codec 1

dtmf-relay rtp-nte cisco-rtp

no vad

Which seems Im forcing the g711ulaw codec, so thats normal they are receiving g711ulaw...

the problem is when I force dial peers to use g711alaw  :

dial-peer voice 11 voip

description **Outgoing Call to SIP Trunk**

translation-profile outgoing SIP-CALLS-OUT

preference 1

destination-pattern 9T

progress_ind setup enable 3

progress_ind progress enable 8

progress_ind connect enable 8

redirect ip2ip

session protocol sipv2

session target ipv4:88.XXX.XXX.XXX

codec g711alaw

dtmf-relay rtp-nte cisco-rtp

no vad

!

dial-peer voice 70 voip

description *** Inbound from CUCM Publisher ***

redirect ip2ip

session protocol sipv2

session target ipv4:10.20.1.6

incoming called-number 9.T

codec g711alaw

dtmf-relay rtp-nte cisco-rtp

no vad


I get this output:

*Dec  3 17:49:09.434: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:907718005040@10.20.1.11:5060 SIP/2.0
Via: SIP/2.0/TCP 10.20.1.6:5060;branch=z9hG4bK1495f22438c023
From: <02036666666>;tag=1132383~6e3f6e1b-b59e-4604-be6a-d6295dc18cf6-45551154
To: <907718005040>
Date: Mon, 03 Dec 2012 17:43:16 GMT
Call-ID: e99d1780-bc1e4b4-5fde3-601140a@10.20.1.6
Supported: timer,resource-priority,replaces
Min-SE:  1800
User-Agent: Cisco-CUCM8.6
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
CSeq: 101 INVITE
Expires: 180
Allow-Events: presence, kpml
Supported: X-cisco-srtp-fallback
Supported: Geolocation
Cisco-Guid: 3919386496-0000065536-0000392451-0100733962
Session-Expires:  1800
P-Asserted-Identity: <02036666666>
Remote-Party-ID: <02036666666>;party=calling;screen=yes;privacy=off
Contact: <02036666666>
Max-Forwards: 70
Content-Type: application/sdp
Content-Length: 210

v=0
o=CiscoSystemsCCM-SIP 1132383 1 IN IP4 10.20.1.6
s=SIP Call
c=IN IP4 10.20.1.11
t=0 0
m=audio 32680 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000
a=ptime:20
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15

*Dec  3 17:49:09.438: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 488 Not Acceptable Media
Via: SIP/2.0/TCP 10.20.1.6:5060;branch=z9hG4bK1495f22438c023
From: <02036666666>;tag=1132383~6e3f6e1b-b59e-4604-be6a-d6295dc18cf6-45551154
To: <907718005040>;tag=F8060B4-DFA
Date: Mon, 03 Dec 2012 17:49:09 GMT
Call-ID: e99d1780-bc1e4b4-5fde3-601140a@10.20.1.6
CSeq: 101 INVITE
Allow-Events: telephone-event
Warning: 304 10.20.1.11 "Media Type(s) Unavailable"
Reason: Q.850;cause=65
Server: Cisco-SIPGateway/IOS-12.x
Content-Length: 0


*Dec  3 17:49:09.442: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
ACK sip:907718005040@10.20.1.11:5060 SIP/2.0
Via: SIP/2.0/TCP 10.20.1.6:5060;branch=z9hG4bK1495f22438c023
From: <02036666666>;tag=1132383~6e3f6e1b-b59e-4604-be6a-d6295dc18cf6-45551154
To: <907718005040>;tag=F8060B4-DFA
Date: Mon, 03 Dec 2012 17:43:16 GMT
Call-ID: e99d1780-bc1e4b4-5fde3-601140a@10.20.1.6
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: presence, kpml
Content-Length: 0


It doesnt even go to the ISTP.

Any idea?

Many thanks.

Cisco Employee

Re: Message SIP with 488 Not Acceptable Here

Hi Chris,

It looks like your CUBE config is correct. The CUCM is sending an Early Offer INVITE now. That means you have enabled MTP on the SIP trunk. The codec being sent in the INVITE is G711ulaw. In order to change this, go to the SIP trunk and look for "MTP Preferred Originating Codec" and change it from default G711ulaw to G711alaw. Hopefully that does the trick for you.

HTH.

Regards,

Harmit.

Beginner

Message SIP with 488 Not Acceptable Here

Hi Harmit,

Why the invite message is not taking the codec configured under the dial-peer, even though it is hard coded to g711alaw, please advise...

cheers,

Shaggy

Cisco Employee

Message SIP with 488 Not Acceptable Here

Hi Raja,

That's because for the call leg in question, CUCM is advertising G711ulaw (as per the SIP trunk MTP preferred codec) and CUBE has G711alaw hardcoded on the incoming dialpeer. Hence it is a mismatch on the incoming call leg itself and it doesnt create an outgoing call leg between CUBE and ITSP.

Regards,

Harmit.

Beginner

Message SIP with 488 Not Acceptable Here

Hi Harmit,

                         Got it, thank you very much , I have issue with a polycom SIP phone, the device got unregistered recently, it was working fine, I tried rebooting the phone remotely and collected logs from CUCM, I wasn't able to find any REGISTER request from the Polycom SIP device, I will provide the error code in the device log of the SIP phone in a while.

Cheers,

Shaggy

CreatePlease to create content
Ask the Expert- Webex Hybrid Services Solutions