×
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Jobs

IP Office SIP TRUNK OVH

IP Office SIP TRUNK OVH

IP Office SIP TRUNK OVH

(OP)
Hello,

im encountring a weird issue with SIP Trunk on IP Office 500V2 R11.0, licences are installed (ESSENTIAL EDITION, 5 sip trunk channels)

we have a customer that bought 2 sip trunks (each have 1 channel) from OVH, they send him the following settings :

Line 1:
Login / User name
0033184345150
Password: password01
Authorization user name
0033184345150
Domain / Registrar
sip60.ovh.fr

---
Line 2:
Login / User name
0033184345146
Password: password02
Authorization user name
0033184345146
Domain / Registrar
sip60.ovh.fr

----

so i did create 2 SIP lines on IP Office with the sip credential above for each and and SIP URI with 2 max sessions and i populate the ITSP DOMAIN ADDRESS , and i specify the port corresponding from OVH forums about the using port. i did configure outgoing call short code for 2 extension (201 and 202) and also an incoming call route for both trunks for these 2 users as follow :

line 1 --> ICR route to 201 (outgoing also)

line 2 --> ICR route to 202 (outgoing also)

outgoing calls are working fine even simultaneous , the issue on incoming calls , when call the line 1 , all is good and the user 201 ring and call is working fine , but when calling the line 2 , i hear my local mobile provider disk for saying that i cannot reach my destination number and on SSA an error come on line 1(weird) for saying that i dnt have enough channels for the call.

Why the alarm come to line 1 even i called the line 2 ? why only when both lines are in service the issue come but when i put one of them out of service all is good (means both trunks can work independent even the line with the isse , in case its line 2) .

anyone can help me with this if you had experienced this before , thank you

here is the trace for SIP Tx and Rx coming from Monitor for one successfull call of line 1 and the fail call of line 2

line 1 number : 0033184345150
line 2 number : 0033184345146
i call from : 0021695579315

----
Monitor trace :

line 1 : success call ringing

********** Warning: Logging to Screen Stopped **********

********** Warning: Logging to Screen Started **********
1740668mS SIP Rx: UDP 91.121.150.30:5962 -> 192.168.100.250:5962
INVITE sip:0033184345150@192.168.100.250:5962;transport=udp SIP/2.0
Call-ID: 11315-WR-64df4ec7-761e8c274@sip60.ovh.fr
Contact: <sip:10.7.1.60:5060>
Content-Type: application/sdp
CSeq: 1690514265 INVITE
From: "+21695579315" <sip:0021695579315@sip60.ovh.fr;user=phone>;tag=11315-WJ-64df4ec8-7c52d5321
Max-Forwards: 29
Record-Route: <sip:91.121.150.30:5962;lr>;session=89407
To: <sip:0184345150@10.7.1.60;user=phone>
Via: SIP/2.0/UDP 91.121.150.30:5962;branch=z9hG4bK-IYUD-0bc68a45-4a2f3b8e
Allow: REFER,INVITE,NOTIFY,ACK,UPDATE,OPTIONS,REGISTER,SUBSCRIBE,NOTIFY,CANCEL,BYE,PRACK
User-Agent: Cirpack/v4.76 (gw_sip)
Content-Length: 319

v=0
o=cp10 155741097611 155741097611 IN IP4 193.251.121.115
s=SIP Call
c=IN IP4 91.121.128.137
t=0 0
m=audio 34672 RTP/AVP 8 18 0 101
b=AS:82
a=rtpmap:8 PCMA/8000/1
a=rtpmap:18 G729/8000/1
a=fmtp:18 annexb=no
a=rtpmap:0 PCMU/8000/1
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20
a=sendrecv
1740675mS SIP Tx: UDP 192.168.100.250:5962 -> 91.121.150.30:5962
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 91.121.150.30:5962;branch=z9hG4bK-IYUD-0bc68a45-4a2f3b8e
Record-Route: <sip:91.121.150.30:5962;lr>;session=89407
From: "+21695579315" <sip:0021695579315@sip60.ovh.fr;user=phone>;tag=11315-WJ-64df4ec8-7c52d5321
Call-ID: 11315-WR-64df4ec7-761e8c274@sip60.ovh.fr
CSeq: 1690514265 INVITE
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,INFO,NOTIFY,UPDATE
Supported: timer
Server: IP Office 11.0.0.0.0 build 849
To: <sip:0184345150@10.7.1.60;user=phone>;tag=4aa33ede3cbd6a24
Content-Length: 0

1740688mS SIP Tx: UDP 192.168.100.250:5962 -> 91.121.150.30:5962
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 91.121.150.30:5962;branch=z9hG4bK-IYUD-0bc68a45-4a2f3b8e
Record-Route: <sip:91.121.150.30:5962;lr>;session=89407
From: "+21695579315" <sip:0021695579315@sip60.ovh.fr;user=phone>;tag=11315-WJ-64df4ec8-7c52d5321
Call-ID: 11315-WR-64df4ec7-761e8c274@sip60.ovh.fr
CSeq: 1690514265 INVITE
Contact: <sip:0184345150@192.168.100.250:5962;transport=udp>
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,INFO,NOTIFY,UPDATE
Supported: timer
Server: IP Office 11.0.0.0.0 build 849
To: <sip:0184345150@10.7.1.60;user=phone>;tag=4aa33ede3cbd6a24
Content-Length: 0


********** SysMonitor v11.0.0.0.0 build 849 [connected to 192.168.100.250 (00E00705A71F)] **********
1745738mS SIP Rx: UDP 91.121.150.30:5962 -> 192.168.100.250:5962
CANCEL sip:0033184345150@192.168.100.250:5962;transport=udp SIP/2.0
Call-ID: 11315-WR-64df4ec7-761e8c274@sip60.ovh.fr
CSeq: 1690514265 CANCEL
From: "+21695579315" <sip:0021695579315@sip60.ovh.fr;user=phone>;tag=11315-WJ-64df4ec8-7c52d5321
Max-Forwards: 29
To: <sip:0184345150@10.7.1.60;user=phone>
Via: SIP/2.0/UDP 91.121.150.30:5962;branch=z9hG4bK-IYUD-0bc68a45-4a2f3b8e
Reason: q.850;cause=16
User-Agent: Cirpack/v4.76 (gw_sip)
Content-Length: 0

1745741mS SIP Tx: UDP 192.168.100.250:5962 -> 91.121.150.30:5962
SIP/2.0 200 OK
Via: SIP/2.0/UDP 91.121.150.30:5962;branch=z9hG4bK-IYUD-0bc68a45-4a2f3b8e
From: "+21695579315" <sip:0021695579315@sip60.ovh.fr;user=phone>;tag=11315-WJ-64df4ec8-7c52d5321
Call-ID: 11315-WR-64df4ec7-761e8c274@sip60.ovh.fr
CSeq: 1690514265 CANCEL
Supported: timer
Server: IP Office 11.0.0.0.0 build 849
To: <sip:0184345150@10.7.1.60;user=phone>;tag=4aa33ede3cbd6a24
Content-Length: 0

1745742mS SIP Tx: UDP 192.168.100.250:5962 -> 91.121.150.30:5962
SIP/2.0 487 Request Terminated
Via: SIP/2.0/UDP 91.121.150.30:5962;branch=z9hG4bK-IYUD-0bc68a45-4a2f3b8e
Record-Route: <sip:91.121.150.30:5962;lr>;session=89407
From: "+21695579315" <sip:0021695579315@sip60.ovh.fr;user=phone>;tag=11315-WJ-64df4ec8-7c52d5321
Call-ID: 11315-WR-64df4ec7-761e8c274@sip60.ovh.fr
CSeq: 1690514265 INVITE
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,INFO,NOTIFY,UPDATE
Supported: timer
Server: IP Office 11.0.0.0.0 build 849
To: <sip:0184345150@10.7.1.60;user=phone>;tag=4aa33ede3cbd6a24
Content-Length: 0

1745789mS SIP Rx: UDP 91.121.150.30:5962 -> 192.168.100.250:5962
ACK sip:0033184345150@192.168.100.250:5962;transport=udp SIP/2.0
Call-ID: 11315-WR-64df4ec7-761e8c274@sip60.ovh.fr
CSeq: 1690514265 ACK
From: "+21695579315" <sip:0021695579315@sip60.ovh.fr;user=phone>;tag=11315-WJ-64df4ec8-7c52d5321
Max-Forwards: 29
To: <sip:0184345150@10.7.1.60;user=phone>;tag=4aa33ede3cbd6a24
Via: SIP/2.0/UDP 91.121.150.30:5962;branch=z9hG4bK-IYUD-0bc68a45-4a2f3b8e
Content-Length: 0


********** Warning: Logging to Screen Stopped **********


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

line 2 : fail call, not ringing and generate alarm on line 1


1785286mS SIP Rx: UDP 91.121.150.30:5962 -> 192.168.100.250:5962
OPTIONS sip:0033184345146@192.168.100.250:5962;transport=udp SIP/2.0
Call-ID: 02-01680-16f78346-11f1ef3d5@91.121.150.30
Contact: <sip:91.121.150.30:5962>;expires=4294967295
CSeq: 1 OPTIONS
From: <sip:keepalive@91.121.150.30:5962>;tag=02-01680-16f78345-1f26bbed6
Max-Forwards: 70
To: <sip:0033184345146@sip60.ovh.fr>
Via: SIP/2.0/UDP 91.121.150.30:5962;rport;branch=z9hG4bK-QZKK-0bc7121e-2d634503
Content-Length: 0

1785289mS SIP Tx: UDP 192.168.100.250:5962 -> 91.121.150.30:5962
SIP/2.0 200 OK
Via: SIP/2.0/UDP 91.121.150.30:5962;rport;branch=z9hG4bK-QZKK-0bc7121e-2d634503
From: <sip:keepalive@91.121.150.30:5962>;tag=02-01680-16f78345-1f26bbed6
Call-ID: 02-01680-16f78346-11f1ef3d5@91.121.150.30
CSeq: 1 OPTIONS
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,INFO,NOTIFY,UPDATE
Supported: timer
Server: IP Office 11.0.0.0.0 build 849
To: <sip:0033184345146@sip60.ovh.fr>;tag=fa1bf3317fd14295
Content-Type: application/sdp
Content-Length: 249

v=0
o=UserA 2354869085 1030902706 IN IP4 192.168.100.250
s=Session SDP
c=IN IP4 192.168.100.250
t=0 0
m=audio 8000 RTP/AVP 9 18 8 4
a=rtpmap:9 G722/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:8 PCMA/8000
a=rtpmap:4 G723/16000
1787560mS SIP Tx: UDP 192.168.100.250:5962 -> 91.121.150.30:5962
OPTIONS sip:sip60.ovh.fr SIP/2.0
Via: SIP/2.0/UDP 192.168.100.250:5962;rport;branch=z9hG4bK09f4c3cdee81aca7c89ff34123591a68
From: <sip:sip60.ovh.fr>;tag=4815e9291624b946
To: <sip:sip60.ovh.fr>
Call-ID: a1036d1be244ef9a93b405aa0e03112d
CSeq: 1800002695 OPTIONS
Contact: <sip:192.168.100.250:5962;transport=udp>
Max-Forwards: 70
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,INFO,NOTIFY,UPDATE
Supported: timer
User-Agent: IP Office 11.0.0.0.0 build 849
Content-Length: 0

1787609mS SIP Rx: UDP 91.121.150.30:5962 -> 192.168.100.250:5962
SIP/2.0 501 Not Implemented
Call-ID: a1036d1be244ef9a93b405aa0e03112d
CSeq: 1800002695 OPTIONS
From: <sip:sip60.ovh.fr>;tag=4815e9291624b946
To: <sip:sip60.ovh.fr>;tag=02-32491-16f78e95-1764fdfa1
Via: SIP/2.0/UDP 192.168.100.250:5962;received=41.230.72.260;rport=5962;branch=z9hG4bK09f4c3cdee81aca7c89ff34123591a68
Content-Length: 0

1788730mS SIP Rx: UDP 91.121.150.30:5962 -> 192.168.100.250:5962
INVITE sip:0033184345146@192.168.100.250:5962;transport=udp SIP/2.0
Call-ID: 03383-BD-64dfb52a-58ccf5014@sip60.ovh.fr
Contact: <sip:10.7.1.60:5060>
Content-Type: application/sdp
CSeq: 1690535639 INVITE
From: "+21695579315" <sip:0021695579315@sip60.ovh.fr;user=phone>;tag=03383-FM-64dfb52b-03bc94026
Max-Forwards: 29
Record-Route: <sip:91.121.150.30:5962;lr>;session=92128
To: <sip:0184345146@10.7.1.60;user=phone>
Via: SIP/2.0/UDP 91.121.150.30:5962;branch=z9hG4bK-ZGFY-0bc71bab-2744345b
Allow: REFER,INVITE,NOTIFY,ACK,UPDATE,OPTIONS,REGISTER,SUBSCRIBE,NOTIFY,CANCEL,BYE,PRACK
User-Agent: Cirpack/v4.76 (gw_sip)
Content-Length: 316

v=0
o=cp10 155741102441 155741102441 IN IP4 193.251.120.205
s=SIP Call
c=IN IP4 91.121.128.138
t=0 0
m=audio 33780 RTP/AVP 8 18 0 96
b=AS:82
a=rtpmap:8 PCMA/8000/1
a=rtpmap:18 G729/8000/1
a=fmtp:18 annexb=no
a=rtpmap:0 PCMU/8000/1
a=rtpmap:96 telephone-event/8000
a=fmtp:96 0-15
a=ptime:20
a=sendrecv
1788737mS SIP Tx: UDP 192.168.100.250:5962 -> 91.121.150.30:5962
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 91.121.150.30:5962;branch=z9hG4bK-ZGFY-0bc71bab-2744345b
Record-Route: <sip:91.121.150.30:5962;lr>;session=92128
From: "+21695579315" <sip:0021695579315@sip60.ovh.fr;user=phone>;tag=03383-FM-64dfb52b-03bc94026
Call-ID: 03383-BD-64dfb52a-58ccf5014@sip60.ovh.fr
CSeq: 1690535639 INVITE
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,INFO,NOTIFY,UPDATE
Supported: timer
Server: IP Office 11.0.0.0.0 build 849
To: <sip:0184345146@10.7.1.60;user=phone>;tag=b03f582a4385a667
Content-Length: 0

1788740mS SIP Tx: UDP 192.168.100.250:5962 -> 91.121.150.30:5962
SIP/2.0 404 Not Found
Via: SIP/2.0/UDP 91.121.150.30:5962;branch=z9hG4bK-ZGFY-0bc71bab-2744345b
Record-Route: <sip:91.121.150.30:5962;lr>;session=92128
From: "+21695579315" <sip:0021695579315@sip60.ovh.fr;user=phone>;tag=03383-FM-64dfb52b-03bc94026
Call-ID: 03383-BD-64dfb52a-58ccf5014@sip60.ovh.fr
CSeq: 1690535639 INVITE
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,INFO,NOTIFY,UPDATE
Supported: timer
Server: IP Office 11.0.0.0.0 build 849
Reason: Q.850;cause=1;text="Unallocated (unassigned) number"
To: <sip:0184345146@10.7.1.60;user=phone>;tag=b03f582a4385a667
Content-Length: 0

1788787mS SIP Rx: UDP 91.121.150.30:5962 -> 192.168.100.250:5962
ACK sip:0033184345146@192.168.100.250:5962;transport=udp SIP/2.0
Call-ID: 03383-BD-64dfb52a-58ccf5014@sip60.ovh.fr
CSeq: 1690535639 ACK
From: "+21695579315" <sip:0021695579315@sip60.ovh.fr;user=phone>;tag=03383-FM-64dfb52b-03bc94026
Max-Forwards: 29
To: <sip:0184345146@10.7.1.60;user=phone>;tag=b03f582a4385a667
Via: SIP/2.0/UDP 91.121.150.30:5962;branch=z9hG4bK-ZGFY-0bc71bab-2744345b
Content-Length: 0

1792575mS SIP Tx: UDP 192.168.100.250:5962 -> 91.121.150.30:5962
OPTIONS sip:sip60.ovh.fr SIP/2.0
Via: SIP/2.0/UDP 192.168.100.250:5962;rport;branch=z9hG4bK1c044ffa909acc425779917b4c4cc6eb
From: <sip:sip60.ovh.fr>;tag=92e6751965e04d81
To: <sip:sip60.ovh.fr>
Call-ID: c2a64c8b4b3cb0430989067cf2b0c8fb
CSeq: 1242283908 OPTIONS
Contact: <sip:192.168.100.250:5962;transport=udp>
Max-Forwards: 70
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,INFO,NOTIFY,UPDATE
Supported: timer
User-Agent: IP Office 11.0.0.0.0 build 849
Content-Length: 0

1792624mS SIP Rx: UDP 91.121.150.30:5962 -> 192.168.100.250:5962
SIP/2.0 501 Not Implemented
Call-ID: c2a64c8b4b3cb0430989067cf2b0c8fb
CSeq: 1242283908 OPTIONS
From: <sip:sip60.ovh.fr>;tag=92e6751965e04d81
To: <sip:sip60.ovh.fr>;tag=02-32429-16f7a72e-3ffadbfa7
Via: SIP/2.0/UDP 192.168.100.250:5962;received=41.230.72.260;rport=5962;branch=z9hG4bK1c044ffa909acc425779917b4c4cc6eb
Content-Length: 0


********** SysMonitor v11.0.0.0.0 build 849 [connected to 192.168.100.250 (00E00705A71F)] **********

********** Warning: Logging to Screen Stopped **********

RE: IP Office SIP TRUNK OVH

(OP)
any suggestion ?

RE: IP Office SIP TRUNK OVH

You are answering Not Found so it probably can't route it, a default monitor trace would show what it's trying to match.

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

RE: IP Office SIP TRUNK OVH

You need 1 SIP trunk with 2 URIs and each URI has its own incoming and outgoing line id and login credentials.
In ICR use the lineID as criteria to route calls.

There are a lot other ways to solve this but this is the quickest and easiest, and i am a lazy engineer, i know.

RE: IP Office SIP TRUNK OVH

(OP)
intrigrant , i will try to follow your procedure now , and i let you know the results

RE: IP Office SIP TRUNK OVH

(OP)
intrigrant thank you , issue solved :)

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close