DDI on 7.1 problem - Fixed

Status
Not open for further replies.

looops

Joined
Mar 4, 2009
Messages
5
Reaction score
0
Hi all,
To 3CX devs - great product, many thanks.

But I have a problem with 7.1 beta and the version 7.0 before it. Previously on 6.x I've had no problems with DDI but when I upgrade following the documented procedure: backup - uninstall - install - restore; my DDIs do not work. The main number that's bound to the VoIP provider works ok but DDIs that are carried by that same provider do not.

This is the successful main number that works:

08:59:51.670 [CM503004]: Call(6): Calling: RingAll800:100Ext.100103Ext.103101Ext.101107Ext.107@[Dev:sip:[email protected]:5060, Dev:sip:[email protected]:5060, Dev:sip:[email protected]:5060]
08:59:51.654 [CM503010]: Making route(s) to <sip:[email protected]:5060>
08:59:51.654 [CM505003]: Provider:[Magrathea] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [MSSGW] Transport: [sip:1.2.3.4:5060]
08:59:51.654 [CM503001]: Call(6): Incoming call from 077123123123@(Ln.10002@Magrathea) to <sip:[email protected]:5060>


This is the one that fails:

09:03:27.753 [CM500002]: Unidentified incoming call. Review INVITE and adjust source identification:
INVITE sip:0207DDI [email protected] SIP/2.0
Via: SIP/2.0/UDP 213.166.5.130;branch=z9hG4bKc3c6.3bff0036.0
Via: SIP/2.0/UDP 213.166.5.134:5060;branch=z9hG4bK49C4E221AD
Max-Forwards: 14
Record-Route: <sip:213.166.5.130;lr=on;ftag=237884C0-C1A>
Contact: <sip:[email protected]:5060>
To: <sip:[email protected]>
From: "0771231231236"<sip:[email protected]>;tag=237884C0-C1A
Call-ID: [email protected]
CSeq: 101 INVITE
Expires: 180
Min-SE: 1800
Allow: INVITE, BYE, CANCEL, ACK
Date: Wed, 04 Mar 2009 09:02:20 gmt
Supported: 100rel, timer, resource-priority, replaces
Timestamp: 1236157340
User-Agent: MSSGW
Allow-Events: telephone-event
Content-Length: 0
Remote-Party-ID: <sip:[email protected]>;party=calling;screen=yes;privacy=off

I've tried entering the DDI as either
0207DDIDDIDDI
44207DDIDDIDDI


It's not just the one DDI, cant make any of them work.

Any suggestions welcome.
Thanks.

Paul.

Fixed it - there's an entry in Edit Port [VoiP provider main number] for Source Identification by DID
Thanks anyway.

Paul.
 
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
111,885
Messages
589,545
Members
164,744
Latest member
johnblackwood1