10-24-2012 10:37 AM - edited 03-16-2019 01:51 PM
Hi I'm having issues with my UC520 where I'm attempting to configure night service forwarding to a cell phone, but any external-to-internal calls cannot be forwarded to external phone number unless the call has been manually transfered to an extension that has call forwarding enabled. This even affects single number ringing configurations.
Now I did find this link http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_tech_note09186a0080618a74.shtml and it describes my problem exactly but doesn't seam to apply to my UC 520. I captured a log of the event but of course the log didn't include any line breaks and is an unreadable mess because of this.
I could really use some help here.
10-24-2012 10:42 AM
You need to describe how you connect to PSTN and add more detail on problem symtoms ans configuration.
10-24-2012 10:52 AM
The probelm's symptoms are identical to the article I incuded a link for. It describes the exact issue I am having and a resolution for the non express version of call manager.
Call forwarding works as expected, including calls from external numbers as long as an internal handset has been manually manupulated in transfering the call to the internal extension that has call forwading configured to an external number.
That means:
1. I can configure call forwarding on an extension internally, including floating extensions configured to dial directly to an external number.
2. I can then call that extension from an internal extension and it will ring the external phone number and complete the call
3. I can then call from an external number, be answered by a human on a handset internally and forwarded to the handset with call forwarding enabled and the call completes as expected
4. I can call from an external phone number, hit the auto attendant dial the extension that has call forwarding enabled and the call never completes
We utlize a basic SIP trunk.
10-24-2012 10:58 AM
Check that you have
voice service voip
no supplementary-service sip moved-temporarily
no supplementary-service sip refer
if you have these, post output of "debug ccsip message" taken with "term mon" for a failed call. Do not enable any other debug.
10-24-2012 11:13 AM
I have thos configurations here's the output:
UC_520#terminal monitor
UC_520#
003639: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
REGISTER sip:MySip.com:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.64:5060;branch=z9hG4bK1B36726FA
From: <>>7806432139@MySip.com>;tag=BD77F5E8-1647
To: <>>7806432139@MySip.com>
Date: Wed, 24 Oct 2012 18:03:24 GMT
Call-ID: 7D5302A9-5111E2-8002DDAF-F4BCFFDB
User-Agent: Cisco-SIPGateway/IOS-12.x
Max-Forwards: 70
Timestamp: 1351101804
CSeq: 105542 REGISTER
Contact: <7806432139>
Expires: 3600
Supported: path
Content-Length: 07806432139>
003640: //66879/000000000000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.1.64:5060;received=50.99.237.105;branch=z9hG4bK1B36726FA;rport=55681
From: <>>7806432139@MySip.com>;tag=BD77F5E8-1647
To: <>>7806432139@MySip.com>;tag=1853771989-1351101804849
Call-ID: 7D5302A9-5111E2-8002DDAF-F4BCFFDB
Timestamp: 1351101804
CSeq: 105542 REGISTER
WWW-Authenticate: DIGEST qop="auth",nonce="MySipXh8or4oq9Tbtap7uBW",realm="MySip",algorithm=MD5
Content-Length: 0
003641: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
REGISTER sip:MySip.com:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.64:5060;branch=z9hG4bK1B368126
From: <>>7806432139@MySip.com>;tag=BD77F5E8-1647
To: <>>7806432139@MySip.com>
Date: Wed, 24 Oct 2012 18:03:24 GMT
Call-ID: 7D5302A9-5111E2-8002DDAF-F4BCFFDB
User-Agent: Cisco-SIPGateway/IOS-12.x
Max-Forwards: 70
Timestamp: 1351101804
CSeq: 105543 REGISTER
Contact: <7806432139>
Expires: 3600
Authorization: Digest username="7806432139",realm="MySip",uri="sip:MySip.com:5060",response="e47d12c2f5464cc52180e301143d18c3",nonce="MySipXh8or4oq9Tbtap7uBW",cnonce="598E1CBF",qop=auth,algorithm=MD5,nc=00000001
Content-Length: 07806432139>
003642: //66879/000000000000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.64:5060;received=50.99.237.105;branch=z9hG4bK1B368126;rport=55681
From: <>>7806432139@MySip.com>;tag=BD77F5E8-1647
To: <>>7806432139@MySip.com>;tag=1902871377-1351101804915
Call-ID: 7D5302A9-5111E2-8002DDAF-F4BCFFDB
Timestamp: 1351101804
CSeq: 105543 REGISTER
Contact: <7806432139>;expires=45;q=0.5
Allow-Events: call-info,line-seize,dialog,message-summary,as-feature-event,x-MySip-hoteling,x-MySip-call-center-status
Content-Length: 07806432139>
003643: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:7806432139@192.168.1.64:5060 SIP/2.0
Via: SIP/2.0/UDP 208.113.62.151:5060;branch=z9hG4bK1o851j00008hiekkg3s0.1
From: <7808328768>;tag=1563449571-1351101805633-
To: "MyCompany"<>>7806432139@MySip.com>
Call-ID: BW1403256332410121114021246@10.10.10.60
CSeq: 167295521 INVITE
Contact: <7808328768>
Diversion: <7804023231>;reason=user-busy;counter=1
Allow: ACK,BYE,CANCEL,INFO,INVITE,OPTIONS,PRACK,REFER,NOTIFY,UPDATE
Accept: application/media_control+xml,application/sdp,multipart/mixed
Supported:
Max-Forwards: 9
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 2747804023231>7808328768>7808328768>
v=0
o=MySip 105897437 1 IN IP4 208.113.62.151
s=-
c=IN IP4 208.113.62.151
t=0 0
m=audio 52138 RTP/AVP 0 18 101
a=rtpmap:0 PCMU/8000
a=rtpmap:18 G729/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=sendrecv
a=maxptime:20
a=bsoft: 1 image udptl t38
003644: //66880/F0E9AE0689C5/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 208.113.62.151:5060;branch=z9hG4bK1o851j00008hiekkg3s0.1
From: <7808328768>;tag=1563449571-1351101805633-
To: "MyCompany"<>>7806432139@MySip.com>
Date: Wed, 24 Oct 2012 18:03:25 GMT
Call-ID: BW1403256332410121114021246@10.10.10.60
CSeq: 167295521 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-12.x
Content-Length: 07808328768>
003645: //66880/F0E9AE0689C5/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 208.113.62.151:5060;branch=z9hG4bK1o851j00008hiekkg3s0.1
From: <7808328768>;tag=1563449571-1351101805633-
To: "MyCompany"<>>7806432139@MySip.com>;tag=BD77F9A8-213C
Date: Wed, 24 Oct 2012 18:03:25 GMT
Call-ID: BW1403256332410121114021246@10.10.10.60
CSeq: 167295521 INVITE
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Contact: <7806432139>
Server: Cisco-SIPGateway/IOS-12.x
Content-Length: 07806432139>7808328768>
003646: //66887/F0E9AE0689C5/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:398@10.1.10.1:5060 SIP/2.0
Via: SIP/2.0/UDP 10.1.10.2:5060;branch=z9hG4bK1B3691DA
From: <>>7808328768@MySip.com>;tag=BD7828BC-1602
To: <398>
Date: Wed, 24 Oct 2012 18:03:37 GMT
Call-ID: F8289A60-1D3B11E2-89DBDDAF-F4BCFFDB@MySip.com
Supported: 100rel,timer,resource-priority,replaces,sdp-anat
Min-SE: 1800
Cisco-Guid: 4041846278-0490410466-2311445935-4106026971
User-Agent: Cisco-SIPGateway/IOS-12.x
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Timestamp: 1351101817
Contact: <7808328768>
Expires: 180
Allow-Events: telephone-event
Max-Forwards: 8
Diversion: <>>7806432139@MySip.com>;privacy=off;reason=no-answer;counter=1;screen=no
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 2177808328768>398>
v=0
o=CiscoSystemsSIP-GW-UserAgent 2769 425 IN IP4 10.1.10.2
s=SIP Call
t=0 0
m=audio 17212 RTP/AVP 0 101
c=IN IP4 10.1.10.2
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20
003647: //66887/F0E9AE0689C5/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 10.1.10.2:5060;branch=z9hG4bK1B3691DA
To: <398>
From: <>>7808328768@MySip.com>;tag=BD7828BC-1602
Call-ID: F8289A60-1D3B11E2-89DBDDAF-F4BCFFDB@MySip.com
CSeq: 101 INVITE
Content-Length: 0
Timestamp: 1351101817398>
003648: //66887/F0E9AE0689C5/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 10.1.10.2:5060;branch=z9hG4bK1B3691DA
To: <398>;tag=ds37c4393b
From: <>>7808328768@MySip.com>;tag=BD7828BC-1602
Call-ID: F8289A60-1D3B11E2-89DBDDAF-F4BCFFDB@MySip.com
CSeq: 101 INVITE
Content-Length: 0
Contact: <398>
Allow: INVITE, BYE, CANCEL, ACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO
Cisco-Gcid: F8289A60-1D3B11E2-89DBDDAF-F4BCFFDB@MySip.com398>398>
003649: //66880/F0E9AE0689C5/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 208.113.62.151:5060;branch=z9hG4bK1o851j00008hiekkg3s0.1
From: <7808328768>;tag=1563449571-1351101805633-
To: "MyCompany"<>>7806432139@MySip.com>;tag=BD77F9A8-213C
Date: Wed, 24 Oct 2012 18:03:25 GMT
Call-ID: BW1403256332410121114021246@10.10.10.60
CSeq: 167295521 INVITE
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Contact: <398>
Server: Cisco-SIPGateway/IOS-12.x
Content-Length: 0398>7808328768>
003650: //66887/F0E9AE0689C5/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 Ok
Via: SIP/2.0/UDP 10.1.10.2:5060;branch=z9hG4bK1B3691DA
To: <398>;tag=ds37c4393b
From: <>>7808328768@MySip.com>;tag=BD7828BC-1602
Call-ID: F8289A60-1D3B11E2-89DBDDAF-F4BCFFDB@MySip.com
CSeq: 101 INVITE
Content-Length: 184
Contact: <398>
Content-Type: application/sdp
Allow: INVITE, BYE, CANCEL, ACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO
Cisco-Gcid: F8289A60-1D3B11E2-89DBDDAF-F4BCFFDB@MySip.com398>398>
v=0
o=CUE 15836135 2 IN IP4 10.1.10.1
s=SIP Call
c=IN IP4 10.1.10.1
t=0 0
m=audio 20670 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
003651: //66887/F0E9AE0689C5/SIP/Msg/ccsipDisplayMsg:
Sent:
ACK sip:398@10.1.10.1:5060;transport=udp SIP/2.0
Via: SIP/2.0/UDP 10.1.10.2:5060;branch=z9hG4bK1B36A1245
From: <>>7808328768@MySip.com>;tag=BD7828BC-1602
To: <398>;tag=ds37c4393b
Date: Wed, 24 Oct 2012 18:03:37 GMT
Call-ID: F8289A60-1D3B11E2-89DBDDAF-F4BCFFDB@MySip.com
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: telephone-event
Content-Length: 0398>
003652: //66880/F0E9AE0689C5/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 208.113.62.151:5060;branch=z9hG4bK1o851j00008hiekkg3s0.1
From: <7808328768>;tag=1563449571-1351101805633-
To: "MyCompany"<>>7806432139@MySip.com>;tag=BD77F9A8-213C
Date: Wed, 24 Oct 2012 18:03:25 GMT
Call-ID: BW1403256332410121114021246@10.10.10.60
CSeq: 167295521 INVITE
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Contact: <7806432139>
Supported: replaces
Supported: sdp-anat
Server: Cisco-SIPGateway/IOS-12.x
Supported: timer
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 2247806432139>7808328768>
v=0
o=CiscoSystemsSIP-GW-UserAgent 3168 6911 IN IP4 192.168.1.64
s=SIP Call
t=0 0
m=audio 16778 RTP/AVP 0 101
c=IN IP4 192.168.1.64
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20
003653: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
ACK sip:7806432139@192.168.1.64:5060 SIP/2.0
Via: SIP/2.0/UDP 208.113.62.151:5060;branch=z9hG4bK7n1i4u3060u0kest8081.1
From: <7808328768>;tag=1563449571-1351101805633-
To: "MyCompany"<>>7806432139@MySip.com>;tag=BD77F9A8-213C
Call-ID: BW1403256332410121114021246@10.10.10.60
CSeq: 167295521 ACK
Contact: <7808328768>
Max-Forwards: 9
Content-Length: 07808328768>7808328768>
003654: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
BYE sip:7808328768@10.1.10.2:5060 SIP/2.0
Via: SIP/2.0/UDP 10.1.10.1:5060;branch=z9hG4bKOltKyt8dr4ClH43Rokt3Cw~~244
Max-Forwards: 70
To: <>>7808328768@MySip.com>;tag=BD7828BC-1602
From: <398>;tag=ds37c4393b
Call-ID: F8289A60-1D3B11E2-89DBDDAF-F4BCFFDB@MySip.com
CSeq: 1 BYE
Content-Length: 0
Also: <206>
Allow: INVITE, BYE, CANCEL, ACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO
Cisco-Gcid: F8289A60-1D3B11E2-89DBDDAF-F4BCFFDB@MySip.com206>398>
003655: //66887/F0E9AE0689C5/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.1.10.1:5060;branch=z9hG4bKOltKyt8dr4ClH43Rokt3Cw~~244
From: <398>;tag=ds37c4393b
To: <>>7808328768@MySip.com>;tag=BD7828BC-1602
Date: Wed, 24 Oct 2012 18:03:47 GMT
Call-ID: F8289A60-1D3B11E2-89DBDDAF-F4BCFFDB@MySip.com
Server: Cisco-SIPGateway/IOS-12.x
CSeq: 1 BYE
P-RTP-Stat: PS=526,OS=76048,PR=331,OR=52483,PL=0,JI=0,LA=0,DU=9
Content-Length: 0398>
003656: //66892/F0E9AE0689C5/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:7808328768@MySip.com:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.64:5060;branch=z9hG4bK1B36B1E2B
From: <>>7808328768@MySip.com>;tag=BD786308-767
To: <>>7808328768@MySip.com>
Date: Wed, 24 Oct 2012 18:03:52 GMT
Call-ID: F4E202-1D3C11E2-89DEDDAF-F4BCFFDB@MySip.com
Supported: 100rel,timer,resource-priority,replaces,sdp-anat
Min-SE: 1800
Cisco-Guid: 4041846278-0490410466-2311445935-4106026971
User-Agent: Cisco-SIPGateway/IOS-12.x
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Timestamp: 1351101832
Contact: <7808328768>
Expires: 180
Allow-Events: telephone-event
Max-Forwards: 8
Diversion: <>>7806432139@MySip.com>;privacy=off;reason=user-busy;counter=1;screen=no
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 2247808328768>
v=0
o=CiscoSystemsSIP-GW-UserAgent 3636 3962 IN IP4 192.168.1.64
s=SIP Call
t=0 0
m=audio 17248 RTP/AVP 0 101
c=IN IP4 192.168.1.64
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20
003657: //66892/F0E9AE0689C5/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.1.64:5060;received=50.99.237.105;branch=z9hG4bK1B36B1E2B;rport=55681
From: <>>7808328768@MySip.com>;tag=BD786308-767
To: <>>7808328768@MySip.com>
Call-ID: F4E202-1D3C11E2-89DEDDAF-F4BCFFDB@MySip.com
CSeq: 101 INVITE
Timestamp: 1351101832
003658: //66892/F0E9AE0689C5/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 403 Forbidden
Via: SIP/2.0/UDP 192.168.1.64:5060;received=50.99.237.105;branch=z9hG4bK1B36B1E2B;rport=55681
From: <>>7808328768@MySip.com>;tag=BD786308-767
To: <>>7808328768@MySip.com>;tag=aprqngfrt-f8d98t30000a6
Call-ID: F4E202-1D3C11E2-89DEDDAF-F4BCFFDB@MySip.com
CSeq: 101 INVITE
Timestamp: 1351101832
003659: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
ACK sip:7808328768@MySip.com:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.64:5060;branch=z9hG4bK1B36B1E2B
From: <>>7808328768@MySip.com>;tag=BD786308-767
To: <>>7808328768@MySip.com>;tag=aprqngfrt-f8d98t30000a6
Date: Wed, 24 Oct 2012 18:03:52 GMT
Call-ID: F4E202-1D3C11E2-89DEDDAF-F4BCFFDB@MySip.com
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: telephone-event
Content-Length: 0
003660: //66880/F0E9AE0689C5/SIP/Msg/ccsipDisplayMsg:
Sent:
BYE sip:7808328768@208.113.62.151:5060;transport=udp SIP/2.0
Via: SIP/2.0/UDP 192.168.1.64:5060;branch=z9hG4bK1B36C396
From: "MyCompany"<>>7806432139@MySip.com>;tag=BD77F9A8-213C
To: <7808328768>;tag=1563449571-1351101805633-
Date: Wed, 24 Oct 2012 18:03:38 GMT
Call-ID: BW1403256332410121114021246@10.10.10.60
User-Agent: Cisco-SIPGateway/IOS-12.x
Max-Forwards: 70
Timestamp: 1351101842
CSeq: 101 BYE
Reason: Q.850;cause=16
P-RTP-Stat: PS=1088,OS=173603,PR=1286,OR=197648,PL=0,JI=0,LA=0,DU=24
Content-Length: 07808328768>
003661: //66880/F0E9AE0689C5/SIP/Msg/ccsipDisplayMsg:
Sent:
BYE sip:7808328768@208.113.62.151:5060;transport=udp SIP/2.0
Via: SIP/2.0/UDP 192.168.1.64:5060;branch=z9hG4bK1B36C396
From: "MyCompany"<>>7806432139@MySip.com>;tag=BD77F9A8-213C
To: <7808328768>;tag=1563449571-1351101805633-
Date: Wed, 24 Oct 2012 18:03:38 GMT
Call-ID: BW1403256332410121114021246@10.10.10.60
User-Agent: Cisco-SIPGateway/IOS-12.x
Max-Forwards: 70
Timestamp: 1351101843
CSeq: 101 BYE
Reason: Q.850;cause=16
P-RTP-Stat: PS=1088,OS=173603,PR=1286,OR=197648,PL=0,JI=0,LA=0,DU=24
Content-Length: 07808328768>
003662: //66880/F0E9AE0689C5/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.64:5060;received=50.99.237.105;branch=z9hG4bK1B36C396;rport=55681
From: "MyCompany"<>>7806432139@MySip.com>;tag=BD77F9A8-213C
To: <7808328768>;tag=1563449571-1351101805633-
Call-ID: BW1403256332410121114021246@10.10.10.60
Timestamp: 1351101842
CSeq: 101 BYE
Content-Length: 07808328768>
003663: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.64:5060;received=50.99.237.105;branch=z9hG4bK1B36C396;rport=55681
From: "MyCompany"<>>7806432139@MySip.com>;tag=BD77F9A8-213C
To: <7808328768>;tag=1563449571-1351101805633-
Call-ID: BW1403256332410121114021246@10.10.10.60
Timestamp: 1351101842
CSeq: 101 BYE
Content-Length: 07808328768>
UC_520#no debug ccsip message
SIP Call messages tracing is disabled
UC_520#
10-24-2012 02:21 PM
Received:
SIP/2.0 403 Forbidden
Via: SIP/2.0/UDP 192.168.1.64:5060;received=50.99.237.105;branch=z9hG4bK1B36B1E2B;rport=55681
From: <>7808328768@MySip.com>;tag=BD786308-767>
To: <>>
7808328768@MySip.com>;tag=aprqngfrt-f8d98t30000a6
Call-ID: F4E202-1D3C11E2-89DEDDAF-F4BCFFDB@MySip.com
CSeq: 101 INVITE
Timestamp: 1351101832
You need to configure so to send a calling number that belongs to you. Can use 'clid' command under DP, and other tehcnciques
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