09-08-2017 08:30 AM - edited 03-17-2019 11:08 AM
Hello,
We use the manager in version 11 and CUBE with SIP Provider.
If the users activate the forwarding of the calls, our provider drops the calls.
In the logs, we see that the CCM is sending the outgoing calls without SDP. The provider rejects this however (Warning: 399 arcor.de " Protocol Error: Media unsupported ").
Here our debug from ccsip
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>176: *Sep 8 14:46:16.727: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>177: Received:
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>178: INVITE sip:+492YYYYYYYYYY@213.23.114.5:5060 SIP/2.0
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>179: Via: SIP/2.0/UDP 176.95.48.106:5060;branch=z9hG4bKu18hs7101gn2o83m0940.1;origin=172.19.127.110
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>180: To: <sip:+492YYYYYYYYYY@xxxxx.arcor.de;user=phone>
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>181: From: <sip:+492XXXXXXXXX@arcor.de;user=phone>;tag=SDehm0b01-25df2522
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>182: Call-ID: SDehm0b01-1d9a46b07d043a9ec0bd108901976315-ct46om0010
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>183: CSeq: 1 INVITE
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>184: Max-Forwards: 69
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>185: Contact: <sip:02XXXXXXXXX@176.95.48.106:5060;transport=udp>
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>186: Date: Fri, 8 Sep 2017 16:52:47 GMT
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>187: Allow: INVITE, ACK, PRACK, CANCEL, BYE, OPT
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>188: IONS, MESSAGE, NOTIFY, UPDATE, REGISTER, INFO, REFER, SUBSCRIBE
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>189: Supported: resource-priority,100rel
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>190: Accept: application/dtmf-relay,application/sdp,application/xml,application/media_control+xml
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>191: Content-Type: application/sdp
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>192: Content-Length: 204
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>193:
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>194: v=0
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>195: o=- 0 141399358 IN IP4 176.95.48.106
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>196: s=IMSS
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>197: c=IN IP4 176.95.48.106
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>198: t=0 0
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>199: m=audio 55038 RTP/AVP 8 101 18 106
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>200: a=rtpmap:101 G726-32/8000
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>201: a=rtpmap:106 telephone-event/8000
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>202: a=sendrecv
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>203: a=ptime:20
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>204: *Sep 8 14:46:16.735: //58/4D9BFEB6803B/SIP/Msg/ccsipDisplayMsg:
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>205: Sent:
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>206: SIP/2.0 100 Trying
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>207: Via: SIP/2.0/UDP 176.95.48.106:5060;branch=z9hG4bKu18hs7101gn2o83m0940.1;origin=172.19.127.110
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>208: From: <sip:+492XXXXXXXXX@arcor.de;user=phone>;tag=SDehm0b01-25df2522
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>209: To: <sip:+492YYYYYYYYYY@xxxxx.arcor.de;user=phone>
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>210: Date: Fri, 08 Sep 2017 14:46:16 GMT
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>211: Call-ID: SDehm0b01-1d9a46b07d043a9ec0bd108901976315-ct46om0010
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>212: CSeq: 1 INVITE
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>213: Allow-Events: telephone-event
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>214: Server: Cisco-SIPGateway/IOS-15.5.1.T2
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>215: Content-Length: 0
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>216:
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>217: *Sep 8 14:46:16.739: //59/4D9BFEB6803B/SIP/Msg/ccsipDisplayMsg:
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>218: Sent:
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>219: INVITE sip:242@10.49.49.5:5060 SIP/2.0
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>220: Via: SIP/2.0/UDP 10.49.49.2:5060;branch=z9hG4bK25BE5
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>221: From: <sip:002XXXXXXXXX@10.49.49.2>;tag=69A34-662
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>222: To: <sip:242@10.49.49.5>
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>223: Date: Fri, 08 Sep 2017 14:46:16 GMT
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>224: Call-ID: 4D9DD32E-93DB11E7-80418F25-5A3A66CE@10.49.49.2
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>225: Supported: 100rel,timer,resource-priority,replaces
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>226: Min-SE: 1800
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>227: Cisco-Guid: 1302068918-2480607719-2151386917-1513776846
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>228: User-Agent: Cisco-SIPGateway/IOS-15.5.1.T2
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>229: Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTI
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>230: FY, INFO, REGISTER
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>231: CSeq: 101 INVITE
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>232: Timestamp: 1504881976
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>233: Contact: <sip:002XXXXXXXXX@10.49.49.2:5060>
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>234: Expires: 180
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>235: Allow-Events: telephone-event
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>236: Max-Forwards: 68
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>237: P-Asserted-Identity: <sip:002XXXXXXXXX@10.49.49.2>
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>238: Content-Type: application/sdp
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>239: Content-Disposition: session;handling=required
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>240: Content-Length: 293
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>241:
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>242: v=0
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>243: o=CiscoSystemsSIP-GW-UserAgent 139 7665 IN IP4 10.49.49.2
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>244: s=SIP Call
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>245: c=IN IP4 176.95.48.106
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>246: t=0 0
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>247: m=audio 55038 RTP/AVP 8 18 101
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>248: c=IN IP4 176.95.48.106
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>249: a=rtpmap:8 PCMA/8000
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>250: a=rtpmap:18 G729/8000
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>251: a=fmtp:18 annexb=no
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>252: a=rtpmap:101 telephone-event/8000
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>253: a=fmtp:101 0-16
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>254: a=ptime:20
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>255: *Sep 8 14:46:16.743: //59/4D9BFEB6803B/SIP/Msg/ccsipDisplayMsg:
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>256: Received:
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>257: SIP/2.0 100 Trying
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>258: Via: SIP/2.0/UDP 10.49.49.2:5060;branch=z9hG4bK25BE5
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>259: From: <sip:002XXXXXXXXX@10.49.49.2>;tag=69A34-662
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>260: To: <sip:242@10.49.49.5>
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>261: Date: Fri, 08 Sep 2017 14:52:47 GMT
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>262: Call-ID: 4D9DD32E-93DB11E7-80418F25-5A3A66CE@10.49.49.2
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>263: CSeq: 101 INVITE
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>264: Allow-Events: presence
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>265: Content-Length: 0
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>266:
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>267: *Sep 8 14:46:16.807: //61/008F6C5F9900/SIP/Msg/ccsipDisplayMsg:
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>268: Sent:
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>269: INVITE sip:0173ZZZZZZZ@176.95.48.106:5060 SIP/2.0
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>270: Via: SIP/2.0/UDP 213.23.114.5:5060;branch=z9hG4bK2639B
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>271: From: <sip:002XXXXXXXXX@213.23.114.5>;tag=69A78-188E
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>272: To: <sip:0173ZZZZZZZ@176.95.48.106>
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>273: Date: Fri, 08 Sep 2017 14:46:16 GMT
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>274: Call-ID: 4DA8339F-93DB11E7-80448F25-5A3A66CE@213.23.114.5
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>275: Supported: 100rel,timer,resource-priority,replaces
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>276: Min-SE: 1800
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>277: Cisco-Guid: 0009399391-3215860123-2566953217-0170995970
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>278: User-Agent: Cisco-SIPGateway/IOS-15.5.1.T2
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>279: Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, U
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>280: PDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>281: CSeq: 101 INVITE
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>282: Max-Forwards: 70
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>283: Timestamp: 1504881976
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>284: Contact: <sip:002XXXXXXXXX@213.23.114.5:5060>
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>285: Expires: 180
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>286: Allow-Events: telephone-event
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>287: P-Asserted-Identity: <sip:002XXXXXXXXX@213.23.114.5>
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>288: Content-Type: application/gtd
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>289: Content-Disposition: signal;handling=optional
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>290: Content-Length: 42
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>291:
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>292: IAM,
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>293: GEA,trs3,00,1,y,y,1,002XXXXXXXXX
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>294:
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>295: *Sep 8 14:46:16.819: //61/008F6C5F9900/SIP/Msg/ccsipDisplayMsg:
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>296: Received:
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>297: SIP/2.0 100 Trying
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>298: Via: SIP/2.0/UDP 213.23.114.5:5060;branch=z9hG4bK2639B
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>299: From: <sip:002XXXXXXXXX@213.23.114.5>;tag=69A78-188E
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>300: To: <sip:0173ZZZZZZZ@176.95.48.106>
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>301: Call-ID: 4DA8339F-93DB11E7-80448F25-5A3A66CE@213.23.114.5
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>302: CSeq: 101 INVITE
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>303: Timestamp: 1504881976
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>304:
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>305: *Sep 8 14:46:16.835: //61/008F6C5F9900/SIP/Msg/ccsipDisplayMsg:
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>306: Received:
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>307: SIP/2.0 415 Unsupported Media Type
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>308: Via: SIP/2.0/UDP 213.23.114.5:5060;branch=z9hG4bK2639B
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>309: From: <sip:002XXXXXXXXX@213.23.114.5>;tag=69A78-188E
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>310: To: <sip:0173ZZZZZZZ@176.95.48.106>;tag=SD2jts799-cb0f9eca-0014-010b-0000-0000
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>311: Call-ID: 4DA8339F-93DB11E7-80448F25-5A3A66CE@213.23.114.5
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>312: CSeq: 101 INVITE
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>313: Timestamp: 1504881976
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>314: Server: SSW/0.0.0
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>315: Warning: 399 arcor.de " Protocol Error: Media unsupported "
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>316: Accept: application/sdp, application/isup, application/xml, application/media_control+xml
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>317: Content-Length: 0
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>318:
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>319: *Sep 8 14:46:16.839: //61/008F6C5F9900/SIP/Msg/ccsipDisplayMsg:
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>320: Sent:
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>321: ACK sip:0173ZZZZZZZ@176.95.48.106:5060 SIP/2.0
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>322: Via: SIP/2.0/UDP 213.23.114.5:5060;branch=z9hG4bK2639B
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>323: From: <sip:002XXXXXXXXX@213.23.114.5>;tag=69A78-188E
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>324: To: <sip:0173ZZZZZZZ@176.95.48.106>;tag=SD2jts799-cb0f9eca-0014-010b-0000-0000
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>325: Date: Fri, 08 Sep 2017 14:46:16 GMT
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>326: Call-ID: 4DA8339F-93DB11E7-80448F25-5A3A66CE@213.23.114.5
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>327: Max-Forwards: 70
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>328: CSeq: 101 ACK
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>329: Allow-Events: telephone-event
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>330: Content-Length: 0
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>331:
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>332: *Sep 8 14:46:16.839: //61/008F6C5F9900/SIP/Msg/ccsipDisplayMsg:
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>333: Sent:
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>334: INVITE sip:0173ZZZZZZZ@176.95.48.106:5060 SIP/2.0
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>335: Via: SIP/2.0/UDP 213.23.114.5:5060;branch=z9hG4bK271CA1
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>336: From: <sip:002XXXXXXXXX@213.23.114.5>;tag=69A94-E6A
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>337: To: <sip:0173ZZZZZZZ@176.95.48.106>
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>338: Date: Fri, 08 Sep 2017 14:46:16 GMT
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>339: Call-ID: 4DA8339F-93DB11E7-80448F25-5A3A66CE@213.23.114.5
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>340: Supported: 100rel,timer,resource-priority,replaces
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>341: Min-SE: 1800
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>342: Cisco-Guid: 0009399391-3215860123-2566953217-0170995970
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>343: User-Agent: Cisco-SIPGateway/IOS-15.5.1.T2
Fri Sep 08 16:52:47 2017;10.49.49.2; <191>344: Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, U
Fri Sep 08 16:52:48 2017;10.49.49.2; <191>345: PDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Fri Sep 08 16:52:48 2017;10.49.49.2; <191>346: CSeq: 102 INVITE
Fri Sep 08 16:52:48 2017;10.49.49.2; <191>347: Max-Forwards: 70
Fri Sep 08 16:52:48 2017;10.49.49.2; <191>348: Timestamp: 1504881976
Fri Sep 08 16:52:48 2017;10.49.49.2; <191>349: Contact: <sip:002XXXXXXXXX@213.23.114.5:5060>
Fri Sep 08 16:52:48 2017;10.49.49.2; <191>350: Expires: 180
Fri Sep 08 16:52:48 2017;10.49.49.2; <191>351: Allow-Events: telephone-event
Fri Sep 08 16:52:48 2017;10.49.49.2; <191>352: P-Asserted-Identity: <sip:002XXXXXXXXX@213.23.114.5>
Fri Sep 08 16:52:48 2017;10.49.49.2; <191>353: Content-Length: 0
What can you adjust to get the SDP again?
09-08-2017 10:42 AM
In SIP trunk configuration on CUCM check the box "Media Termination Point Required".
Brandon
10-16-2017 09:38 AM
Same problem
09-09-2017 08:03 AM
Does the "SIP Trunk Profile" assigned to the SIP trunk has "early offer" enabled?
10-16-2017 09:36 AM
No.
09-09-2017 08:25 PM
Hi,
Your call is rejected because your invite message is containing MIME for GTD. Looking at content-type header it mentions application/gtd. You provider isn't accepting GTD encapsulation.
GTD is usually used when you have ISDN User Parameters (ISUP) to pass over SIP networks. CUBE is passing it through but provider not accepting it.
But I am still confused as you mentioned, users in CUCM while GTD comes from ISDN. Can you detail your setup and call flow.
10-16-2017 09:41 AM
Hi,
we dont use ISDN. Our cube is connected via sip to provider.
It happenes only if we forward our calls to external numbers. Our provider does not accept our sip invites, because sdp information missed.
03-02-2018 12:33 PM
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