09-16-2012 06:07 AM - edited 03-16-2019 01:13 PM
Can anyone assist, I have a call manager express version 8.6 IOS 15.1.4T and i am trying to connect directly to a Gamma provided SIP gateway in the UK. The config looks ok, debugs indicate calls hitting our router but dont get any ringing??
My questions, firstly is this a supported setup I am using config guides from version 4 CME??
Secondly, any assistance with the debugs.
thanks in advance.
Solved! Go to Solution.
09-18-2012 05:22 AM
The transode is not assosiated yet
About Trnasoding:
voice-card 0
no dspfarm
dsp services dspfarm
!
sccp local GigabitEthernet0/0
sccp ccm 172.28.6.200 priority 1 version 7.0
sccp
!
sccp ccm group 1
associate ccm 1 priority 1
associate profile 1 register Trans
!
dspfarm profile 1 transcode
description ***** Transcoder *****
codec g729r8
codec g729abr8
codec g729ar8
codec g711alaw
codec g711ulaw
maximum sessions 5
associate application SCCP
no shut
!
telephony-service
sdspfarm units 1
sdspfarm tag trans
sdspfarm transcode sessions 4
!
no sccp
sccp
09-18-2012 05:16 AM
Ok
*Its a PSTN number the 02079930678?
*Remove the g729
*Did you try this command?
*Under sip-ua config add the below command if you have issues to dial any pstn number
calling-info pstn-to-sip from number set <-calling number->
Need the sip-ua register status
09-18-2012 05:21 AM
this is our new approved SIP number 02079930678
not tried the calling info
sip-ua register status
DL-VG#sh sip-ua register status
Line peer expires(sec) registered P-Associ-URI
================================ ========== ============ ========== ============
0 20001 2 no
02079626001 20005 2 no
02079626011 20017 2 no
02079626014 20019 2 no
02079626016 20023 30 no
02079626017 20025 179 no
02079626019 20027 169 no
02079626020 20029 169 no
02079626027 20033 169 no
02079626030 20035 4 no
02079626034 20037 1 no
02079626042 20042 1 no
02079626047 20046 177 no
02079626052 20050 177 no
02079626053 20052 177 no
02079626054 20054 14 no
02079626055 20056 14 no
02079626057 20058 14 no
02079626058 20060 9 no
02079626061 20066 164 no
02079626062 20068 20 no
02079626063 20070 171 no
02079626064 20072 165 no
02079626065 20074 6 no
02079626071 20082 168 no
02079626072 20084 168 no
02079626073 20086 11 no
02079626079 20094 11 no
02079626080 20096 20 no
02079626081 20098 25 no
02079626082 20100 173 no
02079626093 20108 173 no
02079626098 20114 174 no
6001 20004 2 no
6011 20016 2 no
6014 20018 2 no
6016 20022 30 no
6017 20024 30 no
6019 20026 169 no
6020 20028 169 no
6027 20032 169 no
6030 20034 4 no
6034 20036 4 no
6042 20041 1 no
6047 20045 177 no
6052 20049 177 no
6053 20051 177 no
6054 20053 177 no
6055 20055 14 no
6057 20057 14 no
6058 20059 14 no
6061 20065 9 no
6062 20067 20 no
6063 20069 171 no
6064 20071 171 no
6065 20073 165 no
6071 20081 168 no
6072 20083 168 no
6073 20085 19 no
6079 20093 11 no
6080 20095 20 no
6081 20097 25 no
6082 20099 173 no
6093 20107 173 no
6098 20113 20 no
6601 20115 174 no
DL-VG#sh sip-ua register status
Line peer expires(sec) registered P-Associ-URI
================================ ========== ============ ========== ============
0 20001 2 no
02079626001 20005 2 no
02079626011 20017 2 no
02079626014 20019 2 no
02079626016 20023 30 no
02079626017 20025 179 no
02079626019 20027 169 no
02079626020 20029 169 no
02079626027 20033 169 no
02079626030 20035 4 no
02079626034 20037 1 no
02079626042 20042 1 no
02079626047 20046 177 no
02079626052 20050 177 no
02079626053 20052 177 no
02079626054 20054 14 no
02079626055 20056 14 no
02079626057 20058 14 no
02079626058 20060 9 no
02079626061 20066 164 no
02079626062 20068 20 no
02079626063 20070 171 no
02079626064 20072 165 no
02079626065 20074 6 no
02079626071 20082 168 no
02079626072 20084 168 no
02079626073 20086 11 no
02079626079 20094 11 no
02079626080 20096 20 no
02079626081 20098 25 no
02079626082 20100 173 no
02079626093 20108 173 no
02079626098 20114 174 no
6001 20004 2 no
6011 20016 2 no
6014 20018 2 no
6016 20022 30 no
6017 20024 30 no
6019 20026 169 no
6020 20028 169 no
6027 20032 169 no
6030 20034 4 no
6034 20036 4 no
6042 20041 1 no
6047 20045 177 no
6052 20049 177 no
6053 20051 177 no
6054 20053 177 no
6055 20055 14 no
6057 20057 14 no
6058 20059 14 no
6061 20065 9 no
6062 20067 20 no
6063 20069 171 no
6064 20071 171 no
6065 20073 165 no
6071 20081 168 no
6072 20083 168 no
6073 20085 19 no
6079 20093 11 no
6080 20095 20 no
6081 20097 25 no
6082 20099 173 no
6093 20107 173 no
6098 20113 20 no
6601 20115 174 no
09-18-2012 05:28 AM
I dont see that your sip trunk is registered
You have first to register your sip trunk
i dont know if you have any credentials for the sip registration
if you register only a number then first you have to register this number and then try any calls
Example:
ephone-dn 597
number 22552578962
description SIP Main Number registration
preference 1
Also numbers that you dont want to try for rregistration you have to config the below
Example:
ephone-dn 4 dual-line
number x.x.x.x no-reg primary
09-18-2012 05:38 AM
I originally set this number as a phone i have re-done this and it does not register. All the info i was give was an IP address and a number stating no username or password to register.
new output from sip-ua register status
02079930678 20117 18 no
09-18-2012 05:44 AM
Hi
So its not register at all
You dont have a support from the other end?
Also did you have a routing for their network?
ip route
09-18-2012 05:56 AM
not at all, i still get ringing on my phone?
The only routing issue is we run CCME on interface g0/0 and internet on g0/1
default route 0.0.0.0 to g0/1
internal phone routes 172.28.0.0 g0/0
if you understand. One of my original thought was because we are routing it was not getting to the phone but we get ring tone from the phone.
09-18-2012 06:06 AM
is it a registration failure
Sep 19 15:03:10: //-1/xxxxxxxxxxxx/SIP/Error/act_register_send_msg_failure: Send Error to 87.238.219.194:5060 for transport UDP
Sep 19 15:03:10: //58683/000000000000/SIP/Error/ccsip_api_register_result_ind: Message Code Class 4xx Method Code 100 received for REGISTER
Sep 19 15:03:10: //58683/000000000000/SIP/Error/sipSPIRegPthruProcessResponse: Error NO RPCB
Sep 19 15:03:12: //-1/xxxxxxxxxxxx/SIP/Error/HandleUdpSocketWrites: Send failed errno 261
Sep 19 15:03:12: //-1/xxxxxxxxxxxx/SIP/Error/act_register_send_msg_failure: Send Error to 87.238.219.194:5060 for transport UDP
Sep 19 15:03:12: //58684/000000000000/SIP/Error/ccsip_api_register_result_ind: Message Code Class 4xx Method Code 100 received for REGISTER
Sep 19 15:03:12: //58684/000000000000/SIP/Error/sipSPIRegPthruProcessResponse: Error NO RPCB
Sep 19 15:03:12: //-1/xxxxxxxxxxxx/SIP/Error/act_register_send_msg_failure: Send Error to 87.238.219.194:5060 for transport UDP
Sep 19 15:03:12: //58685/000000000000/SIP/Error/ccsip_api_register_result_ind: Message Code Class 4xx Method Code 100 received for REGISTER
Sep 19 15:03:12: //58685/000000000000/SIP/Error/sipSPIRegPthruProcessResponse: Error NO RPCB
Sep 19 15:03:15: //-1/xxxxxxxxxxxx/SIP/Error/HandleUdpSocketWrites: Send failed errno 261
Sep 19 15:03:15: //-1/xxxxxxxxxxxx/SIP/Error/act_register_send_msg_failure: Send Error to 87.238.219.194:5060 for transport UDP
Sep 19 15:03:15: //58686/000000000000/SIP/Error/ccsip_api_register_result_ind: Message Code Class 4xx Method Code 100 received for REGISTER
Sep 19 15:03:15: //58686/000000000000/SIP/Error/sipSPIRegPthruProcessResponse: Error NO RPCB
Sep 19 15:03:15: //-1/xxxxxxxxxxxx/SIP/Error/act_register_send_msg_failure: Send Error to 87.238.219.194:5060 for transport UDP
Sep 19 15:03:15: //58687/000000000000/SIP/Error/ccsip_api_register_result_ind: Message Code Class 4xx Method Code 100 received for REGISTER
Sep 19 15:03:15: //58687/000000000000/SIP/Error/sipSPIRegPthruProcessResponse: Error NO RPCB
Sep 19 15:03:15: //-1/xxxxxxxxxxxx/SIP/Error/act_register_send_msg_failure: Send Error to 87.238.219.194:5060 for transport UDP
Sep 19 15:03:15: //58688/000000000000/SIP/Error/ccsip_api_register_result_ind: Message Code Class 4xx Method Code 100 received for REGISTER
Sep 19 15:03:15: //58688/000000000000/SIP/Error/sipSPIRegPthruProcessResponse: Error NO RPCB
Sep 19 15:03:15: //-1/xxxxxxxxxxxx/SIP/Error/act_register_send_msg_failure: Send Error to 87.238.219.194:5060 for transport UDP
Sep 19 15:03:15: //58689/000000000000/SIP/Error/ccsip_api_register_result_ind: Message Code Class 4xx Method Code 100 received for REGISTER
Sep 19 15:03:15: //58689/000000000000/SIP/Error/sipSPIRegPthruProcessResponse: Error NO RPCB
09-18-2012 06:22 AM
Yes its a registration failure
I Believe that the other end blocking this registration
Can u contact them?
09-18-2012 06:23 AM
Did you resolve this issue ?
09-18-2012 06:55 AM
no not yet speaking to provider?
09-18-2012 07:00 AM
OK. Good - was going to say that the SIP Service Provider should be helping you with this.
09-19-2012 12:23 AM
Did the provider found the problem?
09-19-2012 01:37 AM
I did raise it with the provider and within 2 minutes we had a resolution. Our internet provision was using an 887 router there was a known bug for 887 routers and g729 calls to CUCME. I am still looking for the bug ID as this is so specific but the resolution is an upgrade of the ADSL to the very latest version of software. The engineer informed me that this was a modification in the SIP packet that was rejected by the ADSL router and thats why we got ringing but no call setup following.
Upgrade resolved the issues.
thanks for all your advice and assistance with this, i will be using and assisting more often on the forums in future.
09-19-2012 07:41 AM
hi pmartland's
you are always Welcome
Glad to hear that your problem get solved
My advice is to use this forum more often because here you will find thousands experts to assist you with any issues that you will have
ALso pls check this tread as answered in order to help other guys in the near feature which may have the same issue with you to read this tread and solve also their problem
Regards
chrysostomos
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide