Incoming Calls, SIP Trunk, UC520

azaghul

I've bee trying to get this working over the past few weeks without success...

I've manually configured a UC520, have a couple of phones set up and working, in/outbound & internal calls working fine.

Have directed my PSTN line to x101...works OK, redirects to CUE OK.
Have setup a SIP trunk via my ISP and have directed it to x101....works OK, however forwarding to CUE fails with a message played by my ISP

Also getting no MWI notification, and not detecting call release...grrrrr....

Been pulling out what hair I have left with different configs....no doubt its starring right at me....time to ask for assistance....

shodown

do a debug CCSIP messages so we can see what happens when the call comes in.

Also do you have

Voip service voip
allow connections sip to sip


?

azaghul

allow connections sip to sip is in place...

i'ts one thing to study for the exams in the lab, another to actually put it to use...

OK, I've stripped out the calling/called numbers and my IP address, and replaced them with tags:
[CALLING NUMBER] [CALLED NUMBER] [MY IP ADDRESS]

I've added line breaks at line 240 where the [CALLED NUMBER] is first hit, and line 1600 where the [CALLED NUMBER] is last referenced

syslog-Copy - Download - 4shared

all assistance appreciated
cheers!

azaghul

I've managed to trim down the debugs by about 75%,

there seem to be a lot of "send/receive pairs" registration attempts for my voip dial-peers with a "400 bad request" response from the ISP,
there are also a few sip : ping's from the ISP with what looks like a capabilities exchange response from the UC520

At the time of disconnect I'm sending a
"503 Service Unavailable", Reason: Q.850;cause=47

and receiving an ACK, couldn't see the BYE, but I'm sure its in there...

Mon Aug 26 20:48:53 2013: <191>8605: Janus520W: Sent: 
Mon Aug 26 20:48:53 2013: <191>8606: Janus520W: SIP/2.0 503 Service Unavailable
Mon Aug 26 20:48:53 2013: <191>8607: Janus520W: Via: SIP/2.0/UDP 58.96.1.2;branch=z9hG4bK51f5.d4304062.0,SIP/2.0/UDP 58.96.1.13:5060;received=58.96.1.13;branch=z9hG4bK7c324835;rport=5060
Mon Aug 26 20:48:53 2013: <191>8608: Janus520W: From: <sip: [CALLING-NUMBER] @58.96.1.13>;tag=as768b008e
Mon Aug 26 20:48:53 2013: <191>8609: Janus520W: To: <sip: [CALLED-NUMBER] @58.96.1.2:5060>;tag=74459D4-5CD
Mon Aug 26 20:48:53 2013: <191>8610: Janus520W: Date: Mon, 26 Aug 2013 10:48:36 GMT
Mon Aug 26 20:48:53 2013: <191>8611: Janus520W: Call-ID: 5100db863c5a13aa15482a6f66ae6735@58.96.1.13:5060
Mon Aug 26 20:48:53 2013: <191>8612: Janus520W: CSeq: 102 INVITE
Mon Aug 26 20:48:53 2013: <191>8613: Janus520W: Allow-Events: telephone-event
Mon Aug 26 20:48:53 2013: <191>8614: Janus520W: Server: Cisco-SIPGateway/IOS-12.x
Mon Aug 26 20:48:53 2013: <191>8615: Janus520W: Reason: Q.850;cause=47
Mon Aug 26 20:48:53 2013: <191>8616: Janus520W: Content-Length: 0
Mon Aug 26 20:48:53 2013: <191>8617: Janus520W: 
Mon Aug 26 20:48:53 2013: <191>8618: Janus520W: 003187: Aug 26 10:48:52.649: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Mon Aug 26 20:48:53 2013: <191>8619: Janus520W: Received: 
Mon Aug 26 20:48:53 2013: <191>8620: Janus520W: ACK sip: [CALLED-NUMBER] @ [MY-IP-ADDRESS] :5060 SIP/2.0
Mon Aug 26 20:48:53 2013: <191>8621: Janus520W: Via: SIP/2.0/UDP 58.96.1.2;branch=z9hG4bK51f5.d4304062.0
Mon Aug 26 20:48:53 2013: <191>8622: Janus520W: From: <sip: [CALLING-NUMBER] @58.96.1.13>;tag=as768b008e
Mon Aug 26 20:48:53 2013: <191>8623: Janus520W: Call-ID: 5100db863c5a13aa15482a6f66ae6735@58.96.1.13:5060
Mon Aug 26 20:48:53 2013: <191>8624: Janus520W: To: <sip: [CALLED-NUMBER] @58.96.1.2:5060>;tag=74459D4-5CD
Mon Aug 26 20:48:53 2013: <191>8625: Janus520W: CSeq: 102 ACK
Mon Aug 26 20:48:53 2013: <191>8626: Janus520W: Max-Forwards: 70
Mon Aug 26 20:48:53 2013: <191>8627: Janus520W: User-Agent: Exetel Voip
Mon Aug 26 20:48:53 2013: <191>8628: Janus520W: Content-Length: 0
Mon Aug 26 20:48:53 2013: <191>8629: Janus520W: 
Mon Aug 26 20:48:53 2013: <191>8630: Janus520W: 003188: Aug 26 10:48:52.729: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

azaghul

Seems to be resolved...touch wood...

It was either a transcoder or mtp(?) issue, appears they had not registered...oops