Reason: Q.850;cause=1;text="Unallocated (unassigned) number"

[ipohead]

My Sipgate test line can no longer receive incoming calls and I'm sure I've not made any changes at this end. Outgoing calls are OK and my regular SIP line works OK.

The ICR is OK but Sipgate told me


Your Avaya System is rejecting the calls. If your PBX is evaluating the "To" header, it needs to look for the SIP-ID (1075328e0) not for a dialed phone number.



I've checked previous posts but I'm not 100% which setting to change to correct this.


17:00:23 66947374mS SIP Call Tx: 17
SIP/2.0 404 Not Found
Via: SIP/2.0/UDP 217.10.79.23;branch=z9hG4bK70fc.65f9d43148032f166a952340c097fe4a.0
Via: SIP/2.0/UDP 172.20.40.8;branch=z9hG4bK70fc.3aa1be559db5277135d5bdf0c7cb732e.0
Via: SIP/2.0/UDP 217.10.68.137;branch=z9hG4bK70fc.f49354ab5df856a93536b90cca0d1e70.0
Via: SIP/2.0/UDP 217.10.77.190:5060;branch=z9hG4bK5f87caa4
Record-Route: <sip:217.10.79.23;lr>
Record-Route: <sip:172.20.40.8;lr;did=73.8363>
Record-Route: <sip:217.10.68.137;lr>
From: "████████85" <sip:███████████30@sipgate.co.uk>;tag=as1ff07c6a
Call-ID: 79c6078d3d492de0406a42994f12ce77@sipgate.co.uk
CSeq: 103 INVITE
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,INFO,NOTIFY,UPDATE
Supported: timer
Server: IP Office 11.0.4.7.0 build 6
Reason: Q.850;cause=1;text="Unallocated (unassigned) number"
Content-Length: 0
To: <sip:██████8e0@sipgate.co.uk>;tag=89ce770b3744297e
█

 

[IamaSherpa]

Your IPO does not find a matching from the user which is directed the invite and the existing one, maybe you have to correct the Users SIP parameters in the User SIP Tab

 

[ipohead]

Thanks for that. It is going to a hunt group but the SIP tab has been set correctly as it works for my main line.

I think there's something wrong with the from: and to: and I can clarify what they are

From: "[highlight #EF2929]called number[/highlight]" <sip:[highlight #AD7FA8]caller number[/highlight]"@sipgate.co.uk>;tag=as1ff07c6a
To: <sip:[highlight #EF2929]SIP ID[/highlight]@sipgate.co.uk>;tag=89ce770b3744297e

 

[Perfs]

Have you tried;

Deleting the ICR > Save > Re-add the ICR > Save?

 

[IPOTS]

On your SIP line are you using "Use Internal Data" or "Auto"?

If configured for Use Internal Data change them to Auto.

 

[AACon]

Try changing your call routing method to Request URI (in SIP Advanced).

-Austin
I used to be an ACE. Now I'm just an Arse.

 

[ipohead]

No completely sure what happened as I recreated the ICR and the other setting were OK. I merged after each one but I did reboot at some stage so all seems OK now so thanks for your help.

16673685mS SIP Call Rx: 20
INVITE sip:[highlight #EF2929]<SIP ID>[/highlight]@192.168.0.201:5060;transport=udp SIP/2.0
Record-Route: <sip:217.10.79.23;lr>
Record-Route: <sip:172.20.40.8;lr;did=efd.13e2>
Record-Route: <sip:217.10.68.137;lr>
Via: SIP/2.0/UDP 217.10.79.23;branch=z9hG4bKfcc6.f2fd44d0ec3e4a0c5d06e998e9856f4b.0
Via: SIP/2.0/UDP 172.20.40.8;branch=z9hG4bKfcc6.227a64bc1a3183754ab631465abcb4de.0
Via: SIP/2.0/UDP 217.10.68.137;branch=z9hG4bKfcc6.382b2a0b2f074fb9e0de98ae7302ddd6.0
Via: SIP/2.0/UDP 217.10.77.191:5060;branch=z9hG4bK1296e210
Max-Forwards: 67
From: "[highlight #EF2929]<called number>[/highlight]" <sip:[highlight #EF2929]<caller number>[/highlight]@sipgate.co.uk>;tag=as30e6b6e5
To: <sip:<SIP ID>@sipgate.co.uk>
Contact: <sip:[highlight #EF2929]<caller number[/highlight]>0@217.10.77.191:5060>
Call-ID: 49964a5672564ef3487e8c054357be59@sipgate.co.uk
CSeq: 103 INVITE
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces
Content-Type: application/sdp
Content-Length: 439

Sipgate did have major maintenance about a week ago so this may have been the cause. Though not relevant to this, they told me they have stopped their STUN server.