Sip trunks on oxe cant register

mramirezg

Sip trunks on oxe cant register

Post by mramirezg »

Hi, We are doing some tests with a SIP trunk operator, but we couldn´t register so we are unable to make calls.
The operator could saw that calls were arriving to their equipment but we couldn´t register so they dropped the call.

The paramenters that the public operator gave us are:
Outbound Proxy 200.94.126.72
SIP Domain asbw.alestravoip.com
Port 5060
UDP
Time to registrarion 3600 seconds
Uername: xxxx
Password: xxxx

Does anyone knows how to program the SIP external gateway to make it work?

Thanks
Mauricio
cavagnaro

Post by cavagnaro »

What does the logs say?
mramirezg

Post by mramirezg »

I have sip traces on wireshark, but the operator sends a 401 message with information so OXE can respond but is not sending the answer
You do not have the required permissions to view the files attached to this post.
User avatar
frank
Alcatel Unleashed Certified Guru
Alcatel Unleashed Certified Guru
Posts: 3390
Joined: 06 Jul 2004 00:18
Location: New York
Contact:

Post by frank »

From the SIP RFP:
If a 401 (Unauthorized) or 407 (Proxy Authentication Required)
response is received, the UAC SHOULD follow the authorization
procedures of Section 22.2 and Section 22.3 to retry the request with
credentials.
I personally think that you have done something wrong in the authentication settings.
It's case sensitive. Verify that you did not put zeros instead of letter O, and that you have an eventual REALM setup ?

THe carrier should be able to tell you what's wrong
Code Free Or Die
Rens

Post by Rens »

Hello Mauricio,

Did you solve your issue with "Status 401 Unauthorized"?

Regards,

Rens
swinstu
Member
Posts: 166
Joined: 30 Oct 2007 21:37

Re: Sip trunks on oxe cant register

Post by swinstu »

Any resolution on this.

I am encountering an issue with carrier AAPT in Sydney Australia where they have provided a Dynamic SIP service on a dedicated service.
There is no interworking report from ALE with AAPT (project aborted for unknown reason)
The OXE is behind the customers firewall and am able to reach out to to AAPT SIP server (AAPT-SBC) address 202.10.4.xxx ( an FQDN has also been provided but no external DNS provided by AAPT as they say I can either put in hostfile or internal DNS - sounds silly). Unlike Telstra SIP service.

The SIP service connection has its own Class A IP addressing scheme 10.239.18x.xxx/29, the 1st 2 addresss being the subnet and gateway and the remaining 5 addresses for dynamic connection back to the AAPT SIP server.

There is no NAT-ing from external Class A to internal Class C address OXE address.

( Note : I have had the services working from an Audiocodes SBC when the service was setup initially as a static SIP service with AAPT provided an defined address 10.239.18x.111 as we could not get the service to connect to the OXE without any registration username/password.

The carrier has since changed the service to a dynamic type with username/password type.
They have provided hostname: sipvoice.syd.aapt.com.au and its IP 202.10.4.xxx service ID: abcdefg and username: abcdefg and password:yyyyyyyyy realm: Realm

I have added the hostname and its corresponding IP to OXE host file and it is routable.
Customer has setup firewall rules to allow everything out from voice VLAN to SIP vlan and incoming is retricted to UDP port 5060.


I am getting the following motortrace 1 errors as the service is unable to register, come into service and able to make any outgoing/incoming calls.
Errors as follows:
SIP/2.0 407 Proxy Authentication Required
SIP/2.0 407 LR3 - Initial password not reset

Carrier thinks we are not sending the expiry timer which is set to default standard 3600(s)




-------------------------------------------------
Wed Jul 6 15:46:29 2016 SEND MESSAGE TO NETWORK (202.10.4.xxx:5060 [UDP]) (BUFF LEN = 541)
----------------------utf8-----------------------
REGISTER sip:sipvoice.syd.aapt.com.au SIP/2.0
Route: <sip:202.10.4.xxx;lr>
Supported: 100rel,path
User-Agent: OmniPCX Enterprise R11.2 l2.300.25.c
To: sip:abcdefg@sipvoice.syd.aapt.com.au
From: sip:abcdefg@sipvoice.syd.aapt.com.au;tag=d4e4496678293027c95926e788310986
Contact: <sip:abcdefg@192.168.xx.xx;transport=UDP>;expires=3600
Call-ID: 45f76422fdedae084fe3fe4b8fef090a@192.168.xx.xx
CSeq: 832204579 REGISTER
Via: SIP/2.0/UDP 192.168.xx.xx;branch=z9hG4bK89402e63075b607bfb4c47c3dc701600
Max-Forwards: 70
Content-Length: 0

-------------------------------------------------
1467783989 -> Wed Jul 6 15:46:29 2016 11d6[CMotorCall::setCurrentState] NOE-SIP : sendBackupUpdate Msg not sent to twin CS
Wed Jul 6 15:46:29 2016 RECEIVE MESSAGE FROM NETWORK (202.10.4.xxx:5060 [UDP])
----------------------utf8-----------------------
SIP/2.0 100 Trying
To: sip:abcdefg@sipvoice.syd.aapt.com.au
From: sip:abcdefg@sipvoice.syd.aapt.com.au;tag=d4e4496678293027c95926e788310986
Call-ID: 45f76422fdedae084fe3fe4b8fef090a@192.168.xx.xx
CSeq: 832204579 REGISTER
Via: SIP/2.0/UDP 192.168.xx.xx;branch=z9hG4bK89402e63075b607bfb4c47c3dc701600
Content-Length: 0

-------------------------------------------------

Wed Jul 6 15:46:29 2016 RECEIVE MESSAGE FROM NETWORK (202.10.4.xxx:5060 [UDP])
----------------------utf8-----------------------
SIP/2.0 407 Proxy Authentication Required
To: <sip:abcdefg@sipvoice.syd.aapt.com.au>;tag=535241501
From: sip:abcdefg@sipvoice.syd.aapt.com.au;tag=d4e4496678293027c95926e788310986
Call-ID: 45f76422fdedae084fe3fe4b8fef090a@192.168.xx.xx
CSeq: 832204579 REGISTER
Via: SIP/2.0/UDP 192.168.xx.xx;branch=z9hG4bK89402e63075b607bfb4c47c3dc701600
User-Agent: Nortel SESM 14.1.10.0
Supported: com.nortelnetworks.firewall, p-3rdpartycontrol, nosec, join, x-nortel-sipvc, gin
Proxy-Authenticate: Digest realm="Realm",nonce="MTQ2Nzc4MzkzOTU0MWQzMDkzMjBkMDE2NjJhNzMxODEwZTVjNGEwOTNjYWRi",stale=false,algorithm=MD5,qop="auth,auth-int"
Content-Length: 0

-------------------------------------------------

Wed Jul 6 15:46:29 2016 SEND MESSAGE TO NETWORK (202.10.4.xxx:5060 [UDP]) (BUFF LEN = 776)
----------------------utf8-----------------------
REGISTER sip:sipvoice.syd.aapt.com.au SIP/2.0
Proxy-Authorization: Digest username="abcdefg",realm="Realm",nonce="MTQ2Nzc4MzkzOTU0MWQzMDkzMjBkMDE2NjJhNzMxODEwZTVjNGEwOTNjYWRi",algorithm=MD5,qop=auth,cnonce="1467783989",nc=00000001,uri="sip:sipvoice.syd.aapt.com.au",response="ce17fa331e254e22194a4c2841b975a7"
Supported: 100rel,path
User-Agent: OmniPCX Enterprise R11.2 l2.300.25.c
To: sip:abcdefg@sipvoice.syd.aapt.com.au
From: sip:abcdefg@sipvoice.syd.aapt.com.au;tag=d4e4496678293027c95926e788310986
Contact: <sip:abcdefg@192.168.xx.xx;transport=UDP>;expires=3600
Call-ID: 45f76422fdedae084fe3fe4b8fef090a@192.168.xx.xx
CSeq: 832204580 REGISTER
Max-Forwards: 70
Via: SIP/2.0/UDP 192.168.xx.xx;branch=z9hG4bKc9f83c7b24362ac7413e091435aa599a
Content-Length: 0

-------------------------------------------------
1467783993 -> Wed Jul 6 15:46:29 2016 RECEIVE MESSAGE FROM NETWORK (202.10.4.xxx:5060 [UDP])
----------------------utf8-----------------------
SIP/2.0 100 Trying
To: sip:abcdefg@sipvoice.syd.aapt.com.au
From: sip:abcdefg@sipvoice.syd.aapt.com.au;tag=d4e4496678293027c95926e788310986
Call-ID: 45f76422fdedae084fe3fe4b8fef090a@192.168.xx.xx
CSeq: 832204580 REGISTER
Via: SIP/2.0/UDP 192.168.xx.xx;branch=z9hG4bKc9f83c7b24362ac7413e091435aa599a
Content-Length: 0

-------------------------------------------------

Wed Jul 6 15:46:29 2016 RECEIVE MESSAGE FROM NETWORK (202.10.4.xxx:5060 [UDP])
----------------------utf8-----------------------
SIP/2.0 407 LR3 - Initial password not reset
To: <sip:abcdefg@sipvoice.syd.aapt.com.au>;tag=1386177314
From: sip:abcdefg@sipvoice.syd.aapt.com.au;tag=d4e4496678293027c95926e788310986
Call-ID: 45f76422fdedae084fe3fe4b8fef090a@192.168.xx.xx
CSeq: 832204580 REGISTER
Via: SIP/2.0/UDP 192.168.xx.xx;branch=z9hG4bKc9f83c7b24362ac7413e091435aa599a
User-Agent: Nortel SESM 14.1.10.0
Supported: com.nortelnetworks.firewall, p-3rdpartycontrol, nosec, join, x-nortel-sipvc, gin
Proxy-Authenticate: Digest realm="Realm",nonce="MTQ2Nzc4MzkzOTU0MWQzMDkzMjBkMDE2NjJhNzMxODEwZTVjNGEwOTNjYWRi",stale=false,algorithm=MD5,qop="auth,auth-int"
Content-Length: 0



Anyone got any clues/suggestions/recommendations. I have searched nearly every forum for the past month here and system documentation for any examples etc but no help.
SWINSTU
ACSE OXE R12.1
ACSE 8770 R3.2(4760 R5.x)
ACSE OT R2.3 IP/SIP and UC&C
sadim
Alcatel Unleashed Certified Guru
Alcatel Unleashed Certified Guru
Posts: 698
Joined: 02 Jun 2006 07:11
Location: Portugal

Re: Sip trunks on oxe cant register

Post by sadim »

Hi,
In the "SIP Ext Gateway" the "Registration timer" parameter is must probably set to 0. Try to change it, then restart sipmotor.
Regards
swinstu
Member
Posts: 166
Joined: 30 Oct 2007 21:37

Re: Sip trunks on oxe cant register

Post by swinstu »

Thanks for response guys.
Sadim - the registration timer is correct.
AAPT came to site, ran some tests after I tested directly the SIP service at demarcation point with a softphone and OXE VM with WAN IP address. I was getting same issue so AAPT rebuilt the service from scratch as advised and resolved the registration issue. This was a carrier problem.
I can now connect my PC at the SIP service demarcation point and register and make calls from my softphone or OXE VM on my laptop

However my issue still exists where the OXE on customers internal network cannot register with the SIP service terminated behind their Juniper SRX240 firewall.
Does anyone have any recommendations on how the firewall should be setup for SIP NAT traversal so that I can have this implemented and working with an OXE in spatrial redundancy?
I have done been searching all over the web, technical communications and documentations, you name it.
SWINSTU
ACSE OXE R12.1
ACSE 8770 R3.2(4760 R5.x)
ACSE OT R2.3 IP/SIP and UC&C
swinstu
Member
Posts: 166
Joined: 30 Oct 2007 21:37

Re: Sip trunks on oxe cant register

Post by swinstu »

I have been able to establish calls to and from the OXE behind the firewall after some routing and port openings made by the firewall maintainer but there is NO audio both ways on the calls. A external diverted call is fine as believe the OXE is only performing the signaling here and not the media stream which could be done by the carrier SIP server in their network.

Traces from the OXe and from the customer network boundary (firewall) sent to the carrier AAPT for analysis advised saying that the contact address is incorrect which is the internal OXE address. So in order to fix this I believe I will have to introduce an SBC unless there might be another way. I have checked the codecs and compression and dont see any issue with this.

Any suggestions anyone.
SWINSTU
ACSE OXE R12.1
ACSE 8770 R3.2(4760 R5.x)
ACSE OT R2.3 IP/SIP and UC&C
cavagnaro

Re: Sip trunks on oxe cant register

Post by cavagnaro »

As said, once more, sip is not NAT friendly. Your firewall must have SBC functions or support NAT transversal which is special for SIP.
Can't re-invent the wheel.

Enviado de meu E6633 usando Tapatalk
Post Reply

Return to “SIP”