Sip trunk Turn up issue 503 error

[G0G3tt3r]

Have had sip running on another provider for years and now am cutting to new provider. I cant see why there is no registering. when we dont require registration it works fine.






6:11:21 217287mS SIP Rx: UDP 199.9.63.38:5060 -> 192.168.2.110:5060
OPTIONS sip:testuser@173.162.24.225:5060;transport=udp SIP/2.0
Via: SIP/2.0/UDP 199.9.63.38:5060;branch=z9hG4bK+cbe581660d2ca4d384408579d4e28e1e1+sip+1+a7e2ba98
From: <sip:testuser@199.9.63.38:5060>;tag=199.9.63.38+1+8b99de16+62c30e50
Content-Length: 0
Supported: resource-priority, 100rel
To: <sip:testuser@173.162.24.225>
Contact: <sip:5660e65fc29f40c67c318ce05dc1f24e@199.9.63.38:5060>
Allow-Events: message-summary, refer, dialog, line-seize, presence, call-info, as-feature-event
Max-Forwards: 69
Call-ID: 0gQAAC8WAAACBAAALxYAADlWNrIhsA71Ykt36n3V+qNUBe9Rv0yWp7a/ZoGnDoG1@199.9.63.38
CSeq: 489150888 OPTIONS
Organization:
Accept: application/sdp, application/dtmf-relay

16:11:21 217290mS SIP Tx: UDP 192.168.2.110:5060 -> 199.9.63.38:5060
SIP/2.0 503 Service Unavailable
Via: SIP/2.0/UDP 199.9.63.38:5060;branch=z9hG4bK+cbe581660d2ca4d384408579d4e28e1e1+sip+1+a7e2ba98
From: <sip:testuser@199.9.63.38:5060>;tag=199.9.63.38+1+8b99de16+62c30e50
Call-ID: 0gQAAC8WAAACBAAALxYAADlWNrIhsA71Ykt36n3V+qNUBe9Rv0yWp7a/ZoGnDoG1@199.9.63.38
CSeq: 489150888 OPTIONS
Supported: timer
Server: IP Office 9.1.6.0 build 153
To: <sip:testuser@173.162.24.225>;tag=940dc270e4a07b3e
Content-Length: 0

16:11:23 219598mS SIP Rx: UDP 199.9.63.38:5060 -> 192.168.2.110:5060
OPTIONS sip:173.162.24.225:5060 SIP/2.0
Via: SIP/2.0/UDP 199.9.63.38:5060;branch=z9hG4bK+e7f02407eb73423d8ab50fea800f98bc1+sip+1+a7e2ba9c
Max-Forwards: 70
Call-ID: CF3CE389-1@199.9.63.38:5060
From: <sip:199.9.63.38:5060;lr>;tag=sip+1+e66000c+2edd65cf
CSeq: 311235893 OPTIONS
Content-Length: 0
To: sip:173.162.24.225:5060
Contact: <sip:199.9.63.38:5060;lr>
Accept: application/sdp, application/dtmf-relay

16:11:23 219601mS SIP Tx: UDP 192.168.2.110:5060 -> 199.9.63.38:5060
SIP/2.0 503 Service Unavailable
Via: SIP/2.0/UDP 199.9.63.38:5060;branch=z9hG4bK+e7f02407eb73423d8ab50fea800f98bc1+sip+1+a7e2ba9c
From: <sip:199.9.63.38:5060;lr>;tag=sip+1+e66000c+2edd65cf
Call-ID: CF3CE389-1@199.9.63.38:5060
CSeq: 311235893 OPTIONS
Supported: timer
Server: IP Office 9.1.6.0 build 153
To: <sip:173.162.24.225:5060>;tag=0b0b148f44691b7c
Content-Length: 0

 

[janni78]

Those are just OPTIONS from the provider, seems IPO doesn't think it's registered.

But if you don't need to register the trunk why try?

"Trying is the first step to failure..." - Homer

 

[G0G3tt3r]

Lol. Because I want to solve the issue. From the same carrier I have 2 other 9.1 systems registered fine. This is my office one and I need to get to the root of what I don't know.

 

[janni78]

Then it would make more sense to trace the actual registration.

Put the trunk out of service and in service again from SSA.

"Trying is the first step to failure..." - Homer

 

[G0G3tt3r]

08:03:45 54645141mS SIP Tx: UDP 192.168.2.110:5060 -> 199.9.63.38:5060
REGISTER sip:199.9.63.38 SIP/2.0
Via: SIP/2.0/UDP 192.168.2.110:5060;rport;branch=z9hG4bKf782af8f823b77ecabb111b1916ae0ae
From: <sip:testuser@199.9.63.38>;tag=5c372c0013772267
To: <sip:testuser@199.9.63.38>
Call-ID: 48ac5a9ff6295b2ee27dc1d6cff2d205
CSeq: 1759220866 REGISTER
Contact: <sip:testuser@192.168.2.110:5060;transport=udp>
Expires: 3600
Max-Forwards: 70
User-Agent: IP Office 9.1.6.0 build 153
Supported: timer
Content-Length: 0

08:03:45 54645177mS SIP Rx: UDP 199.9.63.38:5060 -> 192.168.2.110:5060
SIP/2.0 403 Forbidden
Call-ID: 48ac5a9ff6295b2ee27dc1d6cff2d205
CSeq: 1759220866 REGISTER
From: <sip:testuser@199.9.63.38>;tag=5c372c0013772267
To: <sip:testuser@199.9.63.38>;tag=sip+1+31af000b+1bc81732
Via: SIP/2.0/UDP 192.168.2.110:5060;received=173.162.24.225;rport=5060;branch=z9hG4bKf782af8f823b77ecabb111b1916ae0ae
Content-Length: 0
Server: DC-SIP/2.0
Organization:

 

[IPGuru]

wel ther you go
the sip provider is refusing the registration, you need to ask them why

Have You got the correct credentials?

as you say it works without registration perhaps the provider has configured this one differently again the provider should be able to give additional assistance


Do things on the cheap & it will cost you dear

 

[G0G3tt3r]

as far as registration , I :

provide username and password at the sip credentials tab and ticked registration required.
have a URI - use internal data with unique in and out groups

does the ICR or sip in a user tab need to be completely setup for a basic register to take place? I thought no.

 

[janni78]

So "testuser" is your account at the provider?

Still, they are answering forbidden so they should be able to tell you why.

"Trying is the first step to failure..." - Homer