Hi David,
Thanks for the reply. Relating to the query. As you said I changed the context and below is the basic rule that I am using in extensions.conf.
exten => _00X.,1,Answer
exten => _00X.,n,Set(CALLERID(num)=99051000003852)
exten => _00X.,n,Dial(SIP/${100}@99051000003852)
exten => _00X.,n,Hangup
My sip.conf looks like this
[99051000xxxxxx]
user=990xxxxxxxxx
mailbox=100
callerid=“myskypetrunk” <99051xxxxxx>
type=friend
host=dynamic
context=international
nat=no
canreinvite=no
dtmfmode=rfc2833
pickupgroup=1
callgroup=1
subscribecontext=default
notifyringing=yes
disallow=all
allow=alaw
allow=ulaw
allow=gsm
[100]
user=100
mailbox=100
callerid=“myskypetrunk” <100>
type=friend
host=dynamic
context=international
nat=no
canreinvite=no
dtmfmode=rfc2833
pickupgroup=1
callgroup=1
subscribecontext=internal
notifyringing=yes
disallow=all
allow=alaw
allow=ulaw
allow=gsm
It gives me the following error
localhost*CLI>
<— SIP read from 172.16.62.4:65030 —>
INVITE sip:00447768271167@sip.skype.com SIP/2.0
Via: SIP/2.0/UDP 172.16.62.4:65030;branch=z9hG4bK-d8754z-2a8d1ef8fce4ff59-1—d8754z-;rport
Max-Forwards: 70
Contact: sip:100@172.16.62.4:65030
To: sip:00447768271167@sip.skype.com
From: "sami"sip:100@sip.skype.com;tag=a7830447
Call-ID: MjViMWM5ZmQ4MGZmZGNkNDM4ZmI1MzFlM2NjYmNjMTg.
CSeq: 1 INVITE
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO
Content-Type: application/sdp
User-Agent: Bria 3.0 release 3.0 stamp 56430
Content-Length: 352
v=0
o=- 12935157989375000 12935157989375000 IN IP4 172.16.62.4
s=
c=IN IP4 172.16.62.4
t=0 0
m=audio 57424 RTP/AVP 0 8 18 101
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=yes
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=sendrecv
a=candidate:1 1 UDP 659136 172.16.62.4 57424 typ host
a=candidate:1 2 UDP 659134 172.16.62.4 57425 typ host
<------------->
— (12 headers 13 lines) —
Sending to 172.16.62.4 : 65030 (NAT)
Using INVITE request as basis request - MjViMWM5ZmQ4MGZmZGNkNDM4ZmI1MzFlM2NjYmNjMTg.
Found user '100’
Found RTP audio format 0
Found RTP audio format 8
Found RTP audio format 18
Found RTP audio format 101
Peer audio RTP is at port 172.16.62.4:57424
Found audio description format G729 for ID 18
Found audio description format telephone-event for ID 101
Capabilities: us - 0xe (gsm|ulaw|alaw), peer - audio=0x10c (ulaw|alaw|g729)/video=0x0 (nothing), combined - 0xc (ulaw|alaw)
Non-codec capabilities (dtmf): us - 0x1 (telephone-event), peer - 0x1 (telephone-event), combined - 0x1 (telephone-event)
Peer audio RTP is at port 172.16.62.4:57424
Looking for 00447768271167 in international (domain sip.skype.com)
list_route: hop: sip:100@172.16.62.4:65030
localhost*CLI>
<— Transmitting (no NAT) to 172.16.62.4:65030 —>
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 172.16.62.4:65030;branch=z9hG4bK-d8754z-2a8d1ef8fce4ff59-1—d8754z-;received=172.16.62.4;rport=65030
From: "sami"sip:100@sip.skype.com;tag=a7830447
To: sip:00447768271167@sip.skype.com
Call-ID: MjViMWM5ZmQ4MGZmZGNkNDM4ZmI1MzFlM2NjYmNjMTg.
CSeq: 1 INVITE
User-Agent: Asterisk PBX
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Supported: replaces
Contact: sip:00447768271167@172.16.62.2
Content-Length: 0
<------------>
– Executing [00447768271167@international:1] Answer(“SIP/100-08ec9be0”, “”) in new stack
Audio is at 172.16.62.2 port 16294
Adding codec 0x8 (alaw) to SDP
Adding codec 0x4 (ulaw) to SDP
Adding non-codec 0x1 (telephone-event) to SDP
localhost*CLI>
<— Reliably Transmitting (no NAT) to 172.16.62.4:65030 —>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 172.16.62.4:65030;branch=z9hG4bK-d8754z-2a8d1ef8fce4ff59-1—d8754z-;received=172.16.62.4;rport=65030
From: "sami"sip:100@sip.skype.com;tag=a7830447
To: sip:00447768271167@sip.skype.com;tag=as0e847940
Call-ID: MjViMWM5ZmQ4MGZmZGNkNDM4ZmI1MzFlM2NjYmNjMTg.
CSeq: 1 INVITE
User-Agent: Asterisk PBX
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Supported: replaces
Contact: sip:00447768271167@172.16.62.2
Content-Type: application/sdp
Content-Length: 262
v=0
o=root 13953 13953 IN IP4 172.16.62.2
s=session
c=IN IP4 172.16.62.2
t=0 0
m=audio 16294 RTP/AVP 8 0 101
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=silenceSupp:off - - - -
a=ptime:20
a=sendrecv
<------------>
– Executing [00447768271167@international:2] Set(“SIP/100-08ec9be0”, “CALLERID(num)=99051000003852”) in new stack
– Executing [00447768271167@international:3] Dial(“SIP/100-08ec9be0”, “SIP/@99051000003852”) in new stack
[Nov 25 11:22:24] WARNING[15696]: chan_sip.c:2921 create_addr: No such host: 99051000003852
Really destroying SIP dialog ‘54dbe8b847158ed5172c8233521d551a@127.0.0.1’ Method: INVITE
[Nov 25 11:22:24] WARNING[15696]: app_dial.c:1183 dial_exec_full: Unable to create channel of type ‘SIP’ (cause 3 - No route to destination)
== Everyone is busy/congested at this time (1:0/0/1)
– Executing [00447768271167@international:4] Hangup(“SIP/100-08ec9be0”, “”) in new stack
== Spawn extension (international, 00447768271167, 4) exited non-zero on 'SIP/100-08ec9be0’
Scheduling destruction of SIP dialog ‘MjViMWM5ZmQ4MGZmZGNkNDM4ZmI1MzFlM2NjYmNjMTg.’ in 32000 ms (Method: INVITE)
localhost*CLI>
<— SIP read from 172.16.62.4:65030 —>
ACK sip:00447768271167@172.16.62.2 SIP/2.0
Via: SIP/2.0/UDP 172.16.62.4:65030;branch=z9hG4bK-d8754z-2d3fd790e9453fac-1—d8754z-;rport
Max-Forwards: 70
Contact: sip:100@172.16.62.4:65030
To: sip:00447768271167@sip.skype.com;tag=as0e847940
From: "sami"sip:100@sip.skype.com;tag=a7830447
Call-ID: MjViMWM5ZmQ4MGZmZGNkNDM4ZmI1MzFlM2NjYmNjMTg.
CSeq: 1 ACK
User-Agent: Bria 3.0 release 3.0 stamp 56430
Content-Length: 0
<------------->
— (10 headers 0 lines) —
set_destination: Parsing sip:100@172.16.62.4:65030 for address/port to send to
set_destination: set destination to 172.16.62.4, port 65030
Reliably Transmitting (no NAT) to 172.16.62.4:65030:
BYE sip:100@172.16.62.4:65030 SIP/2.0
Via: SIP/2.0/UDP 172.16.62.2:5060;branch=z9hG4bK32e6db12;rport
From: sip:00447768271167@sip.skype.com;tag=as0e847940
To: "sami"sip:100@sip.skype.com;tag=a7830447
Call-ID: MjViMWM5ZmQ4MGZmZGNkNDM4ZmI1MzFlM2NjYmNjMTg.
CSeq: 102 BYE
User-Agent: Asterisk PBX
Max-Forwards: 70
Content-Length: 0
Scheduling destruction of SIP dialog ‘MjViMWM5ZmQ4MGZmZGNkNDM4ZmI1MzFlM2NjYmNjMTg.’ in 32000 ms (Method: ACK)
localhost*CLI>
<— SIP read from 172.16.62.4:65030 —>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 172.16.62.2:5060;branch=z9hG4bK32e6db12;rport=5060
Contact: sip:100@172.16.62.4:65030
To: "sami"sip:100@sip.skype.com;tag=a7830447
From: sip:00447768271167@sip.skype.com;tag=as0e847940
Call-ID: MjViMWM5ZmQ4MGZmZGNkNDM4ZmI1MzFlM2NjYmNjMTg.
CSeq: 102 BYE
User-Agent: Bria 3.0 release 3.0 stamp 56430
Content-Length: 0
<------------->
— (9 headers 0 lines) —
SIP Response message for INCOMING dialog BYE arrived
Really destroying SIP dialog ‘MjViMWM5ZmQ4MGZmZGNkNDM4ZmI1MzFlM2NjYmNjMTg.’ Method: ACK
Reliably Transmitting (no NAT) to 172.16.62.3:41156:
OPTIONS sip:99051000116684@172.16.62.3:41156 SIP/2.0
Via: SIP/2.0/UDP 172.16.62.2:5060;branch=z9hG4bK566f3d2e;rport
From: “asterisk” sip:asterisk@172.16.62.2;tag=as485441e6
To: sip:99051000116684@172.16.62.3:41156
Contact: sip:asterisk@172.16.62.2
Call-ID: 03267f623f146ab4749dcd843cf48e04@172.16.62.2
CSeq: 102 OPTIONS
User-Agent: Asterisk PBX
Max-Forwards: 70
Date: Thu, 25 Nov 2010 11:22:34 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Supported: replaces
Content-Length: 0
localhost*CLI>
<— SIP read from 172.16.62.3:41156 —>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 172.16.62.2:5060;branch=z9hG4bK566f3d2e;rport=5060
From: “asterisk” sip:asterisk@172.16.62.2;tag=as485441e6
To: sip:99051000116684@172.16.62.3:41156;tag=1630151995
Call-ID: 03267f623f146ab4749dcd843cf48e04@172.16.62.2
CSeq: 102 OPTIONS
Supported: replaces, path, timer
User-Agent: Grandstream GXV3140 1.0.7.3
Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, INFO, REFER, UPDATE, MESSAGE
Content-Length: 0
Any ideas.Thanks a lot for your help.